|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 227] New: Domains hang, no console, cannot be destroyed
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=227
Summary: Domains hang, no console, cannot be destroyed
Product: Xen
Version: unstable
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Tools
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: treed-bugzilla@xxxxxxxxxxxxxxx
After resolving the issue in bug 226 I was able to start a domain, or so it
seemed. xm create /etc/xen/mail.conf would return me to the command line but xm
list showed:
Name Id Mem(MB) CPU VCPU(s) State Time(s)
Domain-0 0 251 0 1 r---- 602.3
mail 29 0 0 1 ----c 0.3
Should Mem be 0? xm destroy seemed to have no effect in killing this domain. I
tried starting it again to get console and see what was happening:
root@localhost xen]# xm create -c mail.conf
Using config file "mail.conf".
Started domain mail
And my terminal hung there. Ctrl-c, ctrl-z did nothing. xm destroy would return
my prompt with no errors but xm list still shows the domains. At this point I
was unable to start any more domains. xm info shows:
free_memory : 113
So the hung domains were eating up all of my RAM. I had to reboot the system to
kill the domains and get my RAM back.
The point of this install was to get some experience using xen but unstable
still seems to have a number of issues so I am going to wipe this box and give
stable a try now.
--
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 227] New: Domains hang, no console, cannot be destroyed,
bugzilla-daemon <=
|
|
|
|
|