This sounds like the same problem we're investigating in Fedora/RHEL land affecting guests with EPYC CPU, or host-passthrough from an EPYC family 17h host. Workaround should be to use "-cpu Opteron_G5" for now
https://bugzilla.redhat.com/show_bug.cgi?id=1592276 https://bugzilla.redhat.com/show_bug.cgi?id=1593190 Looks like windows is tickling an undocumented MSR and we're trying to find out what this MSR is supposed todo and thus how to handle it in KVM/QEMU ** Bug watch added: Red Hat Bugzilla #1592276 https://bugzilla.redhat.com/show_bug.cgi?id=1592276 ** Bug watch added: Red Hat Bugzilla #1593190 https://bugzilla.redhat.com/show_bug.cgi?id=1593190 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1778966 Title: Windows 1803 and later crashes on KVM Status in QEMU: New Bug description: For a bionic host, using the current public kvm modules, KVM is not capable of booting a WindowsInsider or msdn Windows 1803 Windows Server iso. In snstalling from an ISO from a started windows 2016 guest results in an unbootable and unrepairable guest. The hardware is a threadripper 1920x with 32GB of main memory, disk mydigital BPX SSD and WD based 4 column RAID 5 via mdadm. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1778966/+subscriptions
