Description of problem: Installation of RHEL-3.9-32 hung. Formating disk and package installation are all completed. And installation of RHEL-3.9-64 is ok. Version-Release number of selected component (if applicable): # uname -a Linux amd-2427-32-2.englab.nay.redhat.com 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa |grep kvm kvm-83-170.el5 etherboot-zroms-kvm-5.4.4-13.el5 kvm-qemu-img-83-170.el5 kvm-debuginfo-83-170.el5 kmod-kvm-83-170.el5 kvm-tools-83-170.el5 How reproducible: always Steps to Reproduce: 1. install RHEL-3.9-32 guest Actual results: installation hung Expected results: installation can complete Additional info: commandline: # /root/autotest/client/tests/kvm/qemu -name 'vm1' -monitor tcp:0:6001,server,nowait -drive file=/root/autotest/client/tests/kvm/images/RHEL-3.9-32.raw,if=ide,cache=writethrough,boot=on -net nic,vlan=0,model=e1000,macaddr=00:11:22:33:50:01 -net user,vlan=0 -m 33792 -smp 12 -drive file=/root/autotest/client/tests/kvm/isos/linux/RHEL3.9-i386-DVD.iso,index=2,media=cdrom -soundhw ac97 -fda /root/autotest/client/tests/kvm/images/floppy.img -tftp /root/autotest/client/tests/kvm/images/tftpboot -usbdevice tablet -rtc-td-hack -no-hpet -cpu qemu64,+sse2 -no-kvm-pit-reinjection -bootp /pxelinux.0 -boot n -redir tcp:5000::22 -redir tcp:5001::12323 -vnc :0
Created attachment 406171 [details] Packages installation, it can be completed 100%
Created attachment 406172 [details] After packages installation, guest hung
This bug can also be reproduced when using this command line. # qemu-kvm -name 'vm1' -monitor tcp:0:6001,server,nowait -drive file=/root/autotest/client/tests/kvm/images/RHEL-3.9-32.qcow2,if=ide,cache=off,boot=on -net nic,vlan=0,model=e1000,macaddr=00:11:22:33:0f:a9 -net user,vlan=0 -m 33792 -smp 12 -drive file=/root/autotest/client/tests/kvm/isos/linux/RHEL3.9-i386-DVD.iso,index=2,media=cdrom -fda /root/autotest/client/tests/kvm/images/floppy.img -tftp /root/autotest/client/tests/kvm/images/tftpboot -bootp /pxelinux.0 -boot n -vnc :0
Kickstart can be found here: http://github.com/ehabkost/autotest/tree/master/client/tests/kvm/unattended/ The problem happens because it's simply not possible to bring the network up at post install stage so the install can communicate with the host to respond that its installation finished. It may be an anaconda bug on that particular RHEL version.
rhel4 installion also hang qemu: qemu-img-0.12.1.2-2.72.el6.x86_64 kernel: 2.6.32-33.el6.x86_64 command: /usr/libexec/qemu-kvm -name 'vm1' -monitor tcp:0:6001,server,nowait -drive file=/usr/client/tests/kvm/images/RHEL-4.8-32.qcow2,if=ide,cache=none,boot=on,aio=native -net nic,vlan=0,model=e1000,macaddr=02:30:7C:AF:37:cd -net user,vlan=0 -m 2048 -smp 2 -drive file=/usr/isos/linux/RHEL4.8-i386-AS-DVD.iso,index=2,media=cdrom -soundhw ac97 -fda /usr/images/floppy.img -tftp /usr/images/tftpboot -redir tcp:5000::22 -redir tcp:5002::12323 -vnc :0 -usbdevice tablet -rtc-td-hack -cpu qemu64,+sse2 -no-kvm-pit-reinjection -bootp /pxelinux.0 -boot n -serial unix:/tmp/serial-20100611-191801-1ruL,server,nowait
Is it reproducible without qemu's tftp server? 1. With real rhel3 iso 2. With real pxe server
(In reply to comment #7) > Is it reproducible without qemu's tftp server? > 1. With real rhel3 iso result: PASS ( manual) cmdline: qemu-kvm -name vm1 -monitor unix:/tmp/monitor-humanmonitor1-20101124-180901-LAjn,server,nowait -serial unix:/tmp/serial-20101124-180901-LAjn,server,nowait -drive file=/home/devel/autotest-devel/client/tests/kvm/images/RHEL-3.9-32-virtio.qcow2,index=0,if=ide,media=disk,cache=none,format=qcow2 -net nic,vlan=0,model=e1000,macaddr=9a:72:41:20:f4:18 -net tap,vlan=0,ifname=t0-180901-LAjn,script=/home/devel/autotest-devel/client/tests/kvm/scripts/qemu-ifup-vbr0,downscript=no -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive file=/home/devel/autotest-devel/client/tests/kvm/isos/linux/RHEL3.9-i386-DVD.iso,media=cdrom,index=2 -cpu qemu64,+sse2 -soundhw ac97 -spice port=8000,disable-ticketing -qxl 1 -rtc-td-hack -M rhel5.6.0 -usbdevice tablet -no-kvm-pit-reinjection -boot d > 2. With real pxe server result: FAIL (kickstart) (will attach the kickstar file) cmdline: /home/devel/autotest-devel/client/tests/kvm/qemu -name 'vm1' -monitor unix:'/tmp/monitor-humanmonitor1-20101124-180901-LAjn',server,nowait -serial unix:'/tmp/serial-20101124-180901-LAjn',server,nowait -drive file='/home/devel/autotest-devel/client/tests/kvm/images/RHEL-3.9-32-virtio.qcow2',index=0,if=ide,media=disk,cache=none,format=qcow2 -net nic,vlan=0,model=e1000,macaddr='9a:72:41:20:f4:18' -net tap,vlan=0,ifname='t0-180901-LAjn',script='/home/devel/autotest-devel/client/tests/kvm/scripts/qemu-ifup-switch',downscript='no' -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive file='/home/devel/autotest-devel/client/tests/kvm/isos/linux/RHEL3.9-i386-DVD.iso',media=cdrom,index=2 -cpu qemu64,+sse2 -soundhw ac97 -spice port=8000,disable-ticketing -qxl 1 -rtc-td-hack -M rhel5.6.0 -usbdevice tablet -no-kvm-pit-reinjection -boot n
Created attachment 462989 [details] kickstart file of rhel39.32
Glauber can you please have a look? Amos, does it work over rhel6 host?
(In reply to comment #10) > Glauber can you please have a look? > Amos, does it work over rhel6 host? doesn't work, the phenomenon is same.
Has another emulated NIC been tried, i.e., rtl8139 ?
(In reply to comment #14) > Has another emulated NIC been tried, i.e., rtl8139 ? can reproduced.
*** Bug 654551 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release.
Created attachment 488084 [details] Trace output when installation hangs