WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] memory hotplug problem with pygrub and pvgrub
From: Quartexx <quartex73@xxxxxxxxx>
Date: Wed, 20 Apr 2011 15:12:53 +0200
Delivery-date: Wed, 20 Apr 2011 06:14:09 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=/A/Upp5Dl8mryw+t4o7Lgk9e9VAq2+E3JLVsP5qOTSE=; b=TLFttVjV/jNELp4iPXVAVbYmxW7c77LcGUcDhva1Ha0d8C9akpFr0tVF3d78DkhQKR Jm7rCh+ptkCBCobgeZZy4JnN7S/I0g5CnpAjOb/+o5d/C8WYi6u8njtKFgETSI1jk15S +c4KKly72D3JcCpv7HPpOnUAlVe6UBuCQJk7g=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>