Description of problem: Disable ept on host, boot win2022 guest, hit bsod, the stop code is 'UNEXPECTED KERNEL MODE TRAP' or 'PAGE FAULT IN NANPAGED AREA', or 'KERNEL SECURITY CHECK AILURE'. Version-Release number of selected component (if applicable): qemu-kvm-6.0.0-17.module+el8.5.0+11173+c9fce0bb kernel-4.18.0-310.el8.x86_64 How reproducible: always Steps to Reproduce: 1. Disable ept on intel host # rmmod kvm_intel # modprobe kvm_intel ept=0 # cat /sys/module/kvm_intel/parameters/ept N 2. Boot up win2022 guest Actual results: Guest hit BSOD. Expected results: Guest boot up without error. Additional info: 1. Win2019 guest works well. 2. QEMU cli: # /usr/libexec/qemu-kvm \ -S \ -name 'avocado-vt-vm1' \ -sandbox on \ -machine pc\ -nodefaults \ -device VGA,bus=pci.0,addr=0x2 \ -m 4096 \ -smp 6,maxcpus=6,cores=3,threads=1,dies=1,sockets=2 \ -cpu 'Haswell-noTSX',hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,+kvm_pv_unhalt \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \ -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/images/win2022-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \ -device virtio-net-pci,mac=9a:5c:41:18:c9:4e,id=idwyAmhM,netdev=idmsjSu5,bus=pci.0,addr=0x5 \ -netdev tap,id=idmsjSu5 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot menu=off,order=cdn,once=c,strict=off \ -enable-kvm -monitor stdio
Related to BZ#1906634. In any case for Server SKUs - MS requires EPT support in CPUs - https://docs.microsoft.com/en-us/windows-server/get-started-19/sys-reqs-19 Minimum: 1.4 GHz 64-bit processor Compatible with x64 instruction set Supports NX and DEP Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW Supports Second Level Address Translation (EPT or NPT)
(In reply to Yvugenfi from comment #1) > Related to BZ#1906634. > > In any case for Server SKUs - MS requires EPT support in CPUs - > https://docs.microsoft.com/en-us/windows-server/get-started-19/sys-reqs-19 > > Minimum: > 1.4 GHz 64-bit processor > Compatible with x64 instruction set > Supports NX and DEP > Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW > Supports Second Level Address Translation (EPT or NPT) Thanks for the information. But I only hit the issue with Win2022 guest, Win2019 guest works fine. Could it be something else that goes wrong?
(In reply to Yumei Huang from comment #2) > (In reply to Yvugenfi from comment #1) > > Related to BZ#1906634. > > > > In any case for Server SKUs - MS requires EPT support in CPUs - > > https://docs.microsoft.com/en-us/windows-server/get-started-19/sys-reqs-19 > > > > Minimum: > > 1.4 GHz 64-bit processor > > Compatible with x64 instruction set > > Supports NX and DEP > > Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW > > Supports Second Level Address Translation (EPT or NPT) > > Thanks for the information. But I only hit the issue with Win2022 guest, > Win2019 guest works fine. Strange, BZ#1906634 was opened on Windows Server 2019. > Could it be something else that goes wrong? Could be. That's why we are not closing BZ#1906634 and continue to investigate
Meirav - windows guest issue although it looks like Yan is already involved.
BTW, seems the issue is not 100% reproducible. Sometimes windows 2022 guest can boot up without error and works fine when ept=0.