stabilize =sys-apps/seabios-1.7.0 target keywords: amd64 x86
Builds fine on x86. Unable to test further. Please mark stable for x86.
x86: ok i'm make only compile and check with repoman Please mark stable for x86.
I see a small issue : https://forums.gentoo.org/viewtopic-p-7098888.html#7098888
(In reply to comment #3) > I see a small issue : > https://forums.gentoo.org/viewtopic-p-7098888.html#7098888 I have no idea what you're trying to say in the forum post.
(In reply to comment #3) > I see a small issue : > https://forums.gentoo.org/viewtopic-p-7098888.html#7098888 My only guess is that you're complaining that you had an issue where a VM started via virt-manager through libvirt started qemu-kvm with -L /usr/share/kvm. Your domain (VM) XML has this set as an argument to pass to QEMU, which is definitely something you want to remove because its not correct for Gentoo, Fedora/RHEL/CentOS, or Debian/Ubuntu and if you plan on migrating your VMs it won't work. Don't create the symlink. Just remove the extra configs that are bad. Now its possible you don't have it in your XML. Back before qemu-kvm when it was called "kvm" and before Gentoo had really added support for kvm. There were a few guides that talked how to install kvm. They had you write a wrapper script which was called /usr/local/bin/kvm. It set a number of arguments (like -L). Now when I started adding KVM support to Gentoo I had the ebuild install /usr/bin/kvm, which meant from a PATH perspective the old script was invisible. Now at the request of upstream I dropped /usr/bin/kvm recently in qemu-kvm. Which means if you had that old script in /usr/local/bin/kvm, it might still be used. The qemu-kvm and libvirt ebuilds tell people to ensure they're not using "kvm" as the binary but to be using "/usr/bin/qemu-kvm" or "/usr/bin/qemu-system-x86_64". Effectively, if I'm understanding your issue, its a configuration problem.
x86 stable, thanks Mikle and Myckel
amd64 stable. Last arch, closing