From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Marcos E. Matsunaga" <Marcos.Matsunaga@oracle.com>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
ian.campbell@citrix.com
Subject: Re: [PATCH] xend: Fix xm list bug reporting incorrect memory size
Date: Mon, 6 May 2013 16:31:23 -0400 [thread overview]
Message-ID: <20130506203123.GC23361@phenom.dumpdata.com> (raw)
In-Reply-To: <516824FF.7030405@oracle.com>
On Fri, Apr 12, 2013 at 11:15:11AM -0400, Marcos E. Matsunaga wrote:
> Hi Ian,
>
> Sorry, I thought I sent you the answer before, but it was stuck in
> my drafts folder for some reason.
>
> I am not very familiar with xend either, but after reading the code,
> my understanding is that when a domain is being created, it keeps
> the domain paused until all the resources are allocated, then it
> unpause it to complete the boot. If I made a wrong assumption,
> please correct me.
>
> If dominfo is called during the domain initialization process with
> update_mem = true (The default for update_mem is false), it will
> return zero as the resource is not allocated yet, and that will
> break the initialization process. Also, I don't think it would make
> sense to update memory information of a domain that is paused.
>
> That's the relevance of the domain being paused.
ping? Should Marcos include this detail in the patch and repost it?
Thanks.
>
> Regards,
>
> Marcos Eduardo Matsunaga
>
> Oracle USA
> Linux Engineering
>
> “The statements and opinions expressed here are my own and do not
> necessarily represent those of Oracle Corporation.”
>
> On 04/08/2013 01:06 PM, Ian Jackson wrote:
> >Konrad Rzeszutek Wilk writes ("[Xen-devel] [PATCH] xend: Fix xm list bug reporting incorrect memory size"):
> >>From: Marcos Matsunaga<Marcos.Matsunaga@oracle.com>
> >>
> >>Make sure memory is updated every time XendConfig.update is called.
> >>
> >>Without this patch, if a guest self-balloons, the amount of memory
> >>that 'xend' thinks the guest is using is based on last cached value.
> >>This means the reported value is nowhere close to what the real
> >>value is.
> >Err, right. I'm afraid I'm very unfamiliar with the xend code so this
> >is going to take more explanation than usual.
> >
> >>- self._dominfo_to_xapi(dominfo)
> >>+ if dominfo['paused']:
> >>+ self._dominfo_to_xapi(dominfo)
> >>+ else:
> >>+ self._dominfo_to_xapi(dominfo, update_mem = True)
> >Can you explain what the relevance is of the domain being paused ?
> >
> >Thanks,
> >Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-05-06 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 17:38 [PATCH] xend: Fix xm list bug reporting incorrect memory size Konrad Rzeszutek Wilk
2013-04-08 17:06 ` Ian Jackson
2013-04-12 15:15 ` Marcos E. Matsunaga
2013-05-06 20:31 ` Konrad Rzeszutek Wilk [this message]
2013-06-05 19:01 ` Matt Wilson
2013-06-27 9:29 ` Marcos E. Matsunaga
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=20130506203123.GC23361@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Marcos.Matsunaga@oracle.com \
--cc=ian.campbell@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.