[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 1029] New: xm list contains VM ghosts of previous reboot or shutdown
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1029 Summary: xm list contains VM ghosts of previous reboot or shutdown Product: Xen Version: 3.0.4 Platform: x86-64 OS/Version: Linux-2.6 Status: NEW Severity: normal Priority: P2 Component: Unspecified AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx ReportedBy: atatut@xxxxxxxxxxxxxxxxxx Well searching for a bug regarding "xm list" problem with version 3.0.4 doesn't seem to exist, so I create it. PROBLEM: VM reboot or shutdown doesn't work; VM ghosts remain in memory. Here's the output of the "xm list": localhost ~ # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 649 8 r----- 63727.5 Domain-3b56be07-c656-1c3d-5f3b-a849ffa88b1a 114 520 1 --ps-- 52.2 Domain-7f28a72f-be76-9ef4-149a-cc5d0e59865f 113 520 1 --ps-- 32.4 Domain-8200bf13-41c1-6acb-4969-5ec2c0dc0abc 27 520 1 --ps-- 74.5 Domain-a2ae3406-f7be-a52e-1f6f-470362b77623 110 520 1 --ps-- 37.8 Domain-fcbd525e-1b07-a393-8ff7-7488b6c1d16a 96 520 1 --ps-- 76.5 Domain-fcbd525e-1b07-a393-8ff7-7488b6c1d16a 93 520 1 --ps-- 119.6 Domain-fcbd525e-1b07-a393-8ff7-7488b6c1d16a 94 520 1 --ps-- 15.7 Gentoo.2006.1_CVS4 112 520 1 --ps-- 40.2 Gentoo.2006.1_CVS4 115 520 2 -b---- 16549.7 Windows2K004 111 520 1 -b---- 179.6 WORKAROUND: Sometimes killing the VM ghosts does the trick, sometimes it just tells me the domain already exists when I try to restart it, and the only way is to rename my VM configuration file like the above: Gentoo.2006.1_CVS4, that was originally Gentoo.2006.1_CVS, but when kill was not enough anymore or simply didn't work, I had to rename the VM confile file. The only clean way is to: /etc/init.d/xend restart of cours I'd better shutdown my running VM before I execute this command. But this just "kills" the VM ghosts properly, this workaround forces me to setup all my VM from 0% to 100% then launch them and never do a reboot of any of the VM. This is a quite monolithic way to work with VMs. Is there a way cron the deletion of the VM ghosts found in the xm list? And will that do the trick? Iâ??m no coder so donâ??t ask me to hack the xen source or something. -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |