On 12/21/2009 03:45 PM, 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.
If there is no user, then a management app exists. It may be as simple
as execing qemu from initrd, but there is still something that is not a
user that can set the correct parameters. It is up to the author of
this one-line management app to decide what the correct parameters are
(-cpu host or some other cpu baseline that allows VM portability, if
needed).
--
error compiling committee.c: too many arguments to function
