[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] RE: memory hotplug problem with pygrub and pvgrub



As far as I know, xm mem-set just change the memory target of Guest OS by balloon driver, 
if you use xm mem-set DomU 256 , you can also use as much as 256M memory in Guest OS.
Also it has nothing to do with memory hotplug. 


Date: Wed, 20 Apr 2011 06:14:33 -0700
From: [hidden email]
To: [hidden email]
Subject: memory hotplug problem with pygrub and pvgrub

Hi.
I'm trying memory hotplug using xm mem-set and is working fine.
But if I use pygryb or pvgrub it doesn't work

In short:

kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd1)/boot/grub/menu.lst"
memory      = '128'
maxmem=2048

from dom0:
xm mem-set domU 256
xm list show domU with 256MB

from domU I see only original 128MB
If I reboot then I see 256MB and I can move from 256 to 128 on the fly
and then again to 256 and it works.  But I try to give more than 256
then I have to reboot again to see changes in domU.

Any hints?
I have already tried to use mem=2048M in extra but no luck.

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users



If you reply to this email, your message will be added to the discussion below:
http://xen.1045712.n5.nabble.com/memory-hotplug-problem-with-pygrub-and-pvgrub-tp4315824p4315824.html
To unsubscribe from Xen, click here.


View this message in context: RE: memory hotplug problem with pygrub and pvgrub
Sent from the Xen - User mailing list archive at Nabble.com.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.