From mboxrd@z Thu Jan  1 00:00:00 1970
From: Walter Haidinger <walter.haidinger@gmx.at>
Subject: OpenBSD 5.0 kernel panic in AMD K10 cpu power state
Date: Tue, 08 Nov 2011 10:25:10 +0100
Message-ID: <4EB8F576.9040203@gmx.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mailout-de.gmx.net ([213.165.64.23]:47164 "HELO
	mailout-de.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with SMTP id S1753450Ab1KHJZP (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 8 Nov 2011 04:25:15 -0500
Received: from walter.k9 (k9walter.openvpn-trusted.private [10.6.55.98])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(Client did not present a certificate)
	by mail.private (Postfix) with ESMTPS id 1A5B016E1A2
	for <kvm@vger.kernel.org>; Tue,  8 Nov 2011 10:25:11 +0100 (CET)
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.

More from misc@openbsd.org:
  > OpenBSD 5.0 (GENERIC) #43: Wed Aug 17 10:10:52 MDT 2011
  >   deraadt@i386.openbsd.org:/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@openbsd.org 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.

Can somebody reproduce this?

Please CC: me when replying, thanks.
I'll follow the kvm@vger archives, though.

Regards,
Walter