public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Wolff <joe-w0bN8YRwa0o@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: unhandled vm exit on kvm36 with Etch 32 guest on AMD64
Date: Sun, 09 Sep 2007 20:25:00 -0700	[thread overview]
Message-ID: <46E4B90C.8000401@osdf.com> (raw)

Hello,

I'm getting "unhandled vm exit:0xb8002" running a Debian Etch guest 
under kvm36 on AMD64.

The host is a 4-core dual-dual AMD, and I was able to create the Debian 
Etch (4.0) guest image just fine, using a standard install, from the 
standard Debian DVD disc1: debian-40r0-i386-DVD-1.iso

Distro is Ubuntu Gutsy, kernel is brand-new 2.6.22-11-server from the 
Gutsy repo. The KVM36 was installed via apt-pinning from the Debian 
(sid) repo (they're compatible - dependencies all met). The KVM36 is the 
only thing from the sid repo.

I originally upgraded to kvm36 because I was having this problem on the 
default Gutsy kvm28, and the Guest Status page for Etch says kvm29 works 
(albeit with Intel), but this is the same error I was getting with kvm28.


Here's the commandline and the subsequent regdump:

root@librehost-g64:/vm/143#  kvm -vnc :1 -k en-us -net 
nic,macaddr=de:ad:be:ef:01:43 -net tap -monitor 
telnet::23143,server,nowait,nodelay -cdrom 
/iso/debian-40r0-i386-DVD-1.iso -append vga=771 debian-40r0-i386.8G.qc2

In /etc/kvm/kvm-ifup, adding: tap0

unhandled vm exit:  0xb8002
rax 00000000c0318000 rbx 0000000000000fa0 rcx 0000000000000fa0 rdx 
00000000c00b8000
rsi 00000000c00b8000 rdi 00000000c110a980 rsp 00000000c0319fb8 rbp 
00000000c110a980
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
0000000000000000
rip 00000000c01bc276 rflags 00000206
cs 0060 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 0 avl 0)
ds 007b (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 2 l 0 g 1 avl 0)
es 007b (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0068 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0)
fs 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gs 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
tr 0080 (c11006c0/00002073 p 1 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0)
ldt 0088 (c0352020/00000027 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt c1109000/ff
idt c030f000/7ff
cr0 80050033 cr2 0 cr3 34f000 cr4 690 cr8 0 efer 0
Aborted
root@librehost-g64:/vm/143#



Let me know,

Cheers,
joe



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

             reply	other threads:[~2007-09-10  3:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10  3:25 Joseph Wolff [this message]
     [not found] ` <46E4B90C.8000401-w0bN8YRwa0o@public.gmane.org>
2007-09-10  7:35   ` unhandled vm exit on kvm36 with Etch 32 guest on AMD64 Avi Kivity
     [not found]     ` <46E4F3BE.5040807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-10 16:28       ` Joseph Wolff
2007-09-10 12:46   ` Uri Lublin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46E4B90C.8000401@osdf.com \
    --to=joe-w0bn8yrwa0o@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox