Re: [Xen-devel] problems I encountered using xen-4.1-testing and xen-unstable

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Wed, Jan 04, 2012 at 10:07:29PM +0000, Kay, Allen M wrote:
> I'm encountering following problems while using the latest xen-4.1-testing 
> and xen-unstable with the latest Linux 3.2 kernel:
> 
> 
> 1)      Xen-4.1-testing: dom0 only sees ~2.6GB on a 4GB system, using "cat 
> /proc/meminfo".  This is without dom_mem boot parameter and with 64-bit Xen 
> and dom0 Linux.  Native Linux reports correct memory size.

Huh. You are right. Hadn't noticed that before since I was using dom0_mem.

Ian, David: any ideas? I get the same problem and it looks as
if the area above 4GB ends up being reserved.

> 
> 
> 
> 2)      Xen-unstable:  I get ext4 file system corruption when booting xen 
> with the latest upstream Linux kernel.


That I hadn't seen. Is this with dom0 or domU? There is one bug in the 2.6.18 
kernel
in blkback if you are using that version.

> 
> Has anyone seen these two problems?
> 
> Allen

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