[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] GPLPV memory ballooning and x32
> > Any idea why this is occurring? > > Perhaps a bug in populate-on-demand, which I guess is what gets enabled > when > you specify maxmem parameter for an HVM domain. It gets allocated its > basic > memory parameter initially, and extra memory gets allocated when the > HVM > guest first writes to it, up to maxmem limit. Or that's the intent > anyway. > > This is not a regression from 3.1 presumably (3.1 does not implement > populate-on-demand at all)? No, this is not a regression from 3.1. With 3.1 the domHVM would come up but you would only be able to balloon up and down between N and what was specified in the memory option. The maxmem option had no effect. However, as you pointed out ballooning was only kind of working with 3.1. Is there a work around for this issue in 3.4.2? Thanks, Aravindh _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |