(re-adding cc)
On 11/09/2011 09:35 PM, Walter Haidinger wrote:
Am 09.11.2011 14:40, schrieb Avi Kivity:
Actually, it looks like an OpenBSD bug. According to the AMD
documentation:
Well, the OpenBSD developers are very confident that is
a bug in the KVM cpu emulation and _not_ in
On 11/10/2011 09:46 AM, Avi Kivity wrote:
(re-adding cc)
On 11/09/2011 09:35 PM, Walter Haidinger wrote:
Am 09.11.2011 14:40, schrieb Avi Kivity:
Actually, it looks like an OpenBSD bug. According to the AMD
documentation:
Well, the OpenBSD developers are very confident that is
a bug in
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
On 11/09/2011 12:39 PM, Avi Kivity wrote:
More from m...@openbsd.org:
OpenBSD 5.0 (GENERIC) #43: Wed Aug 17 10:10:52 MDT 2011
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Phenom(tm) II X6 1100T Processor (AuthenticAMD 686-class,
512KB L2 cache)
Am 09.11.2011 14:40, schrieb Avi Kivity:
Actually, it looks like an OpenBSD bug. According to the AMD documentation:
The current P-state value can be read using the P-State Status
Register. The P-State Current Limit Register and the P-State Status
Register are read-only registers. Writes to
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
