From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Setting nx bit in virtual CPU Date: Thu, 08 Apr 2010 10:23:32 +0300 Message-ID: <4BBD8474.6060809@redhat.com> 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> <4BBC7645.2070904@huskydog.org.uk> <4BBC7958.9010903@redhat.com> <4BBCED32.30304@huskydog.org.uk> <4BBCEFA5.3050900@redhat.com> <4BBD1198.6010304@huskydog.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Richard Simpson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:38858 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932129Ab0DHHXl (ORCPT ); Thu, 8 Apr 2010 03:23:41 -0400 In-Reply-To: <4BBD1198.6010304@huskydog.org.uk> Sender: kvm-owner@vger.kernel.org List-ID: On 04/08/2010 02:13 AM, Richard Simpson wrote: > >>> 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! >>> >>> >> I really hope so, because I am out of ideas... :) >> >> Can you verify check-nx returns disabled on the guest? >> Does /proc/cpuinfo show nx in the guest? >> >> > OK, time for a summary: > > Host: /proc/cpuinfo shows 'nx' and check-nx shows 'enabled' > > Guest: /proc/cpuinfo doesn't show nx and check-nx shows 'disabled' > Strange. Can you hack qemu-kvm's cpuid code where it issues the ioctl KVM_SET_CPUID2 to show what the data is? I'm not where that code is in your version of qemu-kvm. -- error compiling committee.c: too many arguments to function