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] Re: [PATCH 0 of 3] Patches for PCI passthrough with modi

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 0 of 3] Patches for PCI passthrough with modified E820 (v3) - resent.
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Fri, 13 May 2011 09:47:20 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Fri, 13 May 2011 01:48:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110512174133.GE11649@xxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <patchbomb.1304518670@xxxxxxxxxxxxxxxxxxxxxxx> <1304931630.26692.205.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110509210140.GA29498@xxxxxxxxxxxx> <1305016202.26692.255.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110510145322.GA17128@xxxxxxxxxxxx> <1305040198.26692.286.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110510152751.GA13469@xxxxxxxxxxxx> <1305041579.26692.291.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110510155147.GA17563@xxxxxxxxxxxx> <1305100191.26692.306.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110512174133.GE11649@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2011-05-12 at 18:41 +0100, Konrad Rzeszutek Wilk wrote: 
> > Can you actually allocate and use (nearly) all of that 4G? (modulo
> > kernel allocations/overheads etc). The above doesn't really show that
> memhog 4G worked great.. but then I noticed it started slowing down and
> it was using the swap disk?

I guess the I/O holes shadowed the RAM and hence it is basically wasted.

> Anyhow, seems that if you are using RHEL5, SLES11, you need to be carefull to
> use 'memory' and 'maxmem'.

Hrm, changing behaviour for existing guests isn't so nice, at least not
without a way to turn the behaviour off, perhaps we do need an explicit
cfg file variable to control this after all?

>  With the PVOPS, need to balloon up and you are OK.
> Thought I do want to see about writting the code that would automatically 
> balloon
> back to the amount of memory that was deflated.

I wonder if just writing the correct balloon target to xenstore while
building the guest would be sufficient for the guest to balloon up once
it's up?


Xen-devel mailing list

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