-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

To be more specific on my last post:

- -smbios type=1[,manufacturer=str][,product=str] 
[,version=str][,serial=str][,uuid=uuid][,sku=str] [,family=str]

You can set any, or all, of these fields to be whatever you wish them to be so 
this may not be a foolproof way of obtaining information.

Trevor

On 08/29/2011 10:00 PM, [email protected] wrote:
> 
> Issue #8210 has been updated by Markus Falb.
> 
> 
> You could leave away the funny switches and just do
> <pre>
> $ dmidecode
> ... look if you find something worthfully in this lot of information ...
> </pre>
> 
> I just found
> <pre>
> $ dmidecode -t 1
> ...
>       Product Name: KVM
> ...
> </pre>
> 
> or shorter
> <pre>
> $ dmidecode -s system-product-name
> KVM
> </pre>
> ----------------------------------------
> Bug #8210: virtual => physical for kvm guests
> https://projects.puppetlabs.com/issues/8210
> 
> Author: Markus Falb
> Status: Investigating
> Priority: Normal
> Assignee: Adrien Thebo
> Category: library
> Target version: 
> Keywords: 
> Branch: 
> Affected Facter version: 
> 
> 
> 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)
> 
> 

- -- 
Trevor Vaughan
 Vice President, Onyx Point, Inc.
 email: [email protected]
 phone: 410-541-ONYX (6699)
 pgp: 0x6C701E94

- -- This account not approved for unencrypted sensitive information --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJOXMnvAAoJECNCGV1OLcypiRoH/0PRdlKA7qCx6H3C0qNadVB0
JSCI4uGpPqljyQzRqhiI8ukH1cmNFHDNvmCcXRA9WzLPUeg+L4N1bxrna17y3zJ/
CF70B6Y3OF70hmQwoSz59M4YoYlvBkA1dSlaLPzVvfyiJElOIdFF0gbb5xp4UmXi
xiJnE1bddvNtjR9gMVAm4cbgndPCNXTX6KXoXiEhmjCe87XfNGhrOguGtTRJsb4l
uLLg/52U33FIhJsra9dn7Uu0/aPZ8hhuVYP0A9fsmR6WU8btxOTQGqvMmSWKZ3ag
AxwOum1O84xsyElLdj/EDmiL4U9SKBKnvuZcVfzDw8gz84g1Tp65SNT8FkWx5zU=
=Wf1i
-----END PGP SIGNATURE-----

-- 
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.

<<attachment: tvaughan.vcf>>

Reply via email to