From: Avi Kivity <avi@redhat.com>
To: Nix <nix@esperi.org.uk>
Cc: 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: Mon, 30 Nov 2009 10:15:12 +0200 [thread overview]
Message-ID: <4B137F10.906@redhat.com> (raw)
In-Reply-To: <87y6lorjq6.fsf@spindle.srvr.nix>
On 11/30/2009 01:31 AM, Nix wrote:
> On 29 Nov 2009, Avi Kivity stated:
>
>> Most likely, either this or something similar is called on a userspace
>> device driver. Can you check if this is triggered by starting X?
>>
> *sigh* I just wasted twenty minutes trying to find some way, *any* way
> to not start X under Ubuntu Karmic, so as to test this. None is evident.
> I can't even figure out what and where in upstart's horrific dependency
> tangle is starting X in the first place: deleting suspicious-looking
> things from rc*.d has no effect at all. I can't even tell if rc*.d is
> still used, nor if the concept of runlevel is even meaningful any
> longer. There are lots of things googleable that claim to say how to do
> this, but all relate to the non-dependency-based inittab-emulating
> method used in previous Ubuntu versions.
>
> Anyone know?
>
At least on Fedora, you you can change the runlevel in /etc/inittab (the
sole remaining function of the file).
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-11-30 8:15 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 [this message]
2009-11-30 12:05 ` Alejandro Riveira Fernández
2009-11-30 21:40 ` Nix
2009-12-01 9:59 ` Avi Kivity
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=4B137F10.906@redhat.com \
--to=avi@redhat.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