[Facter - Bug #10879] (Unreviewed) Does not detect KVM VM as a virtual machine when kvm provides an existing CPU

[tic...@puppetlabs.com]

Issue #10879 has been reported by Frederik Himpe.

---

Bug #10879: Does not detect KVM VM as a virtual machine when kvm provides an existing CPU

• Author: Frederik Himpe
• Status: Unreviewed
• Priority: Normal
• Assignee:
• Category:
• Target version:
• Keywords:
• Branch:
• Affected Facter version: 1.6.2

I am using custom CPU flags to launch a qemu-kvm virtual machine: qemu-kvm is launched with this parameter: -cpu phenom,+wdt,+skinit,+osvw,+3dnowprefetch,+misalignsse,+sse4a,+abm,+cr8legacy,+extapic,+cmp_legacy,+lahf_lm,+rdtscp,+pdpe1gb,+popcnt,+cx16,+ht,+vme

Because of that, /proc/cpuinfo does not mention QEMU as CPU vendor anymore but mentions a real physical CPU. Now facter thinks that I am using a physical machine:

facter | grep virtual¶

is_virtual => false virtual => physical

cat /proc/cpuinfo¶

processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom™ 9550 Quad-Core Processor stepping : 3 cpu MHz : 2294.148 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb lm up rep_good extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch bogomips : 4588.29 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management:

$ lspci 00:00.0 Host bridge: Intel Corporation 440FX – 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB Controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:05.0 RAM memory: Red Hat, Inc Virtio memory balloon

dmidecode¶

dmidecode 2.9¶

SMBIOS 2.4 present. 10 structures occupying 263 bytes. Table at 0x3FFFFEF0.

Handle 0x0000, DMI type 0, 24 bytes BIOS Information

Vendor: Bochs
Version: Bochs
Release Date: 01/01/2007
Address: 0xE8000
Runtime Size: 96 kB
ROM Size: 64 kB
Characteristics:
    BIOS characteristics not supported
    Targeted content distribution is supported
BIOS Revision: 1.0

Handle 0x0100, DMI type 1, 27 bytes System Information

Manufacturer: Bochs
Product Name: Bochs
Version: Not Specified
Serial Number: Not Specified
UUID: FB5A8067-81D7-9001-7CE5-D791549FA4AA
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified

Handle 0x0300, DMI type 3, 20 bytes Chassis Information

Manufacturer: Bochs
Type: Other
Lock: Not Present
Version: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: Unknown
OEM Information: 0x00000000

Handle 0x0401, DMI type 4, 32 bytes Processor Information

Socket Designation: CPU01
Type: Central Processor
Family: Other
Manufacturer: Bochs
ID: 23 0F 10 00 FF FB 8B 07
Version: Not Specified
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided

Handle 0x1000, DMI type 16, 15 bytes Physical Memory Array

Location: Other
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 1 GB
Error Information Handle: Not Provided
Number Of Devices: 1

Handle 0x1100, DMI type 17, 21 bytes Memory Device

Array Handle: 0x1000
Error Information Handle: 0x0000
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: None

Handle 0x1300, DMI type 19, 15 bytes Memory Array Mapped Address

Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Array Handle: 0x1000
Partition Width: 0

Handle 0x1400, DMI type 20, 19 bytes Memory Device Mapped Address

Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1

Handle 0x2000, DMI type 32, 11 bytes System Boot Information

Status: No errors detected

Handle 0x7F00, DMI type 127, 4 bytes End Of Table

---

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

[tic...@puppetlabs.com]

Issue #10879 has been updated by Frederik Himpe.

Just found out via the Debian bug tracker that this was already reported here: http://projects.puppetlabs.com/issues/8210

[tic...@puppetlabs.com]

Issue #10879 has been updated by James Turnbull.

• Status changed from Unreviewed to Duplicate

Duplicate of #8210.

---

Bug #10879: Does not detect KVM VM as a virtual machine when kvm provides an existing CPU

• Author: Frederik Himpe
• Status: Duplicate