KVM Guest AMD Erratum 383 since Proxmox v2.0

[Digdug]

Since reinstalling Proxmox 1.9 to Proxmox 2.0 one of my KVM guests keeps rebooting. The error at the host is:"KVM Guest Triggered AMD Erratum 383"

This is a pfSense 2.0.1 installation which has been running happely with Proxmox 1.9
Guest info:
pfSense 2.0.1-RELEASE (amd64) built on Mon Dec 12 18:16:13 EST 2011 FreeBSD 8.1-RELEASE-p6 FreeBSD 8.1-RELEASE-p6 #0: Mon Dec 12 18:15:35 EST 2011 root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64

KVM CPU is set to QEMU64 (default)

Why is this KVM suddenly triggering the erratum and how can I fix this?

 

[spirit]

Hi,
found this:
http://freebsd.1045724.n5.nabble.com/AMD-Erratum-383-crashes-FreeBSD-9-Stable-td5573933.html
"> When the FreeBSD kernel detects that it is running on an affected
> processor, it automatically enables the recommended workaround. However,
> because you are running within a virtual machine, the automatic detection
> may not be working. "

Maybe with qemu64, it doesn't detect the good processor.
Could you try with cpu model : host or opteron_Gx ?

 

[Digdug]

Hi, thanks for the reply. I found the same and tried KVM CPU to mode host and opteron_Gx.
FreeBSD correctly sees the host, halts with a "fatal trap 9: general protection fault while in kernel mode"

When I set the cpu back to QEMU64 it boots, but as soon as the login prompt display's, it reboots with the "KVM Guest Triggered AMD Erratum 383" error.

The host is a AMD Phenom II X6 1075T (K8 class CPU)

 

[Digdug]

Ok, think I "fixed" it with a workaround from 2010...

CPU is set to QEMU64
In the virtual machine added:
vm.pmap.pg_ps_enabled="0"
to /boot/loader.conf

Now the system boots properly, time will tell...