Hello I have a problem shutting down xen guests. Using xm shutdown guests get shut down but gets stuck in state ''---s-d'' or sometimes ''------''. When trying to clone a domain when in this state (my original purpose of the whole operation) I''ll get the error: [root@hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f /var/lib/xen/images/new_img.img ERROR: virDomainGetXMLDesc() failed failed Xen syscall xenDaemonDomainDumpXMLByID failed to find this domain -490299505 The same errors occurs when for example trying to attach to the console using virsh. I have tried to use ''xm destroy'' to kill the guest the hard way but it has no effect - the state remains unchanged. I have also tried this on a few different guest installations with the same result. A thing worth noting is that the output from ''xm list --long'' differs, I''ve attached the out put pre boot, after boot and after shutdown. Note how all the devices in the guests are missing after shutdown. Both the hosts and the guests are fedora 8 installations. Regards, Christian Axelsson smiler@lanil.mine.nu
I have noticed that restarting xend fixes the states. Does that give anyone any ideas? Christian Axelsson wrote:> Hello > > I have a problem shutting down xen guests. Using xm shutdown guests > get shut down but gets stuck in state ''---s-d'' or sometimes ''------''. > When trying to clone a domain when in this state (my original purpose > of the whole operation) I''ll get the error: > > [root@hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f > /var/lib/xen/images/new_img.img > ERROR: virDomainGetXMLDesc() failed failed Xen syscall > xenDaemonDomainDumpXMLByID failed to find this domain -490299505 > > The same errors occurs when for example trying to attach to the > console using virsh. > > I have tried to use ''xm destroy'' to kill the guest the hard way but it > has no effect - the state remains unchanged. I have also tried this on > a few different guest installations with the same result. A thing > worth noting is that the output from ''xm list --long'' differs, I''ve > attached the out put pre boot, after boot and after shutdown. Note how > all the devices in the guests are missing after shutdown. > > Both the hosts and the guests are fedora 8 installations. > > Regards, > Christian Axelsson > smiler@lanil.mine.nu > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen
I''m seeing the same thing regardless of shutdown state. I''ve tried downloading the latest mercurial virtinst--devel distribution and running it. hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel cd virtinst--devel ./virt-clone -o svn -n vpnroute -f /var/lib/xen/images/vpnroute.img ERROR: virDomainGetXMLDesc() failed failed Xen syscall xenDaemonDomainDumpXMLByID failed to find this domain 1732681615 xm list svn Name ID Mem VCPUs State Time(s) svn 24 1024 1 ------ 18.3 Host and guest are both Fedora 8 Anyone know of a fix or workaround? Is this now a known issue? :) If I can help troubleshoot this in any way please let me know. I really need this to work. Rick Christian Axelsson wrote:> > Hello > > I have a problem shutting down xen guests. Using xm shutdown guests get > shut down but gets stuck in state ''---s-d'' or sometimes ''------''. > When trying to clone a domain when in this state (my original purpose of > the whole operation) I''ll get the error: > > [root@hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f > /var/lib/xen/images/new_img.img > ERROR: virDomainGetXMLDesc() failed failed Xen syscall > xenDaemonDomainDumpXMLByID failed to find this domain -490299505 > > The same errors occurs when for example trying to attach to the console > using virsh. > > I have tried to use ''xm destroy'' to kill the guest the hard way but it > has no effect - the state remains unchanged. I have also tried this on a > few different guest installations with the same result. A thing worth > noting is that the output from ''xm list --long'' differs, I''ve attached > the out put pre boot, after boot and after shutdown. Note how all the > devices in the guests are missing after shutdown. > > Both the hosts and the guests are fedora 8 installations. > > Regards, > Christian Axelsson > smiler@lanil.mine.nu > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1644.84369405) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (domid 2) > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206360333.14) > (cpu_time 9.753408915) > (online_vcpus 1) > (image > (linux > (kernel ) > (notes > (FEATURES > > ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 2) > (state -b----) > (store_mfn 196619) > (console_mfn 196618) > (device > (vif > (bridge xenbr0) > (mac 00:16:3e:3f:93:b8) > (script vif-bridge) > (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) > (backend 0) > ) > ) > (device > (vbd > (uname file:/var/lib/xen/images/minimal.img) > (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) > (mode w) > (dev xvda:disk) > (backend 0) > (bootable 1) > ) > ) > (device > (console > (protocol vt100) > (location 2) > (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) > ) > ) > ) > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1648.92600832) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (domid 2) > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206360333.14) > (cpu_time 13.048743365) > (online_vcpus 1) > (image > (linux > (kernel ) > (notes > (FEATURES > > ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 0) > (state ---s-d) > (store_mfn 196619) > (console_mfn 196618) > ) > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1635.21430615) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206309092.82) > (cpu_time 0.0) > (image > (linux > (kernel ) > (notes > (FEATURES > > ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 0) > (device > (vif > (bridge xenbr0) > (mac 00:16:3e:3f:93:b8) > (backend 0) > (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) > (script vif-bridge) > ) > ) > (device > (vbd > (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) > (bootable 1) > (driver paravirtualised) > (dev xvda:disk) > (uname file:/var/lib/xen/images/minimal.img) > (mode w) > (backend 0) > ) > ) > (device > (console > (protocol vt100) > (location 2) > (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) > ) > ) > ) > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > >-- View this message in context: http://www.nabble.com/Guest-shutdown-problems-tp16250249p16329496.html Sent from the Fedora Xen mailing list archive at Nabble.com.
Check to see if libvirtd is running else restarted libvirtd first and then restart xend. this will resolve the problem Christian Axelsson wrote:> > Hello > > I have a problem shutting down xen guests. Using xm shutdown guests get > shut down but gets stuck in state ''---s-d'' or sometimes ''------''. > When trying to clone a domain when in this state (my original purpose of > the whole operation) I''ll get the error: > > [root@hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f > /var/lib/xen/images/new_img.img > ERROR: virDomainGetXMLDesc() failed failed Xen syscall > xenDaemonDomainDumpXMLByID failed to find this domain -490299505 > > The same errors occurs when for example trying to attach to the console > using virsh. > > I have tried to use ''xm destroy'' to kill the guest the hard way but it > has no effect - the state remains unchanged. I have also tried this on a > few different guest installations with the same result. A thing worth > noting is that the output from ''xm list --long'' differs, I''ve attached > the out put pre boot, after boot and after shutdown. Note how all the > devices in the guests are missing after shutdown. > > Both the hosts and the guests are fedora 8 installations. > > Regards, > Christian Axelsson > smiler@lanil.mine.nu > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1644.84369405) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (domid 2) > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206360333.14) > (cpu_time 9.753408915) > (online_vcpus 1) > (image > (linux > (kernel ) > (notes > (FEATURES > > ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 2) > (state -b----) > (store_mfn 196619) > (console_mfn 196618) > (device > (vif > (bridge xenbr0) > (mac 00:16:3e:3f:93:b8) > (script vif-bridge) > (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) > (backend 0) > ) > ) > (device > (vbd > (uname file:/var/lib/xen/images/minimal.img) > (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) > (mode w) > (dev xvda:disk) > (backend 0) > (bootable 1) > ) > ) > (device > (console > (protocol vt100) > (location 2) > (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) > ) > ) > ) > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1648.92600832) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (domid 2) > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206360333.14) > (cpu_time 13.048743365) > (online_vcpus 1) > (image > (linux > (kernel ) > (notes > (FEATURES > > ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 0) > (state ---s-d) > (store_mfn 196619) > (console_mfn 196618) > ) > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1635.21430615) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206309092.82) > (cpu_time 0.0) > (image > (linux > (kernel ) > (notes > (FEATURES > > ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 0) > (device > (vif > (bridge xenbr0) > (mac 00:16:3e:3f:93:b8) > (backend 0) > (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) > (script vif-bridge) > ) > ) > (device > (vbd > (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) > (bootable 1) > (driver paravirtualised) > (dev xvda:disk) > (uname file:/var/lib/xen/images/minimal.img) > (mode w) > (backend 0) > ) > ) > (device > (console > (protocol vt100) > (location 2) > (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) > ) > ) > ) > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > >-- View this message in context: http://www.nabble.com/Guest-shutdown-problems-tp16250249p22845117.html Sent from the Fedora Xen mailing list archive at Nabble.com.