On 18.03.2010, at 08:11, Dieter Ries wrote: > On Wed, Mar 17, 2010 at 11:47:14PM +0100, Alexander Graf wrote: >> It looks like one of your CPUs has EFER_SVME enabled on bootup already. I'm >> not aware of code clearing EFER, so if there's garbage in there on boot it >> stays there. >> >> Could you please add the current CPU number to your printk? I bet it's >> always the same one. > > [ 1300.393635] efer on CPU1 is d01 > [ 1300.393638] efer on CPU3 is d01 > [ 1300.393641] efer on CPU2 is d01 > [ 1300.393643] EFER_SVME is 1000 > [ 1300.393645] EFER_SVME is 1000 > [ 1300.393646] EFER_SVME is 1000 > [ 1300.393650] efer on CPU0 is 1d01 > [ 1300.393652] EFER_SVME is 1000 > [ 1300.393653] kvm: enabling virtualization on CPU0 failed > > >> If that's the case I'd say you have a broken BIOS or bootloader. > > You are right, it seems to be always cpu0. I'll check my BIOS and flash > a newer version if available.
Please do. If that doesn't help ping me again. I'll write up a quirk patch then. Alex-- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
