From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:60607)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1SvOEw-0007BE-36
	for qemu-devel@nongnu.org; Sun, 29 Jul 2012 03:48:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1SvOEv-0006TL-3Q
	for qemu-devel@nongnu.org; Sun, 29 Jul 2012 03:48:38 -0400
Received: from mx1.redhat.com ([209.132.183.28]:27135)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1SvOEu-0006TB-RN
	for qemu-devel@nongnu.org; Sun, 29 Jul 2012 03:48:37 -0400
Date: Sun, 29 Jul 2012 10:48:32 +0300
From: Gleb Natapov <gleb@redhat.com>
Message-ID: <20120729074832.GU26120@redhat.com>
References: <CABurPee=pqnMRfVdcyOLGM+qLKX-ztBH78LFgbbMhHD0mi-D_Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABurPee=pqnMRfVdcyOLGM+qLKX-ztBH78LFgbbMhHD0mi-D_Q@mail.gmail.com>
Subject: Re: [Qemu-devel] [Bug-Report] KVM failed to support netbsd-based
 kernel!
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: GaoYi <gaoyi709@gmail.com>
Cc: qemu-devel@nongnu.org

On Fri, Jul 27, 2012 at 12:44:20PM +0800, GaoYi wrote:
> Hi all,
>    I am running a netbsd kernel in KVM, using Intel VT. However, the OS
> failed to start up with the following outputs:
> 
>     KVM internal error. Suberror: 1
>     emulation failure.
>     EAX=00000001    EBX=ffffffff    ECX=00000005   EDX=00000001
>     ESI=00000001     EDI=001c4bd2   EBP=0011a72c     ESP=0fff007d
>     EIP=0011a6d0     EFL=00010002   [-------]   CPL=0   II=0   A20=1
> SMM=0    HLT=0
>     ES=0010 0000 0000 ffff ffff    00c09300    DPL=0       DS      [-WA]
>     CS=0018 0000 0000 ffff ffff    00c09b00    DPL=0       CS32   [-RA]
>     SS=0010 0000 0000 ffff ffff    00c09300    DPL=0       DS      [-WA]
>     DS=0010 0000 0000 ffff ffff    00c09300    DPL=0       DS      [-WA]
>     FS=0010 0000 0000 ffff ffff    00c09300    DPL=0       DS      [-WA]
>     GS=0010 0000 0000 ffff ffff    00c09300    DPL=0       DS      [-WA]
>     LDT=0000 0000 0000 0000 ffff    00008200    DPL=0  LDT
>     TR=0000 feff d000 0000 2088    00008b00    DPL=0  TSS32-busy
>     GDT= 000080c0 00000027
>     IDT =  00100000 000007ff
>     CR0= 40000011  CR2=00000000 CR3=00000000 CR4=00000400
>     DR0= 0000000000000000  DR1=0000000000000000 DR2=0000000000000000
> DR3=0000000000000000
>     DR0= 00000000ffff0ff0         DR7= 0000000000000400
>     EFER = 0000000000000000
>     Code= 93 a1 11 00 d0 a6 11 00 18 00 00 00 93 00 01 00 d0 4b 1c 00 <ff>
> ff ff ff 2c a7 11 00 ec ab 11 00 ff 26 00 00 00 00 00 00 04 00 00 00 42 00
> 00 00 02 00
> 
>    The software configuration is: QEMU-KVM-1.1.0, kvm-kmod-3.3 and
> linux-2.6.32. So what does this failure report mean and how can I locate
> the unsupported line in the guest kernel.
> 
Can you try 3.5 kernel?

>    With kind regards,
> 
> Yi

--
			Gleb.