In Xen domU, "facter virtual" prints "physical"

Bug #980291 reported by Sergio Gelato
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
facter (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I've installed precise in virtual machines running on top of the Xen 4.0 hypervisor (with a Debian squeeze dom0).
In both i386 machines (running 3.2.0-23-generic-pae #36-Ubuntu) and amd64 machines (with 3.2.0-23-generic #36-Ubuntu), "facter is_virtual" prints out "false" and "facter virtual" prints out "physical".

The desired answers are "true" and "xenu", respectively.

This is related to upstream issue #2747 but I'm not aware of upstream having found a definitive solution to this problem. I have tested a patch, based on an analysis of the systems I run, and it does the job for me but of course I cannot vouch for its universality. I will be attaching my patch to this bug report.

Tags: patch precise
Revision history for this message
Sergio Gelato (sergio-gelato) wrote :
tags: added: precise
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "xen-detection-fix" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
James Page (james-page) wrote :

Also reported upstream - see http://projects.puppetlabs.com/issues/10625

Changed in facter (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package facter - 1.6.9-2ubuntu1

---------------
facter (1.6.9-2ubuntu1) quantal; urgency=low

  * Merge from Debian unstable (LP: #1007560). Remaining changes:
    - debian/rules:
      + use what we had in natty; we don't want ruby-pkg-tools
         in main. (LP: #408402)
      + Use dh_prep instead of dh_clean, add build-arch + build-indep targets
    - debian/control:
      + Continue using ruby + libopenssl-ruby as Build-Depends even tho Debian
        has moved to gem2deb (not in main). Move ruby-json to Suggests.
      + Make binary package depend on ruby1.8 explicitly
  * debian/patches/ubuntu_xen_print_virtual.patch: correctly detect
    xen0,xenu. (LP: #980291)

facter (1.6.9-2) unstable; urgency=medium

  * Add patch from upstream (b050eb1) to ignore LSB noise

facter (1.6.9-1) unstable; urgency=low

  * New upstream release

facter (1.6.8-1) unstable; urgency=low

  * Imported Upstream version 1.6.8

facter (1.6.7-1) unstable; urgency=low

  * Imported Upstream version 1.6.7
  * Bump standards version (no changes)

facter (1.6.6-1) unstable; urgency=low

  * New upstream release
 -- Andres Rodriguez <email address hidden> Fri, 01 Jun 2012 14:51:28 -0400

Changed in facter (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.