|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 145] New: Balloon or set-mem too low causes hang
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=145
Summary: Balloon or set-mem too low causes hang
Product: Xen
Version: unstable
Platform: Other
OS/Version: Linux-2.6
Status: NEW
Severity: normal
Priority: P2
Component: Hypervisor
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: pl@xxxxxxxxxx
CC: hohnbaum@xxxxxxxxxx
This is a well known problem, but it should really be documented as a bug.
Using either the /proc/xen/balloon interface, or xm set-mem (previously xm
balloon) to set the memory reservation for a domain to a value far too low,
causes the domain to hang. This applies to both dom0 and domU, but of course
the results are a bit more severe in dom0.
Example for reproducing this:
# xm set-mem some-domain 1
or
echo 100 > /proc/xen/balloon
The current version I'm testing with is xen-unstable:
changeset: 6026:b63577ff53a3161ac73b55e0aa87803e76c8bde5
tag: tip
user: kaf24@xxxxxxxxxxxxxxxxxxxx
date: Fri Aug 5 09:57:43 2005
summary: Fix xtime_lock handling to avoid deadlock in sched_clock().
It's really far to easy to shoot yourself in the foot here, and I believe this
needs to be more than simply documented.
------- 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 145] New: Balloon or set-mem too low causes hang,
pl <=
|
|
|
|
|