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/
Home Products Support Community News


Re: [Xen-devel] pvops dom0 work roadmap

To: Daniel Schroeder <sec@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] pvops dom0 work roadmap
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 19 Aug 2009 17:42:36 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>
Delivery-date: Wed, 19 Aug 2009 17:43:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A8C9811.10109@xxxxxxxxxxxxxxx>
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>
References: <4A8AF65A.2040904@xxxxxxxx> <4A8C9811.10109@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 08/19/09 17:25, Daniel Schroeder wrote:
> Hi Jeremy,
> thx for your work! I have tested current rebase/master on 64bit (Dell
> PE2900, dual quad Xeon) with xen 3.4.2-rc1 and i have two issues:
>>     * better acpi power management (ported from 2.6.18)
> how do i use the pm feature of pvops?
> [1][2]

Um, not sure.  I applied the patches, but I haven't tested them ;) 
Perhaps Yu Ke can add some light here.

> the other issue is dom0 memory...this is a bit odd...
> system booted with dom0_mem=4096m but top displays only Mem:   2088992k
> total.
> xm top is correct and displays 4GB for Domain-0.

Hm, yes that's expected.  Currently some of dom0's memory is hidden
behind the PCI aperature and is wasted.  The quick fix is to simply
return the memory to Xen so that it can at least be properly used; the
complex fix is to move that memory higher up the address space so that
it's immediately available to dom0.  I tried the latter but it turned
out pretty complex.  The former is relatively simple, and I'll probably
apply a patch to do it soonish.  Once boot-time ballooning works (ie,
starting a domain so that it can be expanded), the memory can be
re-added via the balloon driver.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>