Issue #8210 has been updated by Adrien Thebo. Assignee deleted (shubhra sinha varma)
If I recall correctly, checking the CPUID instruction means having native compiled code - or at least, when I looked at virt-what it was building a tiny binary to do this detection. Considering facter can run on anything that ruby runs on, we would have to build a LOT of binaries for this detection, since it's a little crazy to compile code upon package installation. Building this behavior into facter itself seems like a no-go. We could have a resolution method that attempts to use virt-what if it's available but falls back to other methods if it's not present. However, I would expect that people would probably want virt-what as a required dependency and we try to keep facter light on dependency. ---------------------------------------- Bug #8210: virtual => physical for kvm guests https://projects.puppetlabs.com/issues/8210#change-63344 Author: Markus Falb Status: Re-opened Priority: Normal Assignee: Category: library Target version: 1.6.x Keywords: Branch: Affected Facter version: 1.6.2 The Output from /proc/cpuinfo can not used reliable for telling that it is a kvm virtual machine. On a CentOS 5.6 kvm Host with CentOS guests /proc/cpuinfo tells me: for a smp guest model name : QEMU Virtual CPU version 0.9.1 with only one cpu in the guest: model name : Pentium II (Klamath) but in both cases: $ dmidecode -t 4 ... Manufacturer: QEMU ... I believe it is possible to specify what cpu is used so on the commandline, so relying on the model name is not always working For more information please also have a look at <br>[https://bugzilla.redhat.com/show_bug.cgi?id=707523](https://bugzilla.redhat.com/show_bug.cgi?id=707523) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
