Created attachment 334154 [details] Boot log until hang Description of problem: Trying to boot a F10 i386 guest hanging somewhere around setting up IRC routing. If you disable ACPI it will work, but obviously that's not desirable for many other reasons. Once it hangs, QEMU is totally non-reponsible, not even to new VNC connections, so seems to be live-locked, or stuck in some emulation never processing i/o from the VNC server Version-Release number of selected component (if applicable): qemu-0.9.2-0.1.kvm20090303git.fc11.x86_64 How reproducible: Always Steps to Reproduce: 1. Download F10 i386 kernel + initrd from $OSTREE/images/pxeboot 2. Run /usr/bin/qemu-kvm -hda /var/lib/libvirt/images/demo.img -kernel /root/vmlinuz -initrd /root/initrd.img -vnc :1 -serial stdio -append "console=ttyS0" 3. Actual results: Hangs initializing ACPI Expected results: Boots installer Additional info:
I've hit this same problem with F11 guests too.
should be working by now. Please tell me if it's not.
I updated to the latest available qemu on koji, restarted the qemu service. but still the same error here.
Actually after a system reboot, i got another issue: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc -m 2045 - smp 1 -name mybooksdb2 -uuid a01adfdf-4016-f9b9-6b87-b0c48617c1ec -monitor pty - pidfile /var/run/libvirt/qemu//mybooksdb2.pid -no-reboot -boot d -drive file=/de v/sr0,if=ide,media=cdrom,index=2 -drive file=/dev/sdb2,if=virtio,index=0 -net ni c,macaddr=54:52:00:2f:23:42,vlan=0,model=virtio -net tap,fd=18,script=,vlan=0,if name=vnet0 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:0 -k en-us -soundhw es1370 char device redirected to /dev/pts/1 char device redirected to /dev/pts/2 Could not read keymap file: '/usr/share/kvm/keymaps/en-us' Unable to complete install '<class 'libvirt.libvirtError'> internal error unable to start guest: char device redirected to /dev/pts/1 char device redirected to /dev/pts/2 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1485, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 973, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: char device redirected to /dev/pts/1 char device redirected to /dev/pts/2 '
Ok, this is finally booting F10/11 correctly in the build qemu-0.10-0.9.kvm20090310git.fc11.x86_64
I can start a installation now but i have not been able to complete one yet. I've tried four times and each time it hangs on some point in the installation process.
Think this was the fix: * Tue Mar 10 2009 Glauber Costa <glommer> - 2:0.10-0.5.kvm20090303git ... - build kvm's own bios. It is still necessary while kvm uses a slightly different irq routing mechanism Presumably the plan is to resolve the differences ...
Yeah, precisely. However, this plan is not Targeted at F11. I don't see a drawback of using kvm's bios , tough.
Reopening ... I don't think this is fixed. I'm seeing qemu hanging like this with: guest kernel 2.6.29.3-155.fc11.x86_64 (NB architecture) qemu-kvm-0.10-16.fc11.x86_64 This fails running qemu inside Koji. The x86-64 task here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1368831 I will attach the build log.
Created attachment 344992 [details] build log
I should add that the BIOS version is: bochs-bios 2.3.8-0.6.git04387139e3b.fc11 I don't think this can be a BIOS mismatch because this is using the latest package from F-11.
I've created a new bug for this: bug 502058