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?
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?