From: "Jan Beulich" <JBeulich@novell.com>
To: Keith Coleman <list.keith@scaltro.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Re: PoD issue
Date: Fri, 19 Feb 2010 08:19:15 +0000 [thread overview]
Message-ID: <4B7E57930200007800030409@vpn.id2.novell.com> (raw)
In-Reply-To: <5411dbdc1002181603t23f3a4f6xf28bc0c92403448d@mail.gmail.com>
>>> Keith Coleman <list.keith@scaltro.com> 19.02.10 01:03 >>>
>On Thu, Feb 4, 2010 at 2:12 PM, George Dunlap
><George.Dunlap@eu.citrix.com> wrote:
>> Yeah, the OSS tree doesn't get the kind of regression testing it
>> really needs at the moment. I was using the OSS balloon drivers when
>> I implemented and submitted the PoD code last year. I didn't have any
>> trouble then, and I was definitely using up all of the memory. But I
>> haven't done any testing on OSS since then, basically.
>>
>
>Is it expected that booting HVM guests with maxmem > memory is
>unstable? In testing 3.4.3-rc2 (kernel 2.6.18 c/s 993) I can easily
>crash the guest and occasionally the entire server.
Crashing the guest is expected if the guest doesn't have a fixed
balloon driver (i.e. the mentioned c/s would need to be in the
sources the pv drivers for the guest were built from).
Crashing the host is certainly unacceptable - please provide logs
thereof.
Jan
next prev parent reply other threads:[~2010-02-19 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 17:48 PoD issue Jan Beulich
2010-02-03 18:42 ` George Dunlap
2010-02-04 8:17 ` Jan Beulich
2010-02-04 19:12 ` George Dunlap
2010-02-19 0:03 ` Keith Coleman
2010-02-19 6:53 ` Ian Pratt
2010-02-19 21:28 ` Keith Coleman
2010-02-19 8:19 ` Jan Beulich [this message]
2010-06-04 15:03 ` Pasi Kärkkäinen
-- strict thread matches above, loose matches on Subject: below --
2010-06-05 16:15 Jan Beulich
2010-06-07 9:28 ` George Dunlap
2010-06-07 9:51 ` Pasi Kärkkäinen
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=4B7E57930200007800030409@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=list.keith@scaltro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).