All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@overnetdata.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Para-Virt DomU + HVM DomU with xen 4.1.1 & linux 3.0.6 locks up system
Date: Fri, 14 Oct 2011 16:16:58 +0100	[thread overview]
Message-ID: <4E98526A.7090007@overnetdata.com> (raw)
In-Reply-To: <20111014140030.GF4577@phenom.oracle.com>

On 14/10/2011 15:00, Konrad Rzeszutek Wilk wrote:
> On Fri, Oct 14, 2011 at 02:35:13PM +0100, Anthony Wright wrote:
>> I have xen 4.1.1 running with a 3.0.6 linux kernel, both 32 bit.
>>
>> If I run 2 x para-virtualized DomUs they run fine. If I run 2 x HVM
>> DomUs they run fine. If I run 1 x para-virtualized and 1 x HVM DomU (it
>> doesn't matter which one is run first & which second), the system locks
>> up just after I start the second DomU.
> Locks up you say? When you launch the second guest, can you
> also run 'while (true); do; xl list; sleep 1; done' to see if the memory
> for Dom0 is going down to unreasonable amount?
It behaves as if it's run out of memory as you say, but I did 'while
true; do; xl list; sleep 0.2 ; done' on one session while I started the
other DomU, and the system locked so quickly that the xl list didn't see
any drop in Dom0 memory or the DomU even start.

I have given Dom0 1000MB, and the HVM DomU also uses 1000MB (though it
gets reported as 995MB). The para-virtual DomU uses 2000MB, and the
machine has 8GB. Before I start the para-virtual DomU the commited
AS_limit is around 141MB

      parent reply	other threads:[~2011-10-14 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 13:35 Para-Virt DomU + HVM DomU with xen 4.1.1 & linux 3.0.6 locks up system Anthony Wright
2011-10-14 14:00 ` Konrad Rzeszutek Wilk
2011-10-14 14:42   ` Pasi Kärkkäinen
2011-10-14 15:16   ` Anthony Wright [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E98526A.7090007@overnetdata.com \
    --to=anthony@overnetdata.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.