KVM paravirtualization on non-VMX/SVM CPUs?
In January, Ingo Molnar announced "KVM paravirtualization for Linux"[1].
The announcement mentions "support for the hardware cr3-cache feature of Intel-VMX CPUs" and "i only tested this on 32-bit VMX".
Because of this, I'm not sure how to understand it:
1) KVM paravirtualization means that it will be possible to use KVM on non-VMX/SVM CPUs (much like Xen)?
2) KVM paravirtualization means paravirtualized drivers only (net, disk etc.), but it will still run only on VMX/SVM-capable CPUs?
Which one is true? First, or second?
[1] http://people.redhat.com/mingo/kvm-paravirt-patches/ANNOUNCE
Signature · 8 lines
Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
A message that is not in the archive (sent off-list or not yet received): 45FEBC41.6060802-Nem3ZqsbT/[email protected]
Quoted 7 lines · Tomasz Chmielewski
In January, Ingo Molnar announced "KVM paravirtualization for Linux"[1].
The announcement mentions "support for the hardware cr3-cache feature of Intel-VMX CPUs" and "i only tested this on 32-bit VMX".
Because of this, I'm not sure how to understand it:
Quoted 8 lines
1) KVM paravirtualization means that it will be possible to use KVM on non-VMX/SVM CPUs (much like Xen)?
2) KVM paravirtualization means paravirtualized drivers only (net, disk etc.), but it will still run only on VMX/SVM-capable CPUs?
Which one is true? First, or second?
The latter. I asked this question several weeks ago. The response
was that it "would be nice" for KVM to support non-VMX machines, but that it wasn't a priority in any way for any of the current developers.
My understanding is that the paravirtualisation support that Ingo
wrote is purely for performance purposes, bypassing the hardware emulation layer in qemu and going directly to the host VM's device layer.
Hugo.
Signature · 4 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- If it's December 1941 in Casablanca, what time is it ---
in New York? -------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Quoted 10 lines · Tomasz Chmielewski
In January, Ingo Molnar announced "KVM paravirtualization for Linux"[1].
The announcement mentions "support for the hardware cr3-cache feature of Intel-VMX CPUs" and "i only tested this on 32-bit VMX".
Because of this, I'm not sure how to understand it:
1) KVM paravirtualization means that it will be possible to use KVM on non-VMX/SVM CPUs (much like Xen)?
No. That is possible (and kqemu demonstrates it can be done), but it is not implemented and to my knowledge no one is working on it.
Quoted 5 lines
2) KVM paravirtualization means paravirtualized drivers only (net, disk etc.), but it will still run only on VMX/SVM-capable CPUs?
Yes. In addition, it enables platform-level optimization (like the cr3 cache).
Signature · 8 lines
error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV