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


[Xen-devel] Re: How is the virt_hv_start_low used in compatible guest

To: Jan Beulich <jbeulich@xxxxxxxxxx>, "yunhong.jiang@xxxxxxxxx" <yunhong.jiang@xxxxxxxxx>
Subject: [Xen-devel] Re: How is the virt_hv_start_low used in compatible guest
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 09 Jul 2009 08:27:18 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 09 Jul 2009 00:27:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A55A948020000780004C412@xxxxxxxxxxxxxxxxxx>
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
Thread-index: AcoAZlSLrug5jVnOTOmj/HIFHKe2wAAAFvh8
Thread-topic: How is the virt_hv_start_low used in compatible guest
User-agent: Microsoft-Entourage/
On 09/07/2009 08:24, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>>>> "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> 07/08/09 9:22 AM >>>
>> When consider the memory add situation, the size can't be
>> adjusted, so I disable this adjustment if we support memory
>> add, do you think it is ok?
> I wouldn't welcome this - instead, the maximum range of
> memory ever expected to be added should be controlled by a
> command line option for that purpose. And even without such,
> instead of completely avoiding the adjustment, it should be
> done assuming the maximum amount a 32-bit domain would
> ever get to see (128Gb), which would still make the hole
> smaller than it is on a 32-bit hv.

We agreed for now to size the hole big enough for amount of memory visible
at boot time, and compat dom0 will simply be unable to be allocated
dynamically added memory. It is at least not a regression of existing
support for compat dom0. We can do smarter things later if someone really
cares about the limitations of this scenario.

 -- Keir

Xen-devel mailing list

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