Issue #8210 has been updated by Jeff McCune.

OK, I think I'm up to speed.

First, the CPUID instruction isn't a viable option because it's way too close 
to the underlying hardware for us to maintain in a portable way.

Second, I'm going to limit the scope of this issue to fixing the `virtual` fact 
when running on enterprise linux >= 5 hypervisors (RHEL, CentOS).  If you run 
into this problem on other operating systems, please create new ticket with the 
appropriate steps to reproduce the issue on those platforms and relate them to 
this issue.

The approach I'm going to take is to try and use `virt-what` if it's present, 
then fall back to the other work-arounds in some documented order of preference 
until we're able to get the desired value.

-Jeff
----------------------------------------
Bug #8210: virtual => physical for kvm guests
https://projects.puppetlabs.com/issues/8210#change-74072

Author: Markus Falb
Status: Accepted
Priority: Normal
Assignee: Jeff McCune
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.

Reply via email to