From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity 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 Message-ID: <4B137F10.906@redhat.com> References: <87skbzvdgd.fsf@spindle.srvr.nix> <4B125051.6010506@redhat.com> <87k4x9saqn.fsf@spindle.srvr.nix> <4B1283F5.5060204@redhat.com> <87y6lorjq6.fsf@spindle.srvr.nix> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Linux-Kernel-Mailing-List To: Nix Return-path: In-Reply-To: <87y6lorjq6.fsf@spindle.srvr.nix> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 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.