'host' cpu not working

[Sandra Haag]

Hi,

I am running Proxmox 5.2 on an AMD Ryzen 5 2600 Six-Core Processor, on a
Gigabyte GA-AB350N-Gaming WIFI
(rev. 1.0) motherboard.

Everything is working fine and dandy, all virtualisation-related features seem to be working, I can do PCI passthrough etc, however, there's one thing I can't do. I cannot select 'host' as the CPU for my guests, because then they crash on attempted boot.

I can run them with KVM64, Nehalem, Skylake-Client etc, but I would like the native features of my processor to be available to the guests. Do you have any idea what might be going on?

 

[udo]

Hi Sandra,
does this happens with all guest - like an "normal" linux?

What kind of guest do you test?

Udo

 

[Sandra Haag]

I have only just now confirmed that it does _not_ happen with a Linux Mint guest. There, on the other hand, the graphics (nouveau) fail to initialise at all, despite multiple attempts, eventually dropping me to console login.

Crashing happens with a Win10 guest.

 

[Sandra Haag]

SOLVED! I managed to solve the issue by adding the following to /etc/modprobe.d/kvm.conf


options kvm ignore_msrs=1

My CPU (Ryzen 5 2600) is now detected as an AMD EPYC and all features seem to be working.

 

[pushnoi]

I have the same issue with a Ryzen 2700x + x470 board, could not even install Windows without crashing immediately. Only when I put the cpu type to kvm64 the system works.

Tried your solution, but this did not help much. System would boot, but crashes after using something which utilizes one of the features on the CPU which is not available @ kvm64. My best guess is SSSE3.

Any idea if this will be solved in a future update?

 

[HuJK]

Same problem. You solved some of my problem. After adding options kvm ignore_msrs=1 in my proxmox.

My Windows10 can boot successfully in proxmox, but Centos7 with GNOME still cannot boot. But I can SSH into it.

If I select kvm64, centos7 with GNOME can operate normally.

Here is the output from "cat /var/log/messages":

Dec 31 13:46:56 2001-b011-0002-147c-603e-6dff-fe51-572c dbus[682]: [system] Successfully activated service 'org.freedesktop.realmd'
Dec 31 13:46:56 2001-b011-0002-147c-603e-6dff-fe51-572c dbus-daemon: dbus[682]: [system] Successfully activated service 'org.freedesktop.realmd'
Dec 31 13:46:56 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: LLVM ERROR: Cannot select: intrinsic %llvm.x86.sse41.pblendvb
Dec 31 13:46:56 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: Gjs-Message: JS WARNING: [resource:///org/gnome/shell/ui/extensionSystem.js 301]: octal literals and octal escape sequences are deprecated
Dec 31 13:46:56 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: Gjs-Message: JS WARNING: [resource:///org/gnome/shell/ui/extensionSystem.js 301]: octal literals and octal escape sequences are deprecated
Dec 31 13:46:56 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: Gjs-Message: JS WARNING: [resource:///org/gnome/shell/ui/extensionSystem.js 301]: octal literals and octal escape sequences are deprecated
Dec 31 13:46:56 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: current session already has an ibus-daemon.
Dec 31 13:46:57 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: LLVM ERROR: Cannot select: intrinsic %llvm.x86.sse41.pblendvb
Dec 31 13:46:57 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: gnome-session[2043]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Dec 31 13:46:57 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session[2043]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Dec 31 13:46:57 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: Unrecoverable failure in required component gnome-shell.desktop
Dec 31 13:46:57 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: (gnome-settings-daemon:2519): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Dec 31 13:46:57 2001-b011-0002-147c-603e-6dff-fe51-572c gnome-session: (gnome-settings-daemon:2519): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Dec 31 13:46:58 2001-b011-0002-147c-603e-6dff-fe51-572c NetworkManager[814]: <info>  (virbr0-nic): link disconnected (calling deferred action)
Dec 31 13:47:01 2001-b011-0002-147c-603e-6dff-fe51-572c systemd: Created slice user-1000.slice.
Dec 31 13:47:01 2001-b011-0002-147c-603e-6dff-fe51-572c systemd: Starting user-1000.slice.
Dec 31 13:47:01 2001-b011-0002-147c-603e-6dff-fe51-572c systemd: Started Session 1 of user user.
Dec 31 13:47:01 2001-b011-0002-147c-603e-6dff-fe51-572c systemd-logind: New session 1 of user user.
Dec 31 13:47:01 2001-b011-0002-147c-603e-6dff-fe51-572c systemd: Starting Session 1 of user user.
Dec 31 13:47:01 2001-b011-0002-147c-603e-6dff-fe51-572c dbus-daemon: dbus[682]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)

Anyone have any ideas?