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: Wed, 06 Jun 2012 20:07:52 +0200 [thread overview]
Message-ID: <4FCF9C78.3090406@gmx.de> (raw)
In-Reply-To: <4FCF7CE6.3050901@redhat.com>
On 06.06.2012 17:53, Avi Kivity wrote:
>>> # rmmod kvm_intel
>>> # modprobe kvm_intel emulate_invalid_guest_state=1
>>>
>>> Warning: experimental code.
>>
>> Tried it out -- I don't get the error anymore, but qemu just hangs on
>> boot with 100% CPU. :-(
>
> Please retry with
>
> git://git.kernel.org/pub/scm/virt/kvm/kvm.git big-real-mode
Same thing:
$ uname -a
Linux joequad 3.5.0-rc1-46053-gf2ebd42 #1 SMP PREEMPT Wed Jun 6 19:49:21
CEST 2012 x86_64 Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
GenuineIntel GNU/Linux
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.5.0-rc1-46053-gf2ebd42 root=/dev/sda1 ro
kvm-intel.emulate_invalid_guest_state=1
QEmu hangs with 100% CPU. Is there anything I can try to be able to tell
you *where* it hangs?
Best regards,
Johannes
next prev parent reply other threads:[~2012-06-06 18:07 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 [this message]
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
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=4FCF9C78.3090406@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 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.