On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote: > On 23.06.2013 19:36, Gleb Natapov wrote: > > On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote: > >> On 23.06.2013 09:51, Gleb Natapov wrote: > >>> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote: > >>>>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94 > >>>>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu > >>>>> monitor after the hang. > >>>> > >>>> > >>>> 25391454e73e3156202264eb3c473825afe4bc94 > >>>> emulate_invalid_guest_state=0 > >>>> > >>> Very interesting. Looks like somewhere during TPR access FS > >>> register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin > >>> and try again? This will disable some code paths during TPR access and > >>> will narrow down the issue. > >> > >> > >> Doing this, qemu complains > >> "Could not open option rom 'kvmvapic.bin': No such file or directory", > >> but the virtual machine boots successful with > >> emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1. > >> > > Hmm, I think we ate close. Can you try with upstream qemu? > > > >> kvmvapic.bin comes with Debian package "seabios 1.7.2-3". > > I already tried this with the Debian package qemu-kvm 1.5.0+dfsg-4. And it didn't work? Mind trying some debug kernel patches? I suspect your CPU does something no CPU I have do, so I want to verify it. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
