Issue #8210 has been updated by Ken Barber.
Status changed from Investigating to Accepted
Agreed its important - however I think the problem is specific to various
systems/configurations only.
Firstly - I find it odd that the original described behaviour changed with 1
cpu versus 2 on a Centos 5.6 guest.
I obviously don't get it in Debian - it represents the CPU as:
QEMU Virtual CPU version 0.14.1
Also dmidecode represents my manufacturer as 'Boschs', so using this won't
work, but it might be reasonable fall through for other systems.
For RHEL 6.1 (and I mean RHEL not Centos) I see:
QEMU Virtual CPU version (cpu64-rhel6)
So that works fine there as well. Interesting on RHEL6 I get:
Product Name: KVM
But this doesn't work the same on Debian. Go figure.
Anyway - I wouldn't mind a bit of a poll on this one ... at the moment the
confirmed operating system with this fault 'in ticket' is Centos 5.6. Any
others with the exact same problem where /proc/cpuinfo is different? I just
need to get an idea of what systems we'll have to setup to test this.
----------------------------------------
Bug #8210: virtual => physical for kvm guests
https://projects.puppetlabs.com/issues/8210
Author: Markus Falb
Status: Accepted
Priority: Normal
Assignee: shubhra sinha varma
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.
