linux-kernel - Re: 2.6.31.5 x86-64 KVM: 'emulation failed (pagetable) rip 7fb49335da7b 66 0f 7f 07'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 29 Nov 2009 23:31:45 +0000
From:	Nix <nix@...eri.org.uk>
To:	Avi Kivity <avi@...hat.com>
Cc:	kvm@...r.kernel.org,
	Linux-Kernel-Mailing-List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31.5 x86-64 KVM: 'emulation failed (pagetable) rip 7fb49335da7b 66 0f 7f 07'

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/