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

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

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Quartexx <quartex73@xxxxxxxxx>
  • Date: Wed, 20 Apr 2011 15:12:53 +0200
  • Delivery-date: Wed, 20 Apr 2011 06:14:09 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Mkfw70GqZ54GXECLx0EFO5E9C3qNK48FDmxEawYCsJp10Tn2a6KLdz8XypnOQDmI7J W/8DlACo7XvsNBgCIIT4c0rq1Qd6/fDHQRoJAkdgxq6UUtlR0WwKce0qdU1g27ijdDB3 qZWdmakwcltOlmJ9+CVdKXH8O/7tmbogunXCE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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'

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



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