On 11/08/2011 11:25 AM, Walter Haidinger wrote:
> Hi!
>
> OpenBSD 5.0/i386 throws a kernel panic when I try to
> boot it inside a Linux KVM (host: vanilla 3.0.4,
> openSUSE 11.4/x86_64) unter qemu-kvm 0.14.1 and 0.15.1.
> Note that OpenBSD 4.9/i386 works.
>
> The OpenBSD developers say:
> "the virtual machine emulator you are using has a bug. it declares
> a cpu type from upstream and then does not emulate certain functions
> of that cpu."
>
> Therefore I'm reporting this here.
Thanks.
> More from misc@xxxxxxxxxxx:
> > OpenBSD 5.0 (GENERIC) #43: Wed Aug 17 10:10:52 MDT 2011
> > deraadt@xxxxxxxxxxxxxxxx:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: AMD Phenom(tm) II X6 1100T Processor ("AuthenticAMD" 686-class, 512KB L2 cache) 3.31 GHz
> > ...
> > kernel: protection fault trap, code=0
> > Stopped at k1x_init+0x56: rdmsr
> > k1x_init(d0ad7540,d09ae620,d0b8ce58,d059ce20,30000002) at k1x_init+0x56
>
> k1x_init() is not related to vmt, it is from k1x-pstate.c, which
> is cpu power state driver for K10 processors.
>
> Thread on misc@xxxxxxxxxxx with full OpenBSD dmesg:
> http://marc.info/?l=openbsd-misc&m=132067866208188&w=2
>
> Since both qemu-kvm 0.14.1 and 0.15.1 show identical
> symptoms, I assume this is in deed a KVM kernel bug.
It doesn't actually follow, but happens to be correct.
> Can somebody reproduce this?
I'll try it out and see.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
