|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 1042] xm list, xm console, xm destroy hanging
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1042
------- Comment #4 from ezjohnson@xxxxxxxxx 2007-09-06 00:02 -------
I'm seeing this on the x86_64 version too on multiple servers. Running x86_64
hypervisor, x86_64 dom0, and only PV x86_64 domU's. Xen 3.1.0 tarballs
installed on CentOS 4.5. Seems to happen if a domU hits an "out of memory"
condition and needs to be restarted manually. The xm shutdown and destroy
commands are given, xend then becomes unresponsive and must be restarted. The
domU will not be listed in the output from xm list but will be shown in xm top
with STATE d and 16k of memory that seems cannot be freed. The vbd's and vif
will still be shown as attached so attempts to restart the domU will give the
'vbd already in use by domain" message.
--
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-bugs] [Bug 1042] xm list, xm console, xm destroy hanging,
bugzilla-daemon <=
|
|
|
|
|