From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NDdOh-0001jY-9d for qemu-devel@nongnu.org; Thu, 26 Nov 2009 07:24:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NDdOc-0001gF-67 for qemu-devel@nongnu.org; Thu, 26 Nov 2009 07:24:30 -0500 Received: from [199.232.76.173] (port=47088 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDdOc-0001gC-2Z for qemu-devel@nongnu.org; Thu, 26 Nov 2009 07:24:26 -0500 Received: from cantor.suse.de ([195.135.220.2]:33668 helo=mx1.suse.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NDdOb-0007Pp-2k for qemu-devel@nongnu.org; Thu, 26 Nov 2009 07:24:25 -0500 Message-ID: <4B0E7376.3020907@suse.de> Date: Thu, 26 Nov 2009 13:24:22 +0100 From: Alexander Graf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/6] Fix -kernel with SeaBIOS v2 References: <20091120091231.GA21855@lst.de> <20091120113113.GA26408@lst.de> <450764C8-F59A-411B-9733-07136D97981B@suse.de> <20091123202138.GA9879@lst.de> <5024501E-4BFD-4C6B-8455-20C406948C20@suse.de> <20091123213600.GA12479@lst.de> <4B0CFFD5.1010003@suse.de> <20091126114213.GA31527@lst.de> <4B0E6DD9.5030608@suse.de> <20091126121855.GA336@lst.de> In-Reply-To: <20091126121855.GA336@lst.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: Glauber Costa , Avi Kivity , "qemu-devel@nongnu.org" , Juan Quintela Christoph Hellwig wrote: > On Thu, Nov 26, 2009 at 01:00:25PM +0100, Alexander Graf wrote: > >> Hm - are you using -L pc-bios? >> > > No. I use an installed qemu (./configure --prefix=/opt/qemu) and > there's no pc-bios directorie in my kernel source tree where I start it > from. > Hm - maybe worth a try to give it a -L to the source pc-bios directory anyways. >> Also, maybe there's something in dmesg >> telling you about an invalid instruction or the likes? >> > > [ 5928.948615] kvm: 14584: cpu0 unhandled wrmsr: 0xc0000083 data 0 > [ 5929.309486] kvm: 14584: cpu0 unhandled wrmsr: 0xc0000083 data 0 > [ 5929.309530] kvm: 14584: cpu0 unhandled rdmsr: 0xc0000083 > [ 5929.311763] kvm: 14584: cpu0 unhandled wrmsr: 0xc0000083 data 0 > [ 5929.311856] kvm: 14584: cpu0 unhandled wrmsr: 0xc0000083 data 0 > [ 5929.311899] kvm: 14584: cpu0 unhandled rdmsr: 0xc0000083 > [ 5929.313408] kvm: 14584: cpu0 unhandled wrmsr: 0xc0000083 data 0 > /include/asm/msr-index.h:#define MSR_CSTAR 0xc0000083 /* compat mode SYSCALL target */ Sounds like your guest kernel is trying to access an x86_64 register? You can of cause try insmod'ing kvm.ko with ignore_msrs=1. You hopefully don't need syscalls until you get into user space. Alex