From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
John <lists.xen@nuclearfallout.net>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Memory allocation with rebooted HVM
Date: Wed, 14 Oct 2009 12:12:05 -0400 [thread overview]
Message-ID: <20091014161205.GA32613@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0910131928480.8383@kaball-desktop>
On Tue, Oct 13, 2009 at 07:30:32PM +0100, Stefano Stabellini wrote:
> On Tue, 13 Oct 2009, Keir Fraser wrote:
> > On 13/10/2009 19:13, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
> > wrote:
> >
> > >> This seems to have been triggered just by that one domU being restarted.
> > >> I've seen this before as well, when a 4G domU tried to restart and hosed a
> > >> box that only had 3G of memory free (on top of the 4G it was using).
> > >
> > > It seems to me that the new domain is always created after the old one
> > > has been destroyed with the exception that the old stubdom may still be
> > > alive but one stubdom uses only 32MB of ram, therefore cannot be the one
> > > preventing you from restarting the domain, especially in the case above
> > > where you had 3G free.
> >
> > How much guest memory might the stubdom map? Could the stubdom be preventing
> > the guest's memory from being freed, by holding references to the pages?
> >
>
> Yes it could, this can also be the reason why he was able to reproduce
> this problem only few times (it depends on how much memory the stubdom has
> mapped, and that can vary from case to case).
We had encountered this problem in the past with blkback and with the SCSI disks
being iSCSI. The page's had a page-reference that would never decrement and
the guest would stay in its zombie state. I've posted a patch some-time ago:
http://lists.xensource.com/archives/html/xen-devel/2009-09/msg00561.html
that can help troubleshoot if this is indeed this type of failure.
next prev parent reply other threads:[~2009-10-14 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 20:54 Memory allocation with rebooted HVM John
2009-10-12 7:28 ` Keir Fraser
2009-10-12 7:49 ` John
2009-10-12 8:04 ` Keir Fraser
2009-10-13 15:32 ` Stefano Stabellini
2009-10-13 17:08 ` John
2009-10-13 18:13 ` Stefano Stabellini
2009-10-13 18:21 ` Keir Fraser
2009-10-13 18:30 ` Stefano Stabellini
2009-10-14 16:12 ` Konrad Rzeszutek Wilk [this message]
2009-10-14 17:20 ` John
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=20091014161205.GA32613@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=lists.xen@nuclearfallout.net \
--cc=stefano.stabellini@eu.citrix.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.