Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 899381[details]
screenshot - win8.0.x86_64
met same issue when install win8.0.x86_64 and win8.1.x86_64 guest on qemu-kvm-rhev-0.12.1.2-2.427.el6.x86_64
(In reply to Xu Han from comment #6)
> This issue was caused by '-cpu SandyBridge,hv_relaxed'.
>
> Please have a look at bug 1063124 comment 0.
Isn't it a duplicate?
Description of problem: win2012r2 guest show "Error Code: 0x0000001E" during installation Version-Release number of selected component (if applicable): [root@intel-i5-8-2 ~]# uname -r 2.6.32-438.el6.x86_64 [root@intel-i5-8-2 ~]# rpm -qa | grep qemu-kvm qemu-kvm-debuginfo-0.12.1.2-2.420.el6.x86_64 qemu-kvm-tools-0.12.1.2-2.420.el6.x86_64 qemu-kvm-0.12.1.2-2.420.el6.x86_64 virtio-win-1.6.8.iso How reproducible: 100% Steps to Reproduce: 1. install win2012r2 guest with "-cpu 'SandyBridge',hv_relaxed" [root@intel-i5-8-2 ~]# qemu-img create -f qcow2 win2012r2-64-virtio.qcow2 30G Formatting 'win2012r2-64-virtio.qcow2', fmt=qcow2 size=32212254720 encryption=off cluster_size=65536 /root/staf-kvm-devel/autotest-devel/client/tests/virt/qemu/qemu \ -name 'virt-tests-vm1' \ -M rhel6.5.0 \ -nodefaults \ -vga std \ -device intel-hda,bus=pci.0,addr=03 \ -device hda-duplex \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20140224-111826-lJ0Z2AYV,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20140224-111826-lJ0Z2AYV,server,nowait \ -device isa-serial,chardev=serial_id_serial0 \ -device virtio-serial-pci,id=virtio_serial_pci0,bus=pci.0,addr=04 \ -chardev socket,id=devvs,path=/tmp/virtio_port-vs-20140224-111826-lJ0Z2AYV,server,nowait \ -device virtserialport,chardev=devvs,name=vs,id=vs,bus=virtio_serial_pci0.0 \ -chardev socket,id=seabioslog_id_20140224-111826-lJ0Z2AYV,path=/tmp/seabios-20140224-111826-lJ0Z2AYV,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20140224-111826-lJ0Z2AYV,iobase=0x402 \ -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=05 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=06 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,file=/root/win2012r2-64-virtio.qcow2 \ -device scsi-hd,id=image1,drive=drive_image1 \ -device virtio-net-pci,mac=9a:a6:a7:a8:a9:aa,id=idRaKtAu,netdev=idVUgMtT,bus=pci.0,addr=07 \ -netdev tap,id=idVUgMtT,vhost=on \ -m 4096 \ -smp 2,maxcpus=2,cores=1,threads=1,sockets=2 \ -cpu 'SandyBridge',hv_relaxed \ -drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/isos/ISO/Win2012R2/en_windows_server_2012_r2_x64_dvd_2707946.iso \ -device scsi-cd,id=cd1,drive=drive_cd1 \ -drive id=drive_winutils,if=none,snapshot=off,aio=native,media=cdrom,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/isos/windows/winutils.iso \ -device scsi-cd,id=winutils,drive=drive_winutils \ -drive id=drive_virtio,if=none,snapshot=off,aio=native,media=cdrom,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/isos/windows/virtio-win-latest-signed.iso \ -device scsi-cd,id=virtio,drive=drive_virtio \ -drive id=drive_fl,if=none,cache=none,snapshot=off,readonly=off,aio=native,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/win2012r2-64/answer.vfd \ -global isa-fdc.driveA=drive_fl \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cdn,once=d,menu=off \ -enable-kvm \ -monitor stdio 2. 3. Actual results: guest stuck with "Error Code: 0x0000001E" Expected results: guest installation successfully Additional info: 1. with "-cpu host" can't hit this problem. 2. host cpuinfos: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz stepping : 7 cpu MHz : 1600.000 cache size : 6144 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 6185.97 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: