© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Thanks for the report. We've gotten a few requests about this over the last few weeks. I need to respond to all of those here.
Upstream QEMU has configured kqemu off by default for 0.11, and has completely removed the code from the tree for 0.12. This is upstream's acknowledgement that kqemu is simply unsupportable.
We, Ubuntu, could conceivably ./configure --enable-kqemu for the qemu-kvm-0.11 package in Karmic, however, this would introduce (as I see it) two serious problems...
1) We would be shipping code (in main nonetheless) that upstream is consciously and vocally refusing to support. I think this unwise, at best. We wouldn't get any help fixing/supporting issues (even security vulnerabilities) that come up.
2) And more importantly, enabling kqemu has a *detrimental* effect on ALL Ubuntu KVM users... Enabling kqemu limits the amount of physical memory to VM guests to ~3.5GB. This is something I feel strongly about. Karmic will be around for another 1.5 years, in which we can expect hosts memory to double (at least).
I am very open to the possibility of a community maintained qemu-kvm (+kqemu) package in the ubuntu-virt PPA.
:-Dustin