WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] No Full Virtualisation with Intel Core 2 Duo T5500 Mobil

To: "Karl Stevens" <karl@xxxxxxxxxxxxx>, "Falko Tesch" <falko.tesch@xxxxxxxxxxx>
Subject: RE: [Xen-users] No Full Virtualisation with Intel Core 2 Duo T5500 Mobile CPU?
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Tue, 13 Feb 2007 11:00:57 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Feb 2007 10:14:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45D0BD77.9040801@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdO20MB39SOotxcSemvJ10wTWyY2AAebOHQ
Thread-topic: [Xen-users] No Full Virtualisation with Intel Core 2 Duo T5500 Mobile CPU?
 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Karl Stevens
> Sent: 12 February 2007 19:18
> To: Falko Tesch
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] No Full Virtualisation with Intel 
> Core 2 Duo T5500 Mobile CPU?
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Falko Tesch wrote:
> > Hello,
> > 
> > I have some interesting issue with Intel VT CPU and XEN 3.0.2:
> > 
> > I'm running XEN 3.0.2 on a MSI Fuzzy 945GM2 Mainboard
> > 
> (http://www.msi.com.tw/program/products/ic/ic_detail.php?prod_
> no=4) with
> > a Intel Core 2 Duo Mobile CPU (T5500).
> > 
> > When booting the mainboard BIOS says it found a EM64T CPU, which is
> > AFAIK the code for a Intel CPU with Virtualisation Technologie.
> > But whether Linux nor XEN detects this CPU as a VT CPU.

Just to clarify, EM64T is Intel's name for x86-64 (aka AMD64), so it's
the 64-bit extensions to the x86 architecture. This is NOT directly
related to Intel's VT. 

> > 
> > Who's right, the mainboard or Linux?
> 
> Probably both.  Intel allows the BIOS to disable the VT 
> instructions at
> boot time.

Since you're looking at different features, we can't say one is right or
wrong. Obviously, the core-duo processor shouls support VT and 64-bit
architecture.
> 
> If the BIOS allows you to enable it (most manufacturers leave it
> disabled by default) you will need to power-cycle the machine after
> doing so (just rebooting won't work - the machine needs to be off for
> the option to be enabled properly.)

This is correct, you will need to enable the feature in BIOS (or
technically speaking "Not set the disable bit"!) in the BIOS during
startup. Since this is a "can't clear" bit, once it's been written, it
can't be reset in software, you'll have to power-cycle as Karl says. 

It's worth noting also that there are BIOS's that don't allow this bit
to be turned on/off - they just lock it without giving the user any
options to change the setting. 

--
Mats
> 
> - -Karl
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> 
> iD8DBQFF0L13r6qWhNgoahURAs94AJ9wVrgIngIMKVf19XxE9uwb5QAjEwCbB+KW
> KFWDxOlDM5p28LDY0M+Yh64=
> =xiLs
> -----END PGP SIGNATURE-----
> 
> __ 
>     This communication is intended for the use of the 
> recipient to whom it
>     is addressed, and may contain confidential, personal, and 
> or privileged
>     information. Please contact us immediately if you are not 
> the intended
>     recipient of this communication, and do not copy, 
> distribute, or take
>     action relying on it. Any communications received in error, or
>     subsequent reply, should be deleted or destroyed.
> ---
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users