Bug 470866

Just an added note: I was able to complete the installation when I use the option to boot from local kernel instead boot.iso. Below is the complete command I used:

/usr/bin/qemu-kvm -kernel /a/m/sf/dev/x86_64/os/isolinux/vmlinuz -initrd /a/m/sf/dev/x86_64/os/isolinux/initrd.img -append "ksdevice=52:55:00:03:28:40 ks=http://192.168.5.103/a/ks/fdb0-38740" -drive file=/a/i/fdb0,boot=on  -net nic,vlan=8740,macaddr=52:55:00:03:28:40 -net user,vlan=8740,hostname=fdb0-38740 -name fdb0-38740 -localtime -usbdevice tablet -vnc :2840 -monitor stdio -m 512

kickstart file:
# (fda0-37740)/a/ks/fda0-37740
# Mon Nov 10 13:49:45 EST 2008
keyboard us
lang en_US.UTF-8
timezone  America/New_York
rootpw install
user --name=adm0 --uid=500 --password=install
network --bootproto dhcp --hostname fda0-37740
url --url http://192.168.5.103/a/m/sf/dev/i386/os/


command executed from local console( as a viewer):
vncviewer :7740 -name fda0-37740

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

*** Bug 499794 has been marked as a duplicate of this bug. ***

*** Bug 499794 has been marked as a duplicate of this bug. ***

I have the same problem with Fedora 11 Preview.
Text installation works.

Catalin: could you include the full command line you used for qemu-kvm? Also, include the version of qemu you tested with and any messages printed by qemu or any messages logged to syslog during the install

Moving the bug to Fedora 11 - we've more chance of getting this debugged and fixed in F11

Mark, sorry about not providing all information.
I am using Fedora 10, up-to-date.
qemu-kvm: QEMU PC emulator version 0.9.1 (kvm-74).
Note, please, that the same thing I get also without using KVM!

Kernel: 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009 i686 i686 i386 GNU/Linux

Command line (without KVM):  qemu -m 512 -hda F11preview2.qcow2 -cdrom Fedora-11-Preview-i386-DVD.iso -net nic,macaddr=00:11:11:11:11:78 -net tap,script=run.net -boot d -usbdevice tablet

Command line (with kvm):  qemu-kvm -m 512 -drive file=F11preview2.qcow2,if=virtio,boot=on,cache=on -cdrom Fedora-11-Preview-i386-DVD.iso -net nic,macaddr=00:11:11:11:11:78,model=virtio -net tap,script=run.net -boot d -usbdevice tablet

Hope it helps!

If you need more info, let me know.

If you give me some hints on how to debug this thing, let me know.

Ah, okay - this is a Fedora 10 bug. I don't think we've seen reports of this on a Fedora 11 host

Image was created like this: qemu-img create -f qcow2 F11preview2.qcow2 10G
Host:
May 11 14:45:11 cboie kernel: kvm: guest NX capability removed
May 11 14:45:11 cboie kernel: kvm: guest NX capability removed
(yes, two times)

Guest:
Seems that the system gets stuck. I cannot issue any command on it. Is dead.

Hmm, I wonder is it in any way related to bug #499596?

Try running with qemu-kvm -cpu qemu32 ?

due to space/time limitation I can no longer test i386, but I know for sure that I'm able to install x86_64 w/ no problem as of the latest build (5/1/09) pulled from source. 

Not sure if this bug should closed or not.

Mark, it doesn't work with "-cpu qemu32".

I seem to experience the same behavior on F11, using virt-manager and mostly default options, if this can help:

Host is a T61 with the following from yesterday:
Fedora release 11 (Leonidas)
Linux localhost.localdomain 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

libvirt-0.6.2-11.fc11.x86_64
qemu-img-0.10.4-4.fc11.x86_64
qemu-kvm-0.10.4-4.fc11.x86_64
qemu-common-0.10.4-4.fc11.x86_64
qemu-system-x86-0.10.4-4.fc11.x86_64

selinux enforcing, iptables on

And trying to create a F11 x86_64 guest, using tree from dvd on laptop:

it created a /var/lib/libvirt/images/f11ms.img with the expected size, and target device vda, all good until near the end with an apparent never ending "Installing bootloader..."
The VM details are available just fine, but the guest does not seem to respond to for example a "send keys" to access another tty.

the process is like this on the host:

/usr/bin/qemu-kvm -S -M pc -m 512 -smp 1 -name f11ms -uuid e8068481-7e01-8d8f-48af-0df4d3a3abf2 -monitor pty -pidfile /var/run/libvirt/qemu//f11ms.pid -no-reboot -boot d -drive file=/dev/sr0,if=ide,media=cdrom,index=2 -drive file=/var/lib/libvirt/images/f11ms.img,if=virtio,index=0 -net nic,macaddr=54:52:00:4c:de:d6,vlan=0,model=virtio -net tap,fd=18,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:0

but the F11 guest did reboot properly after a forced shutdown, and install completed with a success (figured out after submitting previous comment, sorry)

Can anyone confirm this is a duplicate of bug #501412? Should be fixed with qemu-0.10.5-2.fc11 or later

I installed F12 Alpha on a F11 host and no stuck happened.
I think the bug can be closed.

Thanks