-2

can some one please clarify this.

I am new to kvm and created two guest instances one linux and one windows.

On both Guests, CPU is showing as QEMU virtual CPU,why is it so?

if kvm utilizes hardware virtualization and Qemu an emulator then what is the role of kvm in virtualization,since in this case its showing only emulated cpu,which i believe is the work of Qemu and not kvm.

On xen, which i am familiar guests cpu are shown as it like an actual hardware,even if it is using qemu drivers.

closed as not a real question by Tom O'Connor, Rob Moir, mgorven, mdpc, Khaled Mar 1 '13 at 18:10

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

2

By default, QEMU/KVM exposes only a subset of CPU features to guests, so that a VM can be migrated from one CPU to another (e.g. from an Intel Xeon to an AMD Opteron) without any ill effects.

You can override this behavior if you wish, by passing parameters on the qemu command line, or setting the appropriate CPU options in your GUI/XML front end. You can select specific CPU features to expose, or to pass through all CPU features.

If you choose to override any of the parameters, then you will only be able to migrate the VM to another CPU which also has those features. If you choose to pass all host CPU features to the guest, then it will also expose the name of the CPU, and you will be unable to migrate the VM to a CPU of a different type.

The difference between QEMU and KVM is that QEMU is full processor emulation, while KVM provides full hardware virtualization (HVM) using the processor's native virtualization capability (Intel VT-x or AMD SVM) to provide near-native CPU performance. As a result, the former is much slower than the latter.

  • It's also worth pointing out that QEMU doesn't do anything that KVM can do better. If QEMU doesn't need to emulate it (e.g. x86 guest on x86 host with Intel VT) then it won't. QEMU provides an abstraction layer between things it has to emulate and things KVM can run through full hardware virtualisation. In essence, by running QEMU, as long as you tweak the guest and host, you'll be running as optimised with as much virtualisation features, compatibility and stability as possible. – NotoriousPyro Jul 4 '17 at 16:11
0

What's in a name? that which we call a rose

By any other name would smell as sweet;

And so also true of virtualised CPUs.

  • Definitely i am not the one who gave - to your answer :).It looks like there are people who have this doubt. – kevin Feb 28 '13 at 8:51
  • 1
    Eh. Some people are tossers. – Tom O'Connor Feb 28 '13 at 9:07
0

qemu a user space program emulates hosts hardware utilizing /dev/kvm interface.KVM itself doesnot have any capability to emulate.

  • This does not answer my question fully,but got some idea. – kevin Feb 28 '13 at 9:57

Not the answer you're looking for? Browse other questions tagged or ask your own question.