Re: [Xen-devel] a ton of kernel issues

[Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>]

On Tue, Dec 13, 2011 at 02:36:04PM +0400, George Shuklin wrote:
> On 13.12.2011 14:19, Alessandro Salvatori wrote:
> >
> >>pv_ops is still have some issues with memory limits, but any
> >>new kernel (3.0+) will boot normal and operates with very
> >>minor glitches. Older pv_ops (f.e. debian 2.6.32) have some
> >>more major issues.
> >what glitches should one expect with 3.0+, and having the choice,
> >would it be better to go with 3.1 or even 3.2?
> >
> >
> Right now I know about two of them:
> When you set up memory for virtual machine using xenballon, value in 
> dom0 differ from value in domU. The issue is that -xen kernels 'hide' 
> some memory in 'used' memory, and pv-ops just reducing TotalMem to value 
> without that memory. Practically that means if you set up memory for 
> domain to 2GiB client will saw only 1.95GiB and so on.
> 
> The second issue is lack of support of 'pre-inflated balloon', means you 
> can not set up memory-static-max to 2GiB, target to 1GiB and do 'memory 
> grow' from 1 G to 2 G latter without VM reboot. -xen kernels allow this 
> (up to memory-static-max limit).

Is all of this with 'xm' or with 'xl' tools? What happens when you 'grow'
the memory from 1G to 2G? Are you using the hotplug memory balloon or
the older one?

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