When I try to emerge qemu v.0.7 with kqemu use enabled, the kernel module can't link: [...] make[2]: Entering directory `/usr/src/linux-2.6.11-gentoo-r6' CC [M] /var/tmp/portage/qemu-0.7.0/work/qemu-0.7.0/kqemu/kmod.o cp /var/tmp/portage/qemu-0.7.0/work/qemu-0.7.0/kqemu/kqemu-mod-i386.o /var/tmp/portage/qemu-0.7.0/work/qemu-0.7.0/kqemu/kqemu-mod.o LD [M] /var/tmp/portage/qemu-0.7.0/work/qemu-0.7.0/kqemu/kqemu.o ld: Relocatable linking with relocations from format elf32-i386 (/var/tmp/portage/qemu-0.7.0/work/qemu-0.7.0/kqemu/kqemu-mod.o) to format elf64-x86-64 (/var/tmp/portage/qemu-0.7.0/work/qemu-0.7.0/kqemu/kqemu.o) is not supported Reproducible: Always Steps to Reproduce: 1. buy an athlon64 & install gentoo 2005.0 64bit edition 2. set the use kqemu 3. emerge qemu Actual Results: build failed Expected Results: build success Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r6 x86_64) ================================================================= System uname: 2.6.11-gentoo-r6 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 30 2005, 20:48:02)] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox strict" GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ http://gentoo.mirror.solnet.ch http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LINGUAS="it" MAKEOPTS="-j2" PKGDIR="/packages/amd64" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 X aac acpi alsa artworkextra avi bash-completion berkdb bitmap-fonts ccache cdda cddb cdparanoia cdr codecs crypt cups curl dga directfb dvd dvdread edl eds emoticon encode esd exif fam fbcon flac font-server foomaticdb fortran gcj gdbm gif gimpprint gmail gnome gnomedb gphoto2 gpm graphviz gstreamer gtk gtk2 hal imagemagick imlib innodb ipv6 java jce jikes jp2 jpeg jpeg2k junit kde ldap libcaca libwww lm_sensors logitech-mouse lzo lzw lzw-tiff mad matroska mng motif mozilla mozsvg mp3 mpeg mysql ncurses nls nptl nvidia ogg oggvorbis openal opengl oss pam pdflib perl png ppds python qt quicktime readline real rtc samba sdl speex spell sql sqlite ssl subversion svg sysfs tcltk tcpd tetex tga theora tiff truetype truetype-fonts type1 type1-fonts usb userlocales vcd vorbis wmf xanim xfs xml2 xpm xrandr xscreensaver xv xvid zeroconf zlib linguas_it" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
kqemu should be available JUST on x86, it will be masked soon for the other arches.
QEMU version 0.7.1 is out (Changelog). * The QEMU Accelerator now supports x86 and x86_64 hosts. On x86_64 32 or 64 bit user code is executed natively. A preliminary version is available for Windows too. * The PowerPC target begins to launch the Mac OS X installer. * Many fixes have been done for 64 bit targets (x86_64, SPARC64). * A new MIPS target is available for the developpers. So kqemu is available for 64bit architecture and it shouldn't be masked for amd64.
Hi - I just enabled the kqemu useflag in my amd64 profile, and modified the ebuild to use the -1 release of kqemu. I'm using a full 64 bit gentoo with kernel 2.6.12 BTW. With 0.7.1 it does compile and appears to be running using it (Note! You need to use 'qemu-system-x86_64' and NOT 'qemu' to run a full system emulation using kqemu). Unfortunately the test install of XP I was doing has died (in the VM only - my host linux is fine :) . I will continue investigating though.
I'll update the ebuild to the kqemu .1-1 soon, amd64 people please test and unmask the flag, please
I just tried installing Win2K with qemu-0.7.1 and the kqemu module loaded. It crashes my amd64 machine during the loading of Windows! It suddenly hangs.
Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-gentoo-r6 x86_64). nForce3-250 (MSI Neo Platinum), a64 3400+, 1G of good RAM, stock speeds (for now). I can definitely confirm Martin's results. Booting an image with XP Pro on it (the image was created with a non-kqemu-enabled qemu) caused my system to instantly restart, shortly after the XP boot screen faded in.
Confirming as well: compiled qemu/kqemu 0.7.1 by hand and my system locks up or reboots with all the livecd or windows images I have using qemu-system-x86_64. Have not tried any other amd64 distros. Wonder if it is Gentoo related?
*** Bug 105583 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > *** Bug 105583 has been marked as a duplicate of this bug. *** With qemu-0.7.2 on AMD64, gentoo-sources-2.6.13, the kqemu module works perfectly. So far I have installed WinXP, Win2k and Gentoo inside a manually installed qemu-0.7.2 VM, and it all works fine with the kqemu module loaded and I can cleary see a speed improvement. Why is the kqemu USE flag blocked for AMD64 then?
Basically because I couldn't test it and on the .7.1 I got reports about every sort of problems. amd64 team tell me something. I will try to test it myself in a way or another in the next week.
We can't de-usemask kqemu until 0.7.0 and 0.7.1 are in tree. In the mean time the workaround is just to do echo "-kqemu" >> /etc/portage/profile/use.mask to un-mask kqemu flag.
*** Bug 110074 has been marked as a duplicate of this bug. ***
please drop the amd64 flag on them and stabilize the 7.2 I'll stabilize it on ppc soon
luca, 0.7.2 works fine here with kqemu, but it was not even 2 weeks in ~, so i'll wait with marking stable
I can double the kqemu running well winXPpro with cygwin and compiling my stuff happily
Forgot to say version 0.7.2
It's been pleanty of time, and it's stable for me, on amd64. lu_zero, should we stabilize?
For me is stable. Please remove ~amd64 to every other ebuild beside the ones that have kqemu working and unmask kqemu
Done. 0.7.2 is stable on amd64, kqemu is unmasked, and all the rest have no amd64 keyword.
