public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Bauer <dfnsonfsduifb@gmx.de>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM entry failed, hardware error
Date: Thu, 07 Jun 2012 17:39:19 +0200	[thread overview]
Message-ID: <4FD0CB27.9040803@gmx.de> (raw)
In-Reply-To: <4FD0C02B.70103@redhat.com>

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

  reply	other threads:[~2012-06-07 15:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-03 12:18 KVM entry failed, hardware error Johannes Bauer
2012-06-03 12:33 ` Avi Kivity
2012-06-03 13:01   ` Johannes Bauer
2012-06-03 13:43     ` Avi Kivity
2012-06-03 16:25       ` Johannes Bauer
2012-06-04  8:53         ` Gleb Natapov
2012-06-04  8:56           ` Avi Kivity
2012-06-04 18:28           ` Johannes Bauer
2012-06-04 18:32             ` Johannes Bauer
2012-06-05 13:59             ` David Ahern
2012-06-06 18:19               ` Johannes Bauer
2012-06-06 15:53     ` Avi Kivity
2012-06-06 18:07       ` Johannes Bauer
2012-06-07  7:12         ` Avi Kivity
2012-06-07 10:03           ` Johannes Bauer
2012-06-07 10:54             ` Avi Kivity
2012-06-07 14:52               ` Avi Kivity
2012-06-07 15:39                 ` Johannes Bauer [this message]
2012-06-07 17:25                   ` Avi Kivity
2012-06-07 19:14                     ` Johannes Bauer
2012-06-10 15:19                       ` Avi Kivity
2012-06-12 10:23                         ` Johannes Bauer
2012-06-12 10:45                           ` Avi Kivity
2012-06-07 19:46                     ` Johannes Bauer
2012-06-07 19:54                       ` Johannes Bauer
2012-06-03 13:04   ` Johannes Bauer

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=4FD0CB27.9040803@gmx.de \
    --to=dfnsonfsduifb@gmx.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.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