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.
Windows guest virtual machine support limited
As of Red Hat Enterprise Linux 7, Windows guest virtual machines are supported only under specific subscription programs, such as Advanced Mission Critical (AMC).
Description of problem:
Version-Release number of selected component (if applicable):
Tried on following qemu-kvm
qemu-kvm-rhev-2.2.0-8.el7.x86_64
qemu-kvm-rhev-0.12.1.2-2.469.el6.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Trying installing windows 10 insider preview or windows server 2016
CLI:
/usr/libexec/qemu-kvm -name 103PNC2016646TV -enable-kvm -m 6G -smp 4 -uuid b503e8e6-1f58-49ce-820e-bc4ace245458 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/103PNC2016646TV,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=103PNC2016646TV,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_server_technical_preview_2_x64_dvd_6651466.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=103PNC2016646TV.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:52:47:3f:a6:5a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -vga cirrus -device pvpanic,id=pvpanic0,ioport=0x050
2.
3.
Actual results:
Guest BSod Directly
Expected results:
no bsod occurs.
Additional info:
1.It might not related to qemu-kvm but Did not hit this issue on previous beta version windows 10/2016.It happened on latest beta version windows 10.
2#sha1sum of images
587d610bc899f14552903272ed0631bc85d18b6e en_windows_10_enterprise_insider_preview_10074_x64_dvd_6651209.iso
37d1c488036f370b842a8d7aac3e40a271e87cb0 en_windows_10_enterprise_insider_preview_10074_x86_dvd_6651242.iso
5efb981c94e1223c85f3bb504d04e0642a85c1d4
aa2bd2f08ab8543d6eb51fcdd50f8ced219a4fe6 en_windows_server_technical_preview_2_x64_dvd_6651466.iso
3.The SHA1SUM is same as as the value provide in MSDN website.
4. QE Test previous Beta iso before ,did not hit the issue.
'en_windows_10_technical_preview_9926_x86_dvd_6245077.iso':'1ae10947cc297ae299e1c81f95812efbb5c84121',
'en_windows_10_technical_preview_9926_x64_dvd_6245061.iso':'6a95316728299d95249a29fbeb9676ded23b8beb',
'en_windows_server_technical_preview_x64_dvd_5554304.iso':'d9300b00f8140439fff22e98fa7b4c82c1366040'}
For this particular MSR it is okay to return the default, i.e. 55h, but there may be other MSRs that Windows tries to access.
Vadim, can you try running KVM with the ignore_msrs parameter set to Y, and grab from dmesg a list of model specific registers that Windows tries to read?
(In reply to Paolo Bonzini from comment #31)
> For this particular MSR it is okay to return the default, i.e. 55h, but
> there may be other MSRs that Windows tries to access.
>
> Vadim, can you try running KVM with the ignore_msrs parameter set to Y, and
> grab from dmesg a list of model specific registers that Windows tries to
> read?
[vrozenfe@oscar qemu]$ dmesg | grep -i msr
[6340893.800233] kvm [28248]: vcpu0 unhandled rdmsr: 0x606
[6340918.337790] kvm [28248]: vcpu1 unhandled rdmsr: 0x606
[6340954.032611] kvm [28290]: vcpu1 ignored rdmsr: 0x606
[6340954.032614] kvm [28290]: vcpu1 ignored rdmsr: 0x641
(In reply to Amnon Ilan from comment #33)
> A new build of Windows 10 (build 10162) is available here:
> http://windows.microsoft.com/en-us/windows/preview-iso
>
> Please check if the problem is still there.
With build 10162, the GP due to missing MSRs is not reproducible anymore (bug 1232894) but the bsod that this bug is tracking due to the cflushopt instruction is still present. I didn't close bug 10162 yet though, it's probably best to wait for a release before closing it. Vadim, do you want to try the 32-bit version ?
(In reply to Bandan Das from comment #34)
> (In reply to Amnon Ilan from comment #33)
> > A new build of Windows 10 (build 10162) is available here:
> > http://windows.microsoft.com/en-us/windows/preview-iso
> >
> > Please check if the problem is still there.
>
> With build 10162, the GP due to missing MSRs is not reproducible anymore
> (bug 1232894) but the bsod that this bug is tracking due to the cflushopt
> instruction is still present. I didn't close bug 10162 yet though, it's
> probably best to wait for a release before closing it. Vadim, do you want to
> try the 32-bit version ?
Also cannot reproduce the crash, mentioned in comment #30, with 32-bit version (build 10162).
Comment 38Miroslav Rezanina
2015-08-07 09:31:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2546.html
JFYI:
hit a similar problem on RHEL-7.9-updates-20230713.1 with CPU(Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz)
install Windows Server 2016 fail, but Windows Server 2012r2 success
workaround:
add '--qemu-commandline=-cpu Skylake-Server' to virt-install
//or
add '-cpu Skylake-Server' to qemu-kvm
Description of problem: Version-Release number of selected component (if applicable): Tried on following qemu-kvm qemu-kvm-rhev-2.2.0-8.el7.x86_64 qemu-kvm-rhev-0.12.1.2-2.469.el6.x86_64 qemu-kvm-rhev-1.5.3-60.el7ev.x86_64 How reproducible: 100% Steps to Reproduce: 1.Trying installing windows 10 insider preview or windows server 2016 CLI: /usr/libexec/qemu-kvm -name 103PNC2016646TV -enable-kvm -m 6G -smp 4 -uuid b503e8e6-1f58-49ce-820e-bc4ace245458 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/103PNC2016646TV,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=103PNC2016646TV,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_server_technical_preview_2_x64_dvd_6651466.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=103PNC2016646TV.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:52:47:3f:a6:5a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -vga cirrus -device pvpanic,id=pvpanic0,ioport=0x050 2. 3. Actual results: Guest BSod Directly Expected results: no bsod occurs. Additional info: 1.It might not related to qemu-kvm but Did not hit this issue on previous beta version windows 10/2016.It happened on latest beta version windows 10. 2#sha1sum of images 587d610bc899f14552903272ed0631bc85d18b6e en_windows_10_enterprise_insider_preview_10074_x64_dvd_6651209.iso 37d1c488036f370b842a8d7aac3e40a271e87cb0 en_windows_10_enterprise_insider_preview_10074_x86_dvd_6651242.iso 5efb981c94e1223c85f3bb504d04e0642a85c1d4 aa2bd2f08ab8543d6eb51fcdd50f8ced219a4fe6 en_windows_server_technical_preview_2_x64_dvd_6651466.iso 3.The SHA1SUM is same as as the value provide in MSDN website. 4. QE Test previous Beta iso before ,did not hit the issue. 'en_windows_10_technical_preview_9926_x86_dvd_6245077.iso':'1ae10947cc297ae299e1c81f95812efbb5c84121', 'en_windows_10_technical_preview_9926_x64_dvd_6245061.iso':'6a95316728299d95249a29fbeb9676ded23b8beb', 'en_windows_server_technical_preview_x64_dvd_5554304.iso':'d9300b00f8140439fff22e98fa7b4c82c1366040'}