[arch-dev-public] [announcement] qemu/qemu-kvm announcement draft

Paul Mattal paul at mattal.com
Sat Jan 9 12:52:24 EST 2010


On 01/09/2010 12:49 PM, Tobias Powalowski wrote:
> Am Samstag 09 Januar 2010 schrieb Dan McGee:
>> On Sat, Jan 9, 2010 at 11:23 AM, Tobias Powalowski<t.powa at gmx.de>  wrote:
>>> Hi,
>>> since qemu/qemu-kvm 0.12.x  kqemu is no longer supported.
>>> kqemu package is removed from the repositories, if you still need kqemu
>>> support please compile 0.11 series and kqemu module yourself.
>>
>> A few things:
>>
>> * the contradictory message in the package itself:
>> [2010-01-08 19:01]>>>  Since kernel 2.6.29:
>> [2010-01-08 19:01]>>>  Qemu package now provides standard qemu with kvm
>>   enabled. [2010-01-08 19:01]
>> [2010-01-08 19:01]>>>  PLEASE READ FOR KVM USAGE!
>> [2010-01-08 19:01]>>>   Load the correct KVM module, you will need a
>> KVM capable CPU!
>> [2010-01-08 19:01]>>>   Add yourself to the group 'kvm'.
>> [2010-01-08 19:01]>>>   Use 'qemu --enable-kvm' to use KVM.
>> [2010-01-08 19:01]
>> [2010-01-08 19:01]>>>  PLEASE READ FOR KQEMU USAGE!
>> [2010-01-08 19:01]>>>  You need to install the 'kqemu' package for your
>>   kernel. [2010-01-08 19:01]>>>  You need to load the module to use qemu
>>   with kqemu. [2010-01-08 19:01] upgraded qemu (0.11.1-1 ->  0.12.1-1)
>>
>> * Let's use proper punctuation and capitalization around here. How about
>>   this: With the release of qemu and qemu-kvm 0.12.X, the kqemu kernel
>>   module is no longer supported and will be removed from the repositories.
>>   You can safely uninstall it from your system.
>>
>> * I had a hard time finding upstream documentation as to why this
>> deprecation happened, but I am guessing it is because KVM is the new
>> hotness. If that is correct, it might not hurt to add that to the note
>> as well.
>>
>> -Dan
>>
> Yes will change the install message.
> Yes there is no mention in the changelogs, really strange.
> greetings
> tpowa

I follow qemu/kvm and was totally blindsided by this, but eventually dug 
this out. Sounds like it's just that nobody wanted to support it and it 
was starting to cause real problems, which is totally reasonable, but it 
was not very well publicized:

https://bugs.launchpad.net/qemu/+bug/493519

Doesn't kvm still require that you have virtualization support in your 
processor? That was the remaining benefit of kqemu-- for people who 
didn't have the processor instructions.

- P




More information about the arch-dev-public mailing list