Issue #20759 has been updated by Tony Lapointe.
I am facing the same issue, was about to open up a ticket when i just saw this one. A little note that might help here. On Gentoo, with openrc, the detection of xen0 and xenU is working just fine. They are relying on /proc/xen/capabilities, if the file contain the string "control_d", it is detected as xen0, otherwise, it is detected as xenU. Maybe that the same mechanism could be use by facter. Best regards, Tony Lapointe ---------------------------------------- Bug #20759: Xen virtualization incorrectly detected when DomU has Dom0-capable kernel https://projects.puppetlabs.com/issues/20759#change-98118 * Author: Gabor Garami * Status: Needs More Information * Priority: Normal * Assignee: Gabor Garami * Category: * Target version: * Keywords: * Branch: * Affected Facter version: 1.7.1 ---------------------------------------- The problem: The Xen virtualization detection says dom0 if domU runs a Dom0-capable kernel. The main problem is checking existence of /dev/xen/evtchn is not enough, the correct detection must include checking the content of /sys/hypervisor/uuid, and if it isn't contains all-zero UUID, then the system is really xenU not xen0. -- 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 -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
