From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: a ton of kernel issues Date: Wed, 14 Dec 2011 12:28:04 +0000 Message-ID: <4EE89654.5040905@citrix.com> References: <4EE675A8.3030609@niemail.de> <4EE71663.5040308@gmail.com> <4EE72A94.6040904@gmail.com> <4EE75080.1000909@citrix.com> <4EE7BE1B.6070509@gmail.com> <20111213214522.GB29005@andromeda.dapyr.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111213214522.GB29005@andromeda.dapyr.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" , George Shuklin , "sandr8@gmail.com" List-Id: xen-devel@lists.xenproject.org On 13/12/11 21:45, Konrad Rzeszutek Wilk wrote: > On Wed, Dec 14, 2011 at 01:05:31AM +0400, George Shuklin wrote: >> >> On 13.12.2011 17:17, David Vrabel 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. >>> This really makes no practical difference. The memory is "used" is >>> either case and the different reporting is a side-effect of the change >>> in how certain memory allocations are done. > > David, > > You are thinking that this is the vmalloc vs kmalloc memory for the > frontends? That wasn't what I was thinking. When I looked (not very hard) at this in dom0 I thought most of it was the swiotlb buffer. David