WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [RFC] [PATCH] sysfs support for Xen attributes

Dave Hansen wrote:

Debugging is always a good reason :) but I'm specifically thinking of systems management tools, deployment of virtual machines, and migration. All of these attributes are important for tools that manage, deploy, or migrate.


-ETOOMANYBUZZWORDS :)

How is this helping to reach consensus?

One concern I have with this approach is that it is for things for which
a need is _anticipated_, instead of things that are actually needed.  It
is awesome that this is being done in advance, but you have to be
careful not to throw the kitchen sink at the problem from the beginning.

I've got 2 problems with this comment. First, these things are actually needed. VMWare has tools that deploy, manage, and migrate virtual machines, PHYP does as well (it can't migrate partitions). Xen really needs tools that do the same. It would be best if these tools are open-source themselves and use GPL'd code to get the necessary information from xen. If you try to use xen I think you will agree.

My second problem with this comment the implication that anticipating needs is bad. I understand your argument but disagree on the kitchen sink comment.

Would a potential workload manager contact the individual Xen partitions
in order to get an overview of the entire machine?  Why would it not
simply contact the controlling partition?

Not sure what you mean by controlling partition. Xen doesn't have a hardware management console like PHYP does. Xen management tools need to run on a regular linux kernel that is running within a domain. Usually this is the first domain created, aka domain 0.

So to answer your question, of course a "workload manager" would contact domain 0. But how does domain 0 obtain an overview of the entire machine so it can relay that info back to the "workload manager"? Domain 0 has to get the attributes from the hypervisor. How does it do that? The best way is to read attributes from sysfs.


--

Mike D. Day
STSM and Architect, Open Virtualization
IBM Linux Technology Center
ncmike@xxxxxxxxxx

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

<Prev in Thread] Current Thread [Next in Thread>