From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Simpson Subject: Re: Setting nx bit in virtual CPU Date: Wed, 07 Apr 2010 13:10:45 +0100 Message-ID: <4BBC7645.2070904@huskydog.org.uk> References: <4BB126AC.8040401@huskydog.org.uk> <4BB45CA2.5040304@redhat.com> <4BB65C9D.3070505@huskydog.org.uk> <4BB99F03.3020208@redhat.com> <4BBBB63B.60007@huskydog.org.uk> <4BBC1A86.6080506@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from server1.huskydog.org.uk ([81.187.172.195]:41774 "EHLO gordon.huskydog.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751216Ab0DGMKq (ORCPT ); Wed, 7 Apr 2010 08:10:46 -0400 In-Reply-To: <4BBC1A86.6080506@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/04/10 06:39, Avi Kivity wrote: > On 04/07/2010 01:31 AM, Richard Simpson wrote: >> >>> 2.6.27 should be plenty fine for nx. Really the important bit is that >>> the host kernel has nx enabled. Can you check if that is so? >>> >>> >> Umm, could you give me a clue about how to do that. It is some time >> since I configured the host kernel, but I do have a /proc/config.gz. >> Could I check by looking in that? >> > > The attached script should verify it. > rs% ./check-nx Traceback (most recent call last): File "./check-nx", line 17, in efer = msr().read(0xc0000080, 0) File "./check-nx", line 8, in __init__ self.f = file('/dev/msr0') IOError: [Errno 2] No such file or directory: '/dev/msr0' Sorry!