This affected me. Took me several days.
The solution posted by asd fghjkl (ryzen27) worked for me as well:
sudo nano /etc/modprobe.d/kvm.conf
options kvm ignore_msrs=1
and then rebooted
I'm very glad i found this thread. Don't know where to report this or if
it's even a bug, But hope it gets
I was able to avoid rebooting after following @Andrii's instructions -
https://bugs.launchpad.net/qemu/+bug/1703506/comments/19 - above:
systemctl stop libvirtd libvirtd-admin.socket libvirtd-ro.socket libvirtd.socket
sudo modprobe -r kvm_intel kvm
systemctl start libvirtd libvirtd-admin.socket
Found the same problem using Gnome boxes, as I understand it uses QEMU.
Error I see in gnome boxes when I'm trying to install windows 10 vm:
SYSTEM THREAD EXCEPTION NOT HANDLED
Fresh install of Ubuntu 22.04
CPU: AMD Ryzen 7 1700
The solution posted by asd fghjkl (ryzen27) worked for me too:
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1703506
Title:
SMT not
** Bug watch removed: Red Hat Bugzilla #1135772
https://bugzilla.redhat.com/show_bug.cgi?id=1135772
** Bug watch removed: Red Hat Bugzilla #1592276
https://bugzilla.redhat.com/show_bug.cgi?id=1592276
** Changed in: qemu
Assignee: Eduardo Habkost (ehabkost) => (unassigned)
--
You
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch
@ryzen27: do you have dmesg logs showing the MSRs being written by the
guest? You may be hitting the bug described at
https://bugzilla.redhat.com/show_bug.cgi?id=1592276
** Bug watch added: Red Hat Bugzilla #1592276
https://bugzilla.redhat.com/show_bug.cgi?id=1592276
--
You received this bug
I got it to work:
sudo nano /etc/modprobe.d/kvm.conf
add "options kvm ignore_msrs=1" (without quotes)
reboot
Then changing "-machine q35" to "-machine pc" kept it from crashing
randomly.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
QEMU 3.0 has limited TOPOEXT support. You can try using `-cpu EPYC`,
and the `threads` option is supposed to work.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1703506
Title:
SMT not supported
Error I see in terminal:
AMD CPU doesn't support hyperthreading. Please configure -smp options properly.
Error I see in my windows 10 vm:
SYSTEM THREAD EXCEPTION NOT HANDLED
I am unable to use Qemu at all. Serious problem.
CPU: AMD Ryzen 5 1600X Six-Core Processor × 6
--
You received this bug
I tried the above patches on a TR 1900X and they do not help to enable
SMT. I still receive the warning.
Also, with the patches applied, the CPU now identifies as EPYC in the
guest.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
just to be clear.. The kernel kvm patch is rebased on linux-next. If you
are on older kernel then try this kernel patch.
https://patchwork.kernel.org/patch/10031775/ plus qemu patch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Posted few patches to support this feature on AMD EPYC processors. Feel free to
test and review.
1. Kernel kvm patch
https://patchwork.kernel.org/patch/10190107/
2. qemu patches
https://patchwork.kernel.org/project/qemu-devel/list/?submitter=178527
Thanks
--
You received this bug
The core topology info used by Linux (see
linux/arch/x86/kernel/cpu/amd.c:amd_get_topology()) is actually at
CPUID[0x801e].
AMD's documentation is a bit confusing, as the Architecture Programmer's
Manual still refers to CPUID[0x801e].EBX[bits 7:0] as "compute unit
ID", but the Processor
I am looking at the diff between the host and guest CPUID, and we have a
few candidates: CPUID[4] is all zeroes on the host, and the host has
CPUID leaves up to 0x801f available, including CPUID[0x801d]
(which contains cache topology information). Probably we need to
implement
I tried disabling the CmpLegacy bit directly on /target/i386/cpu.c deleting the
If statement on "case 0x8001:" or changing "*ecx |= 1 << 1;" to "*ecx |= 0
<< 1;"
But it didn't work, the VM still sees 8 physical cores.
I believe the HTT bit should be enabled by default
I tried changing it to
Attached Ubuntu 17.04 guest logs.
I wasn't able to run x86info as root. Only as regular user.
Error shown:
readEntry: Operation not permitted
error reading 1KB from 0x3fffc00
There are a few bug reports about it but no workarounds. Seems to happen on
vm's.
So the output is missing a few
Thank you for the info. Having info on Linux guests' behavior would be
nice to have, but it's possible to extract the raw CPUID data seen by
the Windows guest using an equivalent Windows tool (suggestions of tools
are welcome).
Also, can somebody confirm if the same Windows version works as
I can confirm the same behavior with a Ryzen 7 1700.
Host Arch Linux x64 Kernel 4.11.9, Guest Windows 10 Pro.
Running with -cpu host and -smp 8,sockets=1,cores=4,threads=2.
Attached the logs of the host and results of the output of msinfo32 and "WMIC
CPU Get
>Please confirm what's the QEMU command-line being used (especially the
-smp and -cpu options), and check if the bug persists if using "-cpu
host".
I'm using -cpu host already, here's just the cpu and smp commands:
-cpu
** Changed in: qemu
Assignee: (unassigned) => Eduardo Habkost (ehabkost)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1703506
Title:
SMT not supported by QEMU on AMD Ryzen CPU
Status in
The warning doesn't make QEMU disable anything, it just warns the user
that guests are likely to ignore the HT info on CPUID if CPU vendor is
AMD.
Please confirm what's the QEMU command-line being used (especially the
-smp and -cpu options), and check if the bug persists if using "-cpu
host".
To
I can confirm this problem as it affects me, too on Ubuntu XENIAL,
Kernel 4.10.0-26-generic
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1703506
Title:
SMT not supported by QEMU on AMD Ryzen CPU
23 matches
Mail list logo
