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

Re: [libvirt] [Qemu-devel] Modern CPU models cannot be used with libvirt



On Sun, Mar 25, 2012 at 03:14:56PM +0200, Avi Kivity wrote:
> On 03/25/2012 03:12 PM, Anthony Liguori wrote:
> >>> qemu -M pc
> >>>
> >>> Would effectively be short hand for -readconfig
> >>> /usr/share/qemu/machines/pc.cfg
> >>
> >> In that case
> >>
> >>   qemu -cpu westmere
> >>
> >> is shorthand for -readconfig /usr/share/qemu/cpus/westmere.cfg.
> >
> >
> > This is not a bad suggestion, although it would make -cpu ? a bit
> > awkward.  Do you see an advantage to this over having
> > /usr/share/qemu/target-x86_64-cpus.cfg that's read early on?
> 
> Nope.  As long as qemu -nodefconfig -cpu westmere works, I'm happy.
> 
As log as qemu -nodefconfig -cpu westmere -M pc1.1 can use different
westmere definition than -M pc1.0 (by amending it according to qom
properties in pc1.1 machine description or by reading
/usr/share/qemu/cpus/westmere-pc1.1.cfg instead) I'm happy too.

> The reasoning is, loading target-x86_64-cpus.cfg does not alter the
> current instance's configuration, so reading it doesn't violate
> -nodefconfig.
> 
> >>> files be read by default or just treated as additional configuration
> >>> files.
> >>
> >> If they're read as soon as they're referenced, what's the difference?
> > I think the thread has reduced to: should /usr/share configuration
> >
> > I suspect libvirt would not be happy with reading configuration files
> > on demand..
> 
> Why not?
> 
> -- 
> error compiling committee.c: too many arguments to function

--
			Gleb.


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