SCIENTIFIC-LINUX-USERS Archives

June 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dr Andrew C Aitchison <[log in to unmask]>
Reply To:
Dr Andrew C Aitchison <[log in to unmask]>
Date:
Wed, 16 Jun 2010 10:58:44 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (31 lines)
On Wed, 16 Jun 2010, Andrey Y. Shevel wrote:

> Hello everybody,
>
> I just discovered in my CPU
>
> model name      : Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz
>
> under
>
> [root@pcfarm-new ~]# uname -a
> Linux pcfarm-new.pnpi.spb.ru 2.6.18-194.3.1.el5xen #1 SMP Fri May 7 02:05:32 
> EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
>
> that there is no flag 'vmx'
>
> [root@pcfarm-new ~]# grep vmx /proc/cpuinfo; echo $?
> 1
>
> At the same time when I boot another kernel 'xen.gz-2.6.18-128.1.1.el5'
> the flag 'vmx' is in place

Hmm. The flags are indeed different with xen and non-xen kernels.

I guess this is because with a xen kernel you are looking at the 
capabiities of the *virtual* CPU, rather than the bare metal processor ?

-- 
Dr. Andrew C. Aitchison		Computer Officer, DPMMS, Cambridge
[log in to unmask]	http://www.dpmms.cam.ac.uk/~werdna

ATOM RSS1 RSS2