From: Joseph Wolff <joe-w0bN8YRwa0o@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: unhandled vm exit on kvm36 with Etch 32 guest on AMD64
Date: Mon, 10 Sep 2007 09:28:07 -0700 [thread overview]
Message-ID: <46E57097.3070306@osdf.com> (raw)
In-Reply-To: <46E4F3BE.5040807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Here's the dmesg snippet from the run:
[47823.616622] device tap0 entered promiscuous mode
[47823.616633] audit(1189441272.489:14): dev=tap0 prom=256 old_prom=0
auid=4294967295
[47823.616638] br0: port 2(tap0) entering learning state
[47830.252510] pf_interception: emulate fail
[47830.308439] br0: port 2(tap0) entering disabled state
[47830.351370] device tap0 left promiscuous mode
[47830.351386] audit(1189441279.240:15): dev=tap0 prom=0 old_prom=256
auid=4294967295
[47830.351390] br0: port 2(tap0) entering disabled state
So just the "pf_interception: emulate fail" is all.
joe
Avi Kivity wrote:
> Joseph Wolff wrote:
>> Hello,
>>
>> I'm getting "unhandled vm exit:0xb8002" running a Debian Etch guest
>> under kvm36 on AMD64.
>>
>>
>
> This is a badly reported emulation failure.
>
> Is there anything in dmesg like "emulation failed but !mmio_needed?"?
>
>
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2007-09-10 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 3:25 unhandled vm exit on kvm36 with Etch 32 guest on AMD64 Joseph Wolff
[not found] ` <46E4B90C.8000401-w0bN8YRwa0o@public.gmane.org>
2007-09-10 7:35 ` Avi Kivity
[not found] ` <46E4F3BE.5040807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-10 16:28 ` Joseph Wolff [this message]
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=46E57097.3070306@osdf.com \
--to=joe-w0bn8yrwa0o@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.