From: Richard Simpson <rs1002@huskydog.org.uk>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Setting nx bit in virtual CPU
Date: Wed, 07 Apr 2010 21:38:10 +0100 [thread overview]
Message-ID: <4BBCED32.30304@huskydog.org.uk> (raw)
In-Reply-To: <4BBC7958.9010903@redhat.com>
On 07/04/10 13:23, Avi Kivity wrote:
> On 04/07/2010 03:10 PM, Richard Simpson wrote:
>> 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?
>>> The attached script should verify it.
>> IOError: [Errno 2] No such file or directory: '/dev/msr0'
>
> Run as root, please. And check first that you have a file named
> /dev/cpu/0/msr.
Doh!
gordon Code # ./check-nx
nx: enabled
gordon Code #
OK, seems to be enabled just fine. Any other ideas? I am beginning to
get that horrible feeling that there isn't a real problem and it is just
me being dumb!
next prev parent reply other threads:[~2010-04-07 20:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 22:16 Setting nx bit in virtual CPU Richard Simpson
2010-03-30 2:12 ` Chris Wright
2010-03-30 20:42 ` Richard Simpson
2010-04-01 8:43 ` Avi Kivity
2010-04-02 21:07 ` Richard Simpson
2010-04-05 8:27 ` Avi Kivity
2010-04-06 22:31 ` Richard Simpson
2010-04-07 5:39 ` Avi Kivity
2010-04-07 12:10 ` Richard Simpson
2010-04-07 12:23 ` Avi Kivity
2010-04-07 20:38 ` Richard Simpson [this message]
2010-04-07 20:48 ` Avi Kivity
2010-04-07 23:13 ` Richard Simpson
2010-04-08 7:23 ` Avi Kivity
2010-04-08 23:55 ` Richard Simpson
2010-04-10 19:34 ` Avi Kivity
2010-04-08 8:52 ` Andre Przywara
2010-04-08 21:23 ` Richard Simpson
2010-04-09 23:45 ` Andre Przywara
2010-04-12 21:15 ` Richard Simpson
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=4BBCED32.30304@huskydog.org.uk \
--to=rs1002@huskydog.org.uk \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.