qemu-devel
[Top][All Lists]
Advanced

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

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


From: Eduardo Habkost
Subject: Re: [Qemu-devel] [libvirt] Modern CPU models cannot be used with libvirt
Date: Mon, 26 Mar 2012 13:00:45 -0300
User-agent: Mutt/1.5.21 (2010-09-15)

On Sun, Mar 25, 2012 at 12:19:13PM +0200, Gleb Natapov wrote:
> > (That's why I said that perhaps keymaps could become configuration
> > someday. Because maybe they can be converted to a key=value model
> > relatively easily)
> > 
> Such whole sale approach is harmful since it starts to affect design
> decisions. So now if it seams logical to move something outside the code
> one can decide against it just because it will become "configuration"
> due to that design.

This is one point I agree completely with.

There's no reason to couple the decision to "move something to an
external file" with making changes to the Qemu external interfaces.

We should be able to gradually move things to be "data" without breaking
the expectations of libvirt at the same time. We must be able to make a
gradual design change, where we first move data to an external file
without making that change visible to the outside, then slowly try to
make it part of the user-visible configuration (that means making
externally visible interface changes, something that has to be made much
more carefully than just moving "internal data" around). Anthony seems
to be simply rejecting the possibility of doing this gradual change[1].

[1] I still need to read this whole thread, so sorry if I am wrong.

-- 
Eduardo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]