Hi,
when using xm mem-set on current (7278) unstable, you'll see
[2005-10-10 10:25:51 xend] ERROR (SrvBase:87) Request mem_target_set failed.
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in
perform
return op_method(op, req)
File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line
132, in op_mem_target_set
return self.call(self.dom.setMemoryTarget
TypeError: unsubscriptable object
in xend.log.
The fix is trivial, a comma is missing, see (first) attached patch.
HOWEVER, this still does not make balllooning work.
Nobody ever writes to /proc/xen/balloon.
I guess some message should go over xenbus and someone should then
write to it's balloon file. For dom0, we could do it directly in
XendDomainInfo.setMemoryTarget(). See attached second patch. It's
a hack and certainly not the right solution.
Who should do it?
Best,
--
Kurt Garloff <kurt@xxxxxxxxxx> [Koeln, DE]
Physics:Plasma modeling <garloff@xxxxxxxxxxxxxxxxxxx> [TU Eindhoven, NL]
Linux: SUSE Labs (Director) <garloff@xxxxxxx> [Novell Inc]
xen-SrvDomain-typo.diff
Description: Text document
xen-balloon-dom0.diff
Description: Text document
pgp7zvQSNcBGL.pgp
Description: PGP signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|