Re: [Xen-devel] Strange (???) xl behavior for save, migrate and migrate-receive

[Daniel Kiper <dkiper@xxxxxxxxxxxx>]

On Wed, Nov 02, 2011 at 06:17:38PM +0400, Vasiliy Tolstov wrote:
> 2011/10/18 Daniel Kiper <dkiper@xxxxxxxxxxxx>
>
> > Guest/host administartor could allocate for given guest no more memory than
> > maxmem (its value could be changed by xl mem-max <domain> <new_size>) 
> > allows,
> > regardless of mechanism (ballooning or memory hotplug) used for that 
> > allocation.
> > It means that memory hotplug does not pose any security threat in that
> > area.
>
> Sorry for bumping thread. Does this mean, that if i use memory=512,
> maxmem=4096 grows via balloon to 4096, after that set maxmem to 8192 and
> grows guest to 7000mb and do live migration - nothing bad happening and
> guest migrate process successed?

Yep, however, now you must use workaround for xl (which was described)
earlier in this thread. I have idea how to fix xl but I do not have
time to do it. I am going to do that next year.

Daniel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel