From: Avi Kivity <avi@redhat.com>
To: Nix <nix@esperi.org.uk>
Cc: "Alejandro Riveira Fernández" <ariveira@gmail.com>,
kvm@vger.kernel.org,
Linux-Kernel-Mailing-List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31.5 x86-64 KVM: 'emulation failed (pagetable) rip 7fb49335da7b 66 0f 7f 07'
Date: Tue, 01 Dec 2009 11:59:05 +0200 [thread overview]
Message-ID: <4B14E8E9.8050305@redhat.com> (raw)
In-Reply-To: <87d42zr8rl.fsf@spindle.srvr.nix>
On 11/30/2009 11:40 PM, Nix wrote:
>
> So I started with -vga std. The emulation failed flood is unaffected
> (strangely it's not consistent: it happens about half the time). As soon
> as I issue a 'stop gdm', X exits and the emulation flood halts: but
> although there are other getties running I can't find a way to switch to
> them, as qemu has stolen Ctrl-Alt for its own purposes: so the system is
> pretty much useless (maybe I should get an sshd up and try to restart
> things from there). (I've never needed to do this before: either my
> qemus have been text mode all the time, or X with one console.)
>
> Surely switching VTs is possible: any clues?
>
'sendkey alt-ctrl-f2' from the qemu monitor.
So it looks like it is X related, and we'll have no choice other than to
emulate the instruction. Annoying, since we don't emulate sse
instructions yet.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-01 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 21:56 2.6.31.5 x86-64 KVM: 'emulation failed (pagetable) rip 7fb49335da7b 66 0f 7f 07' Nix
2009-11-29 10:43 ` Avi Kivity
2009-11-29 13:48 ` Nix
2009-11-29 14:23 ` Avi Kivity
2009-11-29 23:31 ` Nix
2009-11-30 8:15 ` Avi Kivity
2009-11-30 12:05 ` Alejandro Riveira Fernández
2009-11-30 21:40 ` Nix
2009-12-01 9:59 ` Avi Kivity [this message]
2009-12-01 10:12 ` Avi Kivity
2009-12-02 13:25 ` Avi Kivity
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=4B14E8E9.8050305@redhat.com \
--to=avi@redhat.com \
--cc=ariveira@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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