[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Error, system does not manage this VDI on iscsi SR



Hi Anthony,

The managed flag needs to be toggled. If you issue:

'xe vdi-create sr-uuid=c356b7b4-8cb1-4937-dd9b-983f0da2d124 name-label=<DISK NAME> type=user virtual-size=10737418240'

it should return the next closest match VDI from the SR unmanaged list, i.e. the VDI below. This will toggle the status to managed, and you can attach the LUN.

- Julian

Anthony Xu wrote:
1. I created a iscsi SR(uuid=c356b7b4-8cb1-4937-dd9b-983f0da2d124), and
create a lun in iscsi server side, then I execute xe sr-scan, a vdi is
created automatically on top of this lun,

xe sr-param-list uuid=c356b7b4-8cb1-4937-dd9b-983f0da2d124
uuid ( RO)                    : c356b7b4-8cb1-4937-dd9b-983f0da2d124
              name-label ( RW): iscsi
name-description ( RW): host ( RO): <shared>
      allowed-operations (SRO): forget; VDI.introduce; VDI.create; plug;
destroy; VDI.destroy; scan; VDI.clone; unplug
current-operations (SRO): VDIs (SRO): 7beeee98-7168-137d-d7e8-7ef947af00d4
                    PBDs (SRO): 21e6c59c-a767-c711-a049-90e60f76c3a0;
033d093f-2c07-a016-6e2f-be7e8fed581d
      virtual-allocation ( RO): 10737418240
    physical-utilisation ( RO): 10737418240
           physical-size ( RO): 10737418240
                    type ( RO): iscsi
            content-type ( RO): user
                  shared ( RW): true
other-config (MRW): sm-config (MRO): datatype: ISCSI; multipathable: true;
targetIQN: iqn.1986-03.com.sun:02:01b2118736a-1257199661; target:
192.168.1.248; disktype: Raw
blobs ( RO): xe vdi-param-list uuid=7beeee98-7168-137d-d7e8-7ef947af00d4 uuid ( RO) : 7beeee98-7168-137d-d7e8-7ef947af00d4 name-label ( RW): name-description ( RW): is-a-snapshot ( RO): false
             snapshot_of ( RO): <not in database>
snapshots ( RO): snapshot_time ( RO): 19700101T00:00:00Z
      allowed-operations (SRO): clone; destroy
current-operations (SRO): sr-uuid ( RO): c356b7b4-8cb1-4937-dd9b-983f0da2d124
           sr-name-label ( RO): iscsi
               vbd-uuids (SRO): 1c9664df-0e32-e90c-89fa-27f98e59bc63
crashdump-uuids (SRO): virtual-size ( RO): 10737418240
    physical-utilisation ( RO): 0
                location ( RO): 7beeee98-7168-137d-d7e8-7ef947af00d4
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): false
            storage-lock ( RO): false
                 managed ( RO): false
                  parent ( RO): <not in database>
                 missing ( RO): false
other-config (MRW): xenstore-data (MRO): sm-config (MRO): LUNid: 10; SCSIid:
3600144f0a5af4e0000004b67aa0c004c





2. created a vm from "Other install media", and created a vbd for this
vm by using iscsi vdi,

xe vbd-list vm-uuid=ebc13a16-958b-e55f-c765-6f9a5658199f uuid ( RO) : 1c9664df-0e32-e90c-89fa-27f98e59bc63
          vm-uuid ( RO): ebc13a16-958b-e55f-c765-6f9a5658199f
    vm-name-label ( RO): Other install media (1)
         vdi-uuid ( RO): 7beeee98-7168-137d-d7e8-7ef947af00d4
            empty ( RO): false
device ( RO):


3. when I ran xe vm-start,  it failed.

xe vm-start uuid=ebc13a16-958b-e55f-c765-6f9a5658199f
This operation cannot be performed because the system does not manage
this VDI
vdi: 1c9664df-0e32-e90c-89fa-27f98e59bc63





Input are highly appreciated !



Thanks,
Anthony





_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.