WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] 5x dom0 memory increase from Xen/Linux 3.4/2.6.18 to 4.1/3.0

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] 5x dom0 memory increase from Xen/Linux 3.4/2.6.18 to 4.1/3.0.0
From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
Date: Thu, 16 Jun 2011 13:58:25 +0100 (BST)
Delivery-date: Thu, 16 Jun 2011 06:00:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I have a fairly old machine with 512M of RAM that I use for testing. Under Xen 
3.4 with the 2.6.18 linux kernel it would happily work with dom0_mem=50M, 
leaving 450M for VMs. I am in the process of upgrading to Xen 4.1 with a stock 
3.0.0-rc3 linux kernel (with konrad's vga-support patch). This combination 
however requires dom0_mem=250M to work leaving only 250M for the VMs (if I try 
to set dom0_mem any lower I get a kernel panic early on in the kernel boot 
phase).

This is an increase of 5x between the two versions, and I wondered if there's 
an explanation why. Is it possible to reduce the memory requirements, or do I 
have to learn to live with it.

thanks,

Anthony Wright


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