1
19.1 Legacy Series / Re: Running in "boot loop" with KVM/Proxmox
« on: July 06, 2019, 07:05:24 pm »
Hi guys,
I've figured out, that it's an issue from the BSD/HardenedBSD kernel, an erratum/bug from the AMD 10h CPU :
Snipped from the pmap.c file from the kernel:
Has anyone some experience with an secure workaround for this? Or have I really switch CPU/Server to get an VM running for OPNsense
I've figured out, that it's an issue from the BSD/HardenedBSD kernel, an erratum/bug from the AMD 10h CPU :
Code: [Select]
pve01 kernel: [ 284.573818] SVM: KVM: Guest triggered AMD Erratum 383
Snipped from the pmap.c file from the kernel:
Code: [Select]
/*
* If the kernel is running on a virtual machine, then it must assume
* that MCA is enabled by the hypervisor. Moreover, the kernel must
* be prepared for the hypervisor changing the vendor and family that
* are reported by CPUID. Consequently, the workaround for AMD Family
* 10h Erratum 383 is enabled if the processor's feature set does not
* include at least one feature that is only supported by older Intel
* or newer AMD processors.
*/
if (vm_guest != VM_GUEST_NO && (cpu_feature & CPUID_SS) == 0 &&
(cpu_feature2 & (CPUID2_SSSE3 | CPUID2_SSE41 | CPUID2_AESNI |
CPUID2_AVX | CPUID2_XSAVE)) == 0 && (amd_feature2 & (AMDID2_XOP |
AMDID2_FMA4)) == 0)
workaround_erratum383 = 1;
Has anyone some experience with an secure workaround for this? Or have I really switch CPU/Server to get an VM running for OPNsense