From mboxrd@z Thu Jan  1 00:00:00 1970
From: Johannes Bauer <dfnsonfsduifb@gmx.de>
Subject: Re: KVM entry failed, hardware error
Date: Thu, 07 Jun 2012 17:39:19 +0200
Message-ID: <4FD0CB27.9040803@gmx.de>
References: <4FCB55FE.2010808@gmx.de> <4FCB59A2.4020008@redhat.com> <4FCB6045.1050002@gmx.de> <4FCF7CE6.3050901@redhat.com> <4FCF9C78.3090406@gmx.de> <4FD05459.7020702@redhat.com> <4FD07C5D.3080001@gmx.de> <4FD0886C.2050304@redhat.com> <4FD0C02B.70103@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mailout-de.gmx.net ([213.165.64.23]:48870 "HELO
	mailout-de.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with SMTP id S1750795Ab2FGPjW (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 7 Jun 2012 11:39:22 -0400
In-Reply-To: <4FD0C02B.70103@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 07.06.2012 16:52, Avi Kivity wrote:

> Please try the big-real-mode branch again.  It contains emulation for
> the missing instruction, plus a bunch of tweaks which allowed it to boot
> Fedora 17 smp with emulate_invalid_guest_state=1.

Progress!

So now I'm on

Linux joequad 3.5.0-rc1-46078-g54d5c7c #2 SMP PREEMPT Thu Jun 7 17:11:38
CEST 2012 x86_64 Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
GenuineIntel GNU/Linux

And see the following (kind of weird) behavior: I can boot up now. But
it's bound to some condition:

When not using "-monitor stdio", I have the same behavior as before.

When using "-monitor stdio", it locks up occasionaly, but appears to
resume operation whenever I type "info registers". That way I was able
to boot up (by entering about 50 times "info registers", then it had
left real mode and booted up normally).

I was first a bit confused, but this is definitely what I'm seeing:
Because of shutting down the VM I had put the guest in a "Windows
Recovery" mode where a text-mode progress bar appears with the text
"Windows is loading files...". The bar locks up -- when I type "info
registers", it progresses about 2-4 characters and locks up again (until
it's fully loaded, then it just works).

Note that "c" does NOT cause the VM to resume, only "info registers"
does. dmesg shows nothing out of the ordinary.

But I think we're getting somewhere! Thank you very much for your
support already!

Best regards,
Joe