View previous topic :: View next topic |
Author |
Message |
NuMPTy Tux's lil' helper
Joined: 04 Mar 2012 Posts: 78
|
Posted: Wed Oct 10, 2012 12:29 pm Post subject: Emerging qemu fails due to seabios block |
|
|
Hi Everyone,
I'm trying to install qemu 'fresh' and it seems it's being blocked by a dep:
Code: | # emerge -avq qemu
[ebuild N ] sys-firmware/sgabios-0.1_pre8
[ebuild N ] sys-devel/bin86-0.16.18
[ebuild N ] net-misc/vde-2.3.1 USE="ssl -pcap -static-libs"
[ebuild N ] sys-firmware/seabios-1.7.0
[ebuild N ] sys-devel/dev86-0.16.18
[ebuild N ] sys-firmware/vgabios-0.7a USE="-debug"
[ebuild N ] app-emulation/qemu-1.1.2 USE="aio alsa bluetooth caps curl ncurses opengl python sdl vde vhost-net -brltty -debug -doc -fdt -mixemu -pulseaudio -rbd -sasl -smartcard -spice -static -systemtap -tci -tls -usbredir -virtfs -xattr -xen -xfs" QEMU_SOFTMMU_TARGETS="i386 -alpha -arm -cris -lm32 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -ppc -ppc64 -ppcemb -s390x -sh4 -sh4eb -sparc -sparc64 -x86_64 -xtensa -xtensaeb" QEMU_USER_TARGETS="-alpha -arm -armeb -cris -i386 -m68k -microblaze -microblazeel -mips -mipsel -ppc -ppc64 -ppc64abi32 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -unicore32 -x86_64"
[blocks B ] app-emulation/qemu ("app-emulation/qemu" is blocking sys-firmware/seabios-1.7.0)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(app-emulation/qemu-1.1.2::gentoo, ebuild scheduled for merge) pulled in by
qemu
|
Any ideas on how to circumvent this? seabios is pretty necessary :\ |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21635
|
Posted: Thu Oct 11, 2012 1:25 am Post subject: |
|
|
What is the output of emerge --pretend --verbose --deep --tree app-emulation/qemu? Why are you using app-emulation/qemu instead of app-emulation/qemu-kvm? |
|
Back to top |
|
|
miket Guru
Joined: 28 Apr 2007 Posts: 488 Location: Gainesville, FL, USA
|
Posted: Thu Oct 11, 2012 2:12 am Post subject: |
|
|
Hu wrote: | Why are you using app-emulation/qemu instead of app-emulation/qemu-kvm? |
That has everything to do with the fact that just today they dropped app-emulation/qemu-kvm from the tree and merged it into app-emulation/qemu.
I don't have a problem with that; actually the merge makes a lot of sense.
What does not make sense, though, is what is supposed to happen with the USE flags. I *think*, from looking at the ebuild, that app-emulation/qemu-1.1.1-r1 uses that it enables KVM if there is a soft target of x86_64, but that's not super clear to me.
I don't know, but I'm afraid they may have jumped the gun in removing app-emulation/qemu-kvm. |
|
Back to top |
|
|
NuMPTy Tux's lil' helper
Joined: 04 Mar 2012 Posts: 78
|
Posted: Thu Oct 11, 2012 10:51 am Post subject: |
|
|
Thank you for the replies!
I'm using qemu instead of qemu-kvm for simulating Cisco ASAs, and as far as I know 'qemu' is what is required, not qemu-kvm
Code: | $ emerge --pretend --verbose --deep --tree app-emulation/qemu
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
[ebuild N ] app-emulation/qemu-1.1.2 USE="aio alsa bluetooth caps curl ncurses opengl python sdl vde vhost-net -brltty -debug -doc -fdt -mixemu -pulseaudio -rbd -sasl -smartcard -spice -static -systemtap -tci -tls -usbredir -virtfs -xattr -xen -xfs" QEMU_SOFTMMU_TARGETS="i386 -alpha -arm -cris -lm32 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -ppc -ppc64 -ppcemb -s390x -sh4 -sh4eb -sparc -sparc64 -x86_64 -xtensa -xtensaeb" QEMU_USER_TARGETS="-alpha -arm -armeb -cris -i386 -m68k -microblaze -microblazeel -mips -mipsel -ppc -ppc64 -ppc64abi32 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -unicore32 -x86_64" 6,451 kB
[ebuild N ] sys-firmware/seabios-1.7.0 0 kB
[ebuild N ] net-misc/vde-2.3.1 USE="ssl -pcap -static-libs" 499 kB
[ebuild N ] sys-firmware/vgabios-0.7a USE="-debug" 1,474 kB
[ebuild N ] sys-devel/dev86-0.16.18 689 kB
[ebuild N ] sys-devel/bin86-0.16.18 143 kB
[ebuild N ] sys-firmware/sgabios-0.1_pre8 30 kB
[blocks B ] app-emulation/qemu ("app-emulation/qemu" is blocking sys-firmware/seabios-1.7.0)
Total: 7 packages (7 new), Size of downloads: 9,284 kB
Conflict: 1 block (1 unsatisfied)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(app-emulation/qemu-1.1.2::gentoo, ebuild scheduled for merge) pulled in by
app-emulation/qemu
For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked
|
|
|
Back to top |
|
|
NuMPTy Tux's lil' helper
Joined: 04 Mar 2012 Posts: 78
|
Posted: Thu Oct 11, 2012 11:13 am Post subject: |
|
|
and..............after a quick --sync && portage update it doesn't seem to be a problem anymore:
Code: | # emerge -avq qemu
[ebuild N ] sys-firmware/sgabios-0.1_pre8
[ebuild N ] sys-devel/bin86-0.16.18
[ebuild N ] net-misc/vde-2.3.1 USE="ssl -pcap -static-libs"
[ebuild N ] sys-firmware/seabios-1.7.0
[ebuild N ] sys-devel/dev86-0.16.18
[ebuild N ] sys-firmware/vgabios-0.7a USE="-debug"
[ebuild N ] app-emulation/qemu-1.1.2 USE="aio alsa bluetooth caps curl jpeg ncurses opengl png python sdl threads uuid vde vhost-net vnc -brltty -debug -doc -fdt -mixemu -pulseaudio -rbd -sasl -smartcard -spice -static -systemtap -tci -tls -usbredir -virtfs -xattr -xen -xfs" QEMU_SOFTMMU_TARGETS="i386 -alpha -arm -cris -lm32 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -ppc -ppc64 -ppcemb -s390x -sh4 -sh4eb -sparc -sparc64 -x86_64 -xtensa -xtensaeb" QEMU_USER_TARGETS="-alpha -arm -armeb -cris -i386 -m68k -microblaze -microblazeel -mips -mipsel -ppc -ppc64 -ppc64abi32 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -unicore32 -x86_64"
Would you like to merge these packages? [Yes/No] Yes
|
|
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21635
|
Posted: Fri Oct 12, 2012 1:44 am Post subject: |
|
|
miket wrote: | Hu wrote: | Why are you using app-emulation/qemu instead of app-emulation/qemu-kvm? |
That has everything to do with the fact that just today they dropped app-emulation/qemu-kvm from the tree and merged it into app-emulation/qemu.
I don't know, but I'm afraid they may have jumped the gun in removing app-emulation/qemu-kvm. | Good catch. I had not synced since before the move, so it had not appeared to me yet. From looking at the ebuilds, it looks like qemu-kvm was renamed to qemu. The qemu ebuild now fetches the same source paths previously used by qemu-kvm, so it looks like the change is mostly cosmetic at this point. |
|
Back to top |
|
|
|