There should be an ebuild for qemu-kvm-0.10.5 (http://sourceforge.net/projects/kvm/files/qemu-kvm/qemu-kvm-0.10.5.tar.gz). It contains a bunch of bugfixes and performance improvements compared to the stock qemu with kvm useflag. Afaik this is the recommended userspace tool for KVM in a production environment, so this should go into the tree ... Best regards, Fabian Henze Reproducible: Always
lu_zero: qemu is yours, not sure if you want to add this.
I'd like to know if would be possible having an extracted patch with the changes first and how different would be since we already have qemu and kvm
(In reply to comment #2) > I'd like to know if would be possible having an extracted patch with the > changes first and how different would be since we already have qemu and kvm I tried that: tar xf qemu-0.10.5.tar.bz2 tar xf qemu-kvm-0.10.5.tar.bz2 diff -pruN qemu-0.10.5 qemu-kvm-0.10.5 The resulting patch seems to work, but causes trouble under certain circumstances ... I had to build the patched qemu with: QEMU_SOFTMMU_TARGETS="-ppc -ppc64 -ppcemb" and QEMU_USER_TARGETS="-i386 -ppc -ppc64 -ppc64abi32 -x86_64". While this is okay, if one just needs kvm it's not such a good idea for the normal qemu ebuild. Maybe its better to add a app-emulation/kvm-0.10.5 ebuild to the tree?
Created attachment 201166 [details] ebuild for 0.10.6 I have created an ebuild (based on the existing kvm-88 ebuild), it's not well tested but works here, YMMV.
(In reply to comment #2) > I'd like to know if would be possible having an extracted patch with the > changes first and how different would be since we already have qemu and kvm > <quote from http://www.linux-kvm.org/page/Code#release_tags> kvm stable releases (based off of Qemu's stable branch) are tagged with kvm-qemu-0.NN.N where N equates to the upstream Qemu branch versions. Note that kvm has them tagged not branched. kvm development releases are tagged with kvm-nn where nn is the release number. </quote> So the only question I can think of is why you chooses to have the development-releases and not the stable in portage?
I'm not the kvm maintainer, let me add him to the bug =)
any news on this? qemu-kvm is the new "stable" releases, and should really be what people use..
Please don't upload ebuilds in tarballs. :) Some issues here. We need an updated kvm-kmod ebuild. The new version numbers are less than the old ones. I've also found that this collides with regular qemu, though I think it's only on the qemu-io executable. I recommend that qemu and kvm have the same maintainer since there's so much overlap.
Luca: qemu-kvm is merely just a series of fixes on top of qemu for kvm support. I'm thinking we pretty much start using qemu-kvm as the ~arch package while qemu itself can be stable.
basic version of this is now in the tree
