Hide Forgot
Description: In RHEL 6.1 system, RHEL 6.1 32bit guest will report "This hardware (or a combination thereof) is not supported by Red Hat" while install form url or nfs. If install with -smp 1 or in Intel host, it will works fine. Version-Release number of selected component (if applicable): 2.6.32-125.el6.x86_64 qemu-kvm: rpm -qa |grep qemu qemu-kvm-debuginfo-0.12.1.2-2.152.el6.x86_64 qemu-img-0.12.1.2-2.152.el6.x86_64 gpxe-roms-qemu-0.9.7-6.7.el6.noarch qemu-kvm-tools-0.12.1.2-2.152.el6.x86_64 qemu-kvm-0.12.1.2-2.152.el6.x86_64 How reproducible: always Steps to Reproduce: 1.Set up the env #/usr/sbin/brctl addbr vbr0; \ #echo 1 > /proc/sys/net/ipv6/conf/vbr0/disable_ipv6; \ #echo 1 > /proc/sys/net/ipv4/ip_forward; \ #/usr/sbin/brctl stp vbr0 on; \ #/usr/sbin/brctl setfd vbr0 0; \ #ifconfig vbr0 192.168.58.1; \ #ifconfig vbr0 up; \ #iptables -t nat -A POSTROUTING \ -s 192.168.58.254/24 ! -d 192.168.58.254/24 -j MASQUERADE; #dnsmasq --strict-order --bind-interfaces \ --listen-address 192.168.58.1 \ --dhcp-range 192.168.58.2,192.168.58.254 \ --enable-tftp --tftp-root /home/tests/kvm/images/tftpboot \ --dhcp-boot pxelinux.0 --dhcp-no-override 2. get the vmlinuz and initrd file from nfs or url url we use: http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL6.1-20110317.1/ 2.install guest with command line and guest will hang while boot up. /root/autotest-devel/client/tests/kvm/qemu -name 'vm1' -chardev socket,id=qmp_monitor_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20110329-101545-krkw,server,nowait -mon chardev=qmp_monitor_id_qmpmonitor1,mode=control -chardev socket,id=serial_id_20110329-101545-krkw,path=/tmp/serial-20110329-101545-krkw,server,nowait -device isa-serial,chardev=serial_id_20110329-101545-krkw -drive file='/root/autotest-devel/client/tests/kvm/images/RHEL-Server-6.1-32-virtio.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=qcow2,aio=native -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk1,id=virtio-disk1 -device e1000,netdev=idTsgooc,mac=9a:37:f3:8f:b1:92,id=ndev00idTsgooc,bus=pci.0,addr=0x3 -netdev tap,id=idTsgooc,ifname='t0-101545-krkw',script='/root/autotest-devel/client/tests/kvm/scripts/qemu-ifup-switch',downscript='no' -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive file='/root/autotest-devel/client/tests/kvm/isos/../images/rhel61-32/ks.iso',index=1,if=none,id=drive-ide0-0-0,media=cdrom,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -cpu cpu64-rhel6,+sse2,+x2apic -kernel '/root/autotest-devel/client/tests/kvm/images/rhel61-32/vmlinuz' -initrd '/root/autotest-devel/client/tests/kvm/images/rhel61-32/initrd.img' -vnc :0 -rtc base=utc,clock=host,driftfix=none -M rhel6.1.0 -boot order=cdn,once=n,menu=off -usbdevice tablet -no-kvm-pit-reinjection --append 'ks=cdrom nicdelay=60 console=ttyS0,115200 console=tty0' -enable-kvm Expected results: Guest install can finished. Additional info: 1.Host cpuinfo processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : Dual-Core AMD Opteron(tm) Processor 1216 stepping : 3 cpu MHz : 1000.000 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips : 2009.29 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc
Created attachment 488367 [details] screen 0
Created attachment 488368 [details] info from other console 3
Created attachment 488369 [details] info from other consoel: 4
What happens when you run the guest w/o -kernel/-initrd ? Why is that testBlocker? -initrd is not that important for us
(In reply to comment #6) > What happens when you run the guest w/o -kernel/-initrd ? > Why is that testBlocker? -initrd is not that important for us It is OK to run the install test with boot ISO. Just thought that install failed should be testBlocker. It should be OK to remove that flag.
(In reply to comment #0) > 2.install guest with command line and guest will hang while boot up. : > -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive Just for my understanding, the problem occurs as above when "-smp 2" but does not occur for "-smp 1", all other options being the same? The cpuid data exported appears to be confusing the guest somehow. It is also not surprising for a difference to exist between AMD and Intel as different cpuid encodings to represent the cpu/cache topology. Is this a recent regression or is the test scenario above new?
(In reply to comment #8) > (In reply to comment #0) > > > 2.install guest with command line and guest will hang while boot up. > : > > -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive > > Just for my understanding, the problem occurs as above when "-smp 2" > but does not occur for "-smp 1", all other options being the same? > Yes, only the smp parameter changed. > The cpuid data exported appears to be confusing the guest somehow. > It is also not surprising for a difference to exist between AMD and > Intel as different cpuid encodings to represent the cpu/cache topology. > > Is this a recent regression or is the test scenario above new? I tried the RHEL 6.0 host(kernel:2.6.32-71 qemu:qemu-kvm-0.12.1.2-2.113), RHEL 6.1 guest also has the same problem. At the same time RHEL 6.0 guest works well in both RHEL 6.0 host and RHEL 6.1 host.
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #0) > > > > > 2.install guest with command line and guest will hang while boot up. > > : > > > -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive > > > > Just for my understanding, the problem occurs as above when "-smp 2" > > but does not occur for "-smp 1", all other options being the same? > > > Yes, only the smp parameter changed. Fail: -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive ... Good: -m 2048 -smp 1,cores=1,threads=1,sockets=1 -drive ...
The error message is due to a guest-side check for known/supported CPU information. Could you check if this is still reproducible using RHEL-6.4 as guest?
This was an Anaconda bug, fixed on anaconda-13.21.94-1~1. I couldn't reproduce it even using a RHEL-6.1 guest because the bug was fixed before 6.1 was released. See https://bugzilla.redhat.com/show_bug.cgi?id=623140#c10