Dong, Eddie wrote: > Avi Kivity wrote: > >> Dong, Eddie wrote: >> >>> Use host cpu model name, type, family, Model, stepping for guest. >>> >>> Against head. >>> >>> >>> >> This is turning into a mix of the qemu cpuid and the host cpuid. We >> need to think of a way to make this controllable. >> >> > Actually I am wondering why we need a Qemu CPUID. A basic concept of > virtualization is that good user software (following ABI) will not know > if it is running in VM or natively. But now with qemu cpuid, any > application knows "I am running in a VM". Is that really what we want? >
One of the uses of virtualization is to abstract the underlying hardware, so that a VM image can run on any platform (live migration is an example of this use case). For that we must not let any detail of the hardware be visible. On the other hand, other users (desktop users, or users with homogeneous server farms) will want to use the full capabilities of the hardware, requiring the host cpuid to be exposed. We need to support both use cases. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
