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/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
