On 12/21/2009 06:51 AM, Michael S. Tsirkin wrote: > On Mon, Dec 21, 2009 at 06:45:22AM -0700, David S. Ahern wrote: >> >> On 12/21/2009 05:05 AM, Avi Kivity wrote: >>> On 12/21/2009 01:45 PM, Alexander Graf wrote: >>>> >>>> Well, we have two groups: >>>> >>>> 1) Casual user w/o management app >>>> 2) Enterprise user w/ management app >>>> >>>> So I clearly belong to the first group. >>>> >>> >>> 3) Developer/power user who knows what he's about. >>> >>> You could simply add -cpu qemu64 for those guests that care about it. >>> >> >> 4) embedded virtualization where the use of a management app provides >> little to no added benefit and everything has to be >> "automated" (ie., no user). >> >> My point is there are other use cases besides data center deployments >> (aka enterprise) and workstation (casual/power user). There are use >> cases where virtualization is just yet another tool to achieve a product. >> >> David > > Yes, but unless someone runs qemu directly, default value for any flag > does not matter much. >
That's what I was getting at - "direct" invocation of qemu in an automated sense without a libvirt layer. Defaults that do the right thing on the host would be nice, with tweaking from the defaults only if something extra is wanted. David
