RE: [Xen-devel] [PATCH]:libxl__get_free_memory_slack cannot retu

On Mon, 27 Sep 2010, Jun Zhu (Intern) wrote:
> Hi,
> 
> > How did you get in the state of having the target on xenstore but not
> > freemem-slack?
> > If you are using libxl this shouldn't be possible unless you mess around
> > with xenstore directly.
> 
> I did not try to find where target is created. I think the target is created 
> when dom0 starts. 
> I do nothing related with the dom0 infomation in xenstore. 
> 

Are you starting xend at boot?

> But, in my opition, it is not enough to check dom0 memory info only by 
> target. 

In that case you should add two more checks for the existance of
static-max and freemem-slack, printing a warning if only one or two of
the nodes are missing (because this state shouldn't be possible if the
user is only using libxl/xl).
If some nodes are missing, we should only write those nodes to xenstore
without overwriting the informations that are already there.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

RE: [Xen-devel] [PATCH]:libxl__get_free_memory_slack cannot return when creating a vm by xl, Jun Zhu (Intern)

Next by Date:

Re: [Xen-devel] Performance numbers on PV-on-HVM, Jagadish Nadimpalli

Previous by Thread:

RE: [Xen-devel] [PATCH]:libxl__get_free_memory_slack cannot return when creating a vm by xl, Jun Zhu (Intern)

Next by Thread:

[Xen-devel] [PATCh]: It is not an error when reporting "Device model is a stubdom", Jun Zhu (Intern)

Indexes:

[Date] [Thread] [Top] [All Lists]