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: Fri, 02 Apr 2010 22:07:41 +0100 [thread overview]
Message-ID: <4BB65C9D.3070505@huskydog.org.uk> (raw)
In-Reply-To: <4BB45CA2.5040304@redhat.com>
Nope, both Kernels are 64 bit.
uname -a Host: Linux gordon 2.6.27-gentoo-r8 #5 Sat Mar 14 18:01:59 GMT
2009 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux
uname -a Guest: Linux andrew 2.6.28-hardened-r9 #4 Mon Jan 18 22:39:31
GMT 2010 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux
As you can see, both kernels are a little old, and I have been wondering
if that might be part of the problem. The Guest one is old because that
is the latest stable hardened version in Gentoo. The host one is old
because of:
(gordon:~) rs10% uptime
22:01:37 up 374 days, 23:29, 1 user, load average: 1.09, 0.42, 0.18
Now that I have managed to smash the psychologically important 1 year
uptime for the first time ever (Woo!) I shall probably upgrade the host
kernel in the near future. Of course, it is important to remember that
with the --no-kvm switch it works just fine (only slowly) with exactly
the same two kernels.
Thanks
On 01/04/10 09:43, Avi Kivity wrote:
> On 03/30/2010 01:16 AM, Richard Simpson wrote:
>> Hello,
>>
>> Summary: How can I have a virtual CPU with the nx bit set whilst
>> enjoying KVM acceleration?
>>
>> My Host - AMD Athlon(tm) 64 Processor 3200+ running Gentoo
>> My VM - KVM running hardened Gentoo
>> My KVM version - 0.12.3
>> My Task - Implement restricted secure VM to handle services exposed to
>> internet.
>> My Command - kvm -hda /dev/mapper/vols-andrew -kernel ./bzImage -append
>> root=/dev/hda2 -cpu host -runas xxx -net nic -net user -m 256 -k en-gb
>> -vnc :1 -monitor stdio
>>
>>
>
>
> Are you running a 32-bit non-pae host kernel? In that case, nx is
> disabled both for the guest and host. Switch to a pae (or 64-bit)
> kernel and all should be well.
>
next prev parent reply other threads:[~2010-04-02 21:07 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 [this message]
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
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=4BB65C9D.3070505@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox