Mailing List Archive

> -----Original Message-----
> From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On
> Behalf Of Volodymyr Kotulskyi
> Sent: Thursday 05 June 2014 11:10
> To: xen-api@lists.xen.org
> Subject: [Xen-API] Can`t uninstall VM
>
> The server was rebooted during VM creation and now I can`t destroy it
> Please advice how to uninstall this VM ?
>
>
>
> [root@xenserver-2 ~]# xe vbd-list vdi-uuid=afc680f9-3a49-4e02-8d71-
> 004efffe2759
> uuid ( RO) : ed1bc66a-5961-fe7a-5e4c-6480bbcdd57e
> vm-uuid ( RO): 85c11607-11bb-48e2-983c-abcf6ec0b57f
> vm-name-label ( RO): Control domain on host: xenserver-2
> vdi-uuid ( RO): afc680f9-3a49-4e02-8d71-004efffe2759
> empty ( RO): false
> device ( RO): sm/backend/cf294ed7-c6bf-d01c-3899-
> bb99bb56c0dc/afc680f9-3a49-4e02-8d71-004efffe2759
>
> [root@xenserver-2 ~]# xe vm-destroy uuid=85c11607-11bb-48e2-983c-abcf6ec0b57f
> You attempted an operation on a VM that was not in an appropriate power state
> at the time; for example, you attempted to start a VM that was already
> running. The parameters returned are the VM's handle, and the expected and
> actual VM state at the time of the call.
> vm: 85c11607-11bb-48e2-983c-abcf6ec0b57f (Control domain on host: xenserver-
> 2)
> expected: halted, suspended
> actual: running
>
> [root@xenserver-2 ~]# xe vm-shutdown --force uuid=85c11607-11bb-48e2-983c-
> abcf6ec0b57f
> Error: No matching VMs found
>
> [root@xenserver-2 ~]# xe vm-reset-powerstate --force uuid=85c11607-11bb-48e2-
> 983c-abcf6ec0b57f
> Error: No matching VMs found

You are trying to shutdown/destroy the Control domain (dom0). This is probably not what you intended. I have just tried the same and get the same error ("Error: No matching VMs found"). This is not very informative but it's because it is dom0.

-Si
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

I am trying to detach ISCSI SR

[root@xenserver-2 ~]# xe pbd-list
sr-uuid=cf294ed7-c6bf-d01c-3899-bb99bb56c0dc
uuid ( RO) : c42ca367-9118-914e-c7c2-1e2c84a824ed
host-uuid ( RO): 339c6ac7-927f-4dde-a64a-666e9c57f408
sr-uuid ( RO): cf294ed7-c6bf-d01c-3899-bb99bb56c0dc
device-config (MRO): multihomelist: 192.168.2.214:3260; SCSIid:
14f504e46494c45523363636338382d516c36632d374f4d53; targetIQN:
iqn.2006-01.com.openfiler:tsn.a6f66366d865; port: 3260; target:
192.168.2.214
currently-attached ( RO): true

[root@xenserver-2 ~]# xe pbd-list
sr-uuid=cf294ed7-c6bf-d01c-3899-bb99bb56c0dc
uuid ( RO) : c42ca367-9118-914e-c7c2-1e2c84a824ed
host-uuid ( RO): 339c6ac7-927f-4dde-a64a-666e9c57f408
sr-uuid ( RO): cf294ed7-c6bf-d01c-3899-bb99bb56c0dc
device-config (MRO): multihomelist: 192.168.2.214:3260; SCSIid:
14f504e46494c45523363636338382d516c36632d374f4d53; targetIQN:
iqn.2006-01.com.openfiler:tsn.a6f66366d865; port: 3260; target:
192.168.2.214
currently-attached ( RO): true


[root@xenserver-2 ~]# xe vdi-destroy
uuid=afc680f9-3a49-4e02-8d71-004efffe2759
This operation cannot be performed because this VDI is in use by some other
operation
vdi: afc680f9-3a49-4e02-8d71-004efffe2759 (OracleLinux)
operation: destroy

[root@xenserver-2 ~]# xe vbd-list
vdi-uuid=afc680f9-3a49-4e02-8d71-004efffe2759
uuid ( RO) : ed1bc66a-5961-fe7a-5e4c-6480bbcdd57e
vm-uuid ( RO): 85c11607-11bb-48e2-983c-abcf6ec0b57f
vm-name-label ( RO): Control domain on host: xenserver-2
vdi-uuid ( RO): afc680f9-3a49-4e02-8d71-004efffe2759
empty ( RO): false
device ( RO):
sm/backend/cf294ed7-c6bf-d01c-3899-bb99bb56c0dc/afc680f9-3a49-4e02-8d71-004efffe2759




2014-06-05 13:34 GMT+03:00 Simon Beaumont <simon.beaumont@citrix.com>:

>
>
> > -----Original Message-----
> > From: xen-api-bounces@lists.xen.org [mailto:
> xen-api-bounces@lists.xen.org] On
> > Behalf Of Volodymyr Kotulskyi
> > Sent: Thursday 05 June 2014 11:10
> > To: xen-api@lists.xen.org
> > Subject: [Xen-API] Can`t uninstall VM
> >
> > The server was rebooted during VM creation and now I can`t destroy it
> > Please advice how to uninstall this VM ?
> >
> >
> >
> > [root@xenserver-2 ~]# xe vbd-list vdi-uuid=afc680f9-3a49-4e02-8d71-
> > 004efffe2759
> > uuid ( RO) : ed1bc66a-5961-fe7a-5e4c-6480bbcdd57e
> > vm-uuid ( RO): 85c11607-11bb-48e2-983c-abcf6ec0b57f
> > vm-name-label ( RO): Control domain on host: xenserver-2
> > vdi-uuid ( RO): afc680f9-3a49-4e02-8d71-004efffe2759
> > empty ( RO): false
> > device ( RO): sm/backend/cf294ed7-c6bf-d01c-3899-
> > bb99bb56c0dc/afc680f9-3a49-4e02-8d71-004efffe2759
> >
> > [root@xenserver-2 ~]# xe vm-destroy
> uuid=85c11607-11bb-48e2-983c-abcf6ec0b57f
> > You attempted an operation on a VM that was not in an appropriate power
> state
> > at the time; for example, you attempted to start a VM that was already
> > running. The parameters returned are the VM's handle, and the expected
> and
> > actual VM state at the time of the call.
> > vm: 85c11607-11bb-48e2-983c-abcf6ec0b57f (Control domain on host:
> xenserver-
> > 2)
> > expected: halted, suspended
> > actual: running
> >
> > [root@xenserver-2 ~]# xe vm-shutdown --force
> uuid=85c11607-11bb-48e2-983c-
> > abcf6ec0b57f
> > Error: No matching VMs found
> >
> > [root@xenserver-2 ~]# xe vm-reset-powerstate --force
> uuid=85c11607-11bb-48e2-
> > 983c-abcf6ec0b57f
> > Error: No matching VMs found
>
> You are trying to shutdown/destroy the Control domain (dom0). This is
> probably not what you intended. I have just tried the same and get the same
> error ("Error: No matching VMs found"). This is not very informative but
> it's because it is dom0.
>
> -Si
>



--
Best wishes.
Vladimir

On 05/06/14 12:26, Volodymyr Kotulskyi wrote:
>
> [root@xenserver-2 ~]# xe vdi-destroy
> uuid=afc680f9-3a49-4e02-8d71-004efffe2759
> This operation cannot be performed because this VDI is in use by some
> other operation
> vdi: afc680f9-3a49-4e02-8d71-004efffe2759 (OracleLinux)
> operation: destroy
>
> [root@xenserver-2 ~]# xe vbd-list
> vdi-uuid=afc680f9-3a49-4e02-8d71-004efffe2759
> uuid ( RO) : ed1bc66a-5961-fe7a-5e4c-6480bbcdd57e
> vm-uuid ( RO): 85c11607-11bb-48e2-983c-abcf6ec0b57f
> vm-name-label ( RO): Control domain on host: xenserver-2
> vdi-uuid ( RO): afc680f9-3a49-4e02-8d71-004efffe2759
> empty ( RO): false
> device ( RO):
> sm/backend/cf294ed7-c6bf-d01c-3899-bb99bb56c0dc/afc680f9-3a49-4e02-8d71-004efffe2759
>

The VBD looks like it is currently attached to dom0. Try unplugging it
(xe vbd-unplug uuid=ed1bc....). If this fails, it's usually because the
disk is in use by something, and you'll have to see any process that
might be using it (or it might be mounted).

Cheers,

Jon

2014-06-05 14:45 GMT+03:00 Jon Ludlam <jonathan.ludlam@eu.citrix.com>:

> xe vbd-unplug uuid=


*Thank you very much*


--
Best wishes.
Vladimir