Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-700

Detect KVM even when generic CPU Model Name is used.

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FACT 2.3.0
    • Component/s: Community
    • Labels:
      None
    • Template:

      Description

      We recently changed our VPS's CPU models from "QEMU Virtual CPU version 1.7.1"
      to "Westmere E56xx/L56xx/X56xx (Nehalem-C)". This led to facter
      errorenously detecting a physical environment rather than a virtualized one.

      This PR ( https://github.com/puppetlabs/facter/pull/774 ) checks both pciconf and dmidecode for any signs of a virtualized.
      environment. KVM relies on bochs for emulating its BIOS. But if there's no
      virtio device and no telling CPU Model Name there is no way to distinct
      between plain Bochs and Bochs used together with KVM (at least not that I'm aware of). Therefore, I added an extra virtual type called 'bochs'. At least it will result either way in is_virtual=true.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              Freeaqingme Dolf Schimmel
              QA Contact:
              Eric Thompson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support