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

Xen virtual fact reported as hyperv when viridan extensions enabled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Needs Information
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: FACT 3.1.8, FACT 3.3.0
    • Fix Version/s: None
    • Component/s: None
    • Template:
    • Team:
      Platform OS

      Description

      Under some circumstances when Xen is configured with Viridian extensions enabled the version of virt-what included with Puppet returns three lines of output, hyperv followed by xen then xen-domU/xen-dom0. This results in the virtual fact being set to hyperv.

      With the viridan extensions enabled, "virt-what-cpuid-helper" can return "Microsoft Hv" causing the two sections of virt-what to be triggered ... .

      • Detecting Hypervisor as HyperV
      1. Check for Hyper-V.
      2. http://blogs.msdn.com/b/sqlosteam/archive/2010/10/30/is-this-real-the-metaphysics-of-hardware-virtualization.aspx
        if [ "$cpuid" = "Microsoft Hv" ]; then
        echo hyperv
        fi
      • First If statement is false but ${root}/proc/xen evaluates to true.

      if [ "$cpuid" = "XenVMMXenVMM" ]; then
      echo xen; echo xen-hvm
      skip_qemu_kvm=true
      elif [ -d "${root}/proc/xen" ]; then
      echo xen
      if grep -q "control_d" "${root}/proc/xen/capabilities" 2>/dev/null; then
      echo xen-dom0
      else
      echo xen-domU
      fi

      facter 2.4.4 virtual fact set to xen-domU
      facter 3.1.8 virtual fact set to hyperv
      facter 3.3.0 virtual fact set to hyperv

      Redhat bug 671510 - https://bugzilla.redhat.com/show_bug.cgi?id=671510 describes this behavior and potential changes to virt-what output

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              gary.walker Gary Walker
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support