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/
Home Products Support Community News


Re: [Xen-devel] detecting a xen environment easily

To: "Guillaume Rousse" <Guillaume.Rousse@xxxxxxxx>
Subject: Re: [Xen-devel] detecting a xen environment easily
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Thu, 10 Apr 2008 12:46:48 -0400
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 10 Apr 2008 09:47:13 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=x+Ttykt5XHG+8GVbiJb5PCIer9+b7QTj9Biu2SloGmo=; b=pLwQn3Z3Ld4wxjmZOm1S8btmShE+8joYL9bdiC5GwM4twKFvPZiu4yXCIh7O/ZoyiaWA2TCVGlbhBnUV1Bbfo610dzAFlvxCJVJpTOjSD2Tj6CGoRgSjkVzE+VKfPWnVsr3p1ZS5yuW7pN0R/aK6AsSpFtpW8FAIAnBC5R337Cs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=G3VEfZe8Tu93dVE2OGvhYnXLMYG5K3YAr1p3PEr4vDc8Cqtjn6Vcxtzr6g3EWWI5oKyxCkGoHwcsJ16473b/+r59U+Ux+1nOhV/qb/LyiPjhI6C15TLBGfi0/KRcFiKh9xfOM9S8/y/8jLsPc503BNKhJn+A84DV8sMxsXQtu7g=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47FE4212.5050707@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <47FE4212.5050707@xxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On Thu, Apr 10, 2008 at 12:36 PM, Guillaume Rousse <Guillaume.Rousse@xxxxxxxx> wrote:
Hello list.

I'm looking for a way to easily segregate paravirtualized hosts,
hardware virtualized hosts, and native hosts for sysadmin purpose
(installing specific software or configuration files through cfengine).

So far, I found the presence of a /proc/xen directory indicated either a
paravirtualized host, or a dom0 native host, with the additional
presence of /proc/xen/xsd_* files distinguishing between the two last
ones. However, I didn't found any way to distinguish between other
native host (non dom0 ones), and hardware virtualized hosts.

In "Definitive guide to the xen hypervisor" book from D. Chisnall, i
found some C code allowing to do it, based on CPUID cpu instruction
usage. I didn't tried it yet, but isn't it any way to do something
similar with non-compiled code, for portability issues (distributing a
python script is far easier than providing as much different binaries
than monitored platform) ?

Also, is there any better way to achieve what I'm currently trying to do ?

Take a look here:


Not sure if it is exactly what you are looking for, but maybe some ideas...

The markmail search is pretty good, by the way.


Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62

Xen-devel mailing list

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>