Puppet » Facter

more from the list:–

2009/3/11 Avi Miller avi.miller@gmail.com

Trevor Hemsley wrote:

It appears that $virtual doesn’t work on Xen :(

It does for me. I get $virtual = xenu or xen0 on my boxes. Will have to check the exact Facter version, but I can tell you it’s whatever’s in EPEL.

Doesn’t seem to work well from a kvm vm either. Here the interesting facter bits:

facterversion => 1.5.4
lsbdistdescription => Ubuntu 8.04.2
physicalprocessorcount => 0
processor0 => QEMU Virtual CPU version 0.9.1
processor1 => QEMU Virtual CPU version 0.9.1
processorcount => 2
productname => Not Specified
rubyversion => 1.8.6
virtual => physical

Feel free to ping me if you need more info. I’m not sure how much time I can spend testing stuff in the next few days/weeks, but I could at least provide the devs an internet-reachable kvm machine with whichever distribution they see fit.

I think that this could be somehow related to the problem I encountered in #2011 , as this have been as well on a debian system. It looks like debian systems have other entries in /proc which will result in failing. At least this have been the problem in #2011 .

So anybody who encounters this bug, hence have the necessary systems, could try to debug the fact and see why it fails? You’ll find all the logic how facter decides what kind of system it is in lib/facter/virtual.rb and there isn’t much magic. I suspect that the necessary /proc entries or further things are missing, named differently or just in another location.

We use this which returns QEMU for both QEMU and KVM – sorry, no way to tell them apart AFAIK:

if FileTest.exists?(“/proc/cpuinfo”) txt = File.read(“/proc/cpuinfo”) result = “qemu” if txt =~ /QEMU/ end

I get a similar problem with VirtualBox (Centos 5.3 guest, Virtualbox 2.2.4 on OSX). Facter is the latest EPEL version

On VirtualBox, things are screwy:

[root@shoemaker ~]# facter manufacturer innotek GmbH [root@shoemaker ~]# facter virtual physical [root@shoemaker ~]# facter productname [root@shoemaker ~]# facter | grep productname productname => VirtualBox [root@shoemaker ~]#

(this is on the puppet + facter that are in EPEL:

root@shoemaker ~]# rpm -qa | egrep ‘(puppet|facter)’ puppet-0.24.8-1.el5.1 puppet-server-0.24.8-1.el5.1 facter-1.5.4-1.el5 [root@shoemaker ~]#

Gary Law wrote:

Not sure how to detect HyperV or Xen.

At least with kernel 2.6.30 and kvm-88 the “hypervisor” flag is set in cpuinfo cpu flags inside kvm guests. I’m also seeing patches here and there to add a “hypervisor” field to cpuinfo to show which hypervisor (ie. kvm, vmware, etc) but it doesn’t seem to be accepted in the kernel yet.

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 3
model name      : Pentium II (Klamath)
stepping        : 3
cpu MHz         : 2493.908
cache size      : 2048 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu de pse tsc msr pae mce cx8 apic sep pge cmov mmx fxsr sse sse2 pni hypervisor
bogomips        : 4987.81
clflush size    : 32
power management: