Augusto Castelan Carlson wrote:
Hi!
One of my guests (guest1) was not accessible today. The state was
---s-d. Looking at the xen docs, for "s" says that the state is
shutdown, but there is no entry for "d".
Every night I save the guest with
# virsh save guest1 /saved/guest1_saved
and mount the guest1 disk to backup user files, umount the disk and
restore the guest:
# virsh restore /saved/guest1_saved
In the xend.log there was no message about the restore.
When I tried to shutdown (with xm ou virsh) the guest , I received
"Error: Domain cannot be shutdown". Below the " xm list" output and
the error from xend.log
Dom0 and DomU are Fedora 7 with 2.6.21-6.fc7xen, xen-3.1.2-1.fc7,
xen-libs-3.1.2-1.fc7 and libvirt-0.3.2-1.fc7.
#xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 493 2 r----- 5039.8
guest1 13 251 1 ---s-d 440.0
guest2 14 251 2 ------ 219.6
xend.log output:
[2008-01-16 08:09:15 2303] ERROR (SrvBase:88) Request shutdown failed.
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/web/SrvBase.py", line 85, in perfor
m
return op_method(op, req)
File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvDomain.py", line 65,
in op_shutdown
return self.dom.shutdown(req.args['reason'][0])
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 453,
in shutdown
raise XendError('Domain cannot be shutdown')
XendError: Domain cannot be shutdown
What is the meaning of the "---s-d" state and what canbe the cause of
this problem?
I think the 'd' in this case means 'dying'. Try shutting down the domain hard, eg. 'virsh destroy guest1'.
Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
