Re: VCPU mapping into the XML

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Feb 27, 2007 at 02:04:22PM +0000, Daniel P. Berrange wrote:
> On Tue, Feb 27, 2007 at 06:40:54PM +0900, ASANO Yuzuru wrote:
> > Hello,
> > 
> > I want to add the info of VCPU mapping into the XML,
> > because we cannot manage VCPU mapping automatically
> > when a domain starts or reboots.
> > 
> > But in the following patch, the function written in "TODO"
> > which I wanted has not been accepted.
> > 
> > https://www.redhat.com/archives/libvir-list/2006-August/msg00015.html
> > 
> > If I provided the patch managing VCPU mapping in the XML, do you accept it?
> 
> The VCPU mapping, schedular parameters, and similar types of data are all 
> examples of 'runtime policy' you'd apply to a guest domain. The XML format 
> meanwhile, is expressing a guest's virtual hardware definition. IMHO we
> should not mix runtime policy with hardware defintiion, and thus I'd say
> it was not appropriate to include VCPU mapping in the XML.

 If I good remember we've selected XML, because it supports namespaces
 and you can extend a domain description by arbitrary three-party
 (non-libvirt) stuff.

    Karel

-- 
 Karel Zak  <kzak@xxxxxxxxxx>


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]