Issue #8210 has been updated by Markus Falb.
Adrien Thebo wrote: > 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. If virt-what provides above mentioned interface to the CPUID instruction, well, all is good. If fall backs are acceptable depends. For kvm virtual machines, in my understanding, there are no reliable fall backs. I see only 2 solutions, you find a library that implements this CPUID beast or you do not and have it implemented yourself. I do not know how it is with other Virtualization methods. ---------------------------------------- Bug #8210: virtual => physical for kvm guests https://projects.puppetlabs.com/issues/8210#change-73902 Author: Markus Falb Status: Re-opened Priority: High Assignee: Category: library Target version: 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.
