Markus Hochholdinger
2008-Apr-10 15:48 UTC
Re: [Xen-devel] detecting a xen environment easily
Hi, Am Donnerstag, 10. April 2008 18:36 schrieb Guillaume Rousse: [..]> 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.you could look on the hardware (video card, pci bus, ..) to identify a hvm!? -- greetings eMHa _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 ? -- Guillaume Rousse Moyens Informatiques - INRIA Futurs Tel: 01 69 35 69 62 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Apr 10, 2008 at 12:36 PM, Guillaume Rousse < Guillaume.Rousse@inria.fr> 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: http://xen.markmail.org/search/?q=Shell%20test%20for%20pv%20vs%20hvm#query:Shell%20test%20for%20pv%20vs%20hvm+page:1+mid:xurts65ly6b3xlch+state:results Not sure if it is exactly what you are looking for, but maybe some ideas... The markmail search is pretty good, by the way. Regards, Todd> -- > Guillaume Rousse > Moyens Informatiques - INRIA Futurs > Tel: 01 69 35 69 62 > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel