Finally I'm able to test on a Threadripper myself now.
Note: In regard to the commit that Babu identified - I'm on kernel
5.10.0-1020-oem so that patch would be applied already. I need to find
an older kernel to retry with that as well
(on that new kernel) I did a full Win10 install and it worked fine for
me.
In regard to CPU types (for comparison) I got
qemu 1:4.2-3ubuntu6.15 / libvirt 6.0.0-0ubuntu8.8:
<mode name='host-model' supported='yes'>
<model fallback='forbid'>EPYC-Rome</model>
<vendor>AMD</vendor>
<feature policy='require' name='x2apic'/>
<feature policy='require' name='tsc-deadline'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='tsc_adjust'/>
<feature policy='require' name='stibp'/>
<feature policy='require' name='arch-capabilities'/>
<feature policy='require' name='ssbd'/>
<feature policy='require' name='xsaves'/>
<feature policy='require' name='cmp_legacy'/>
<feature policy='require' name='invtsc'/>
<feature policy='require' name='amd-ssbd'/>
<feature policy='require' name='virt-ssbd'/>
<feature policy='require' name='rdctl-no'/>
<feature policy='require' name='skip-l1dfl-vmentry'/>
<feature policy='require' name='mds-no'/>
<feature policy='require' name='pschange-mc-no'/>
</mode>
With a more recent qemu/libvirt it isn't much different for this chip
(there recently were some Milan changes, but those seem not to matter
for this chip).
qemu 1:5.2+dfsg-9ubuntu1 / libvirt 7.0.0-2ubuntu1
<mode name='host-model' supported='yes'>
<model fallback='forbid'>EPYC-Rome</model>
<vendor>AMD</vendor>
<feature policy='require' name='x2apic'/>
<feature policy='require' name='tsc-deadline'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='tsc_adjust'/>
<feature policy='require' name='stibp'/>
<feature policy='require' name='arch-capabilities'/>
<feature policy='require' name='ssbd'/>
<feature policy='require' name='xsaves'/>
<feature policy='require' name='cmp_legacy'/>
<feature policy='require' name='invtsc'/>
<feature policy='require' name='amd-ssbd'/>
<feature policy='require' name='virt-ssbd'/>
<feature policy='require' name='rdctl-no'/>
<feature policy='require' name='skip-l1dfl-vmentry'/>
<feature policy='require' name='mds-no'/>
<feature policy='require' name='pschange-mc-no'/>
</mode>
I wasn't able to crash this setup with an old (18.04) nor a new 21.04) Ubuntu
guest.
Installing Win10 worked fine for a while and didn't break as reported. But the
setup I have goes through triple ssh-tunnels and around the globe - that slows
things down a lot :-/
This is how far I've got:
1. start up the install
2. select no license key -> custom install -> it started copying files
3. it goes into the first reboot
After this the latency kills me and virt-manager starts to abort the
installation.
So far I did not hit (https://launchpadlibrarian.net/529734412/security.png) as
reported by David.
@David - did this already pass the critical step for you, how early or late in
the install did you hit the issues.
As I said I'll probably need to find an older kernel anyway (to be before the
commit that Babu referenced)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1915063
Title:
Windows 10 wil not install using qemu-system-x86_64
Status in QEMU:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce
install virt-manager and ovmf if nopt already there
copy windows and virtio iso files to /var/lib/libvirt/images
Use virt-manager from local machine to create your VMs with the disk, CPUs
and memory required
Select customize configuration then select OVMF(UEFI) instead of seabios
set first CDROM to the windows installation iso (enable in boot options)
add a second CDROM and load with the virtio iso
change spice display to VNC
Always get a security error from windows and it fails to launch the
installer (works on RHEL and Fedora)
I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of
no help
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-01-20 (19 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20201030-14:39
MachineType: LENOVO 30E102Z
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash
vt.handoff=7
ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
RelatedPackageVersions:
linux-restricted-modules-5.6.0-1042-oem N/A
linux-backports-modules-5.6.0-1042-oem N/A
linux-firmware 1.187.8
RfKill:
Tags: focal
Uname: Linux 5.6.0-1042-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/29/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: S07KT08A
dmi.board.name: 1046
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
dmi.product.family: INVALID
dmi.product.name: 30E102Z
dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
dmi.product.version: ThinkStation P620
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1915063/+subscriptions
