On 03/17/12 15:21, Alan Cox wrote: > 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. Alternatively, you may be using a newer processor > revision that still suffers from the bug, but the kernel doesn't enable the > workaround for. Can you tell us how the FreeBSD guest sees the underlying > processor, e.g., the first few lines of dmesg from the guest? > > Alan >
I am currently passing "-cpu Opteron_G3,+3dnowext,+3dnow,+3dnowprefetch,+cmp_legacy" to KVM at libvirtd's suggestion. I assume this is why the workaround is not being triggered. # dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-RELEASE #0: Sun Jan 15 22:48:55 UTC 2012 root@zfsguru:/usr/obj/usr/src/sys/OFED amd64 module_register: module pci/mps already exists! Module pci/mps failed to register: 17 CPU: AMD Opteron 23xx (Gen 3 Class Opteron) (3210.85-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf61 Family = f Model = 6 Stepping = 1 Features=0x783fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2> Features2=0x80802001<SSE3,CX16,POPCNT,HV> AMD Features=0xe0100800<SYSCALL,NX,LM,3DNow!+,3DNow!> AMD Features2=0x1e7<LAHF,CMP,SVM,ABM,SSE4A,MAS,Prefetch>
signature.asc
Description: OpenPGP digital signature