>From: Charles Coffing
>Sent: 2006年5月20日 3:59
>> On Thu, May 18, 2006 at 10:23 PM, in message
>"Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>> Hi, Charles
>> Just one suggestion, for xen- hvm- auto- balloon.diff, how
>> xc.domain_setmaxmem(self.domid, m)
>> xc.domain_setmaxmem(self.domid, self.info['memory']
>Ideally, yes, I would agree. But later, in qemu, another
>increase_reservation() is called. If I make the suggested change, I
>suspect that qemu will fail to get its memory.
>Or is this upper limit not checked when increase_reservation() is
>called from dom0?
BTW, could you please explain why following change is required:
+ given amount, also in KiB. This is normally just mem, but if
+ supported, keep a little extra free."""
+ if 'hvm' in xc.xeninfo()['xen_caps']:
+ mem_kb += 4*1024;
+ return mem_kb
Why do you need to reserve extra memory even for domU as long as
the platform supports hvm feature?
P.S I'll send a patch to reverse this change for ia64, since balloon doesn't
work for xen/ia64 yet and thus we have to allocate all memory at creation
Xen-devel mailing list