Issue #2067 has been updated by intri geri.
This has been fixed for KVM in 1.5.8, thanks to Git commit 62b6773. (Distributors, please note that this patch applies flawlessly on 1.5.7 and works well there too.) Splitting this bug report into more specific ones (Xen, HyperV and kvm) would help tracking this I guess. ---------------------------------------- Bug #2067: Virtual fact does not work for Xen, HyperV, kvm https://projects.puppetlabs.com/issues/2067 Author: Gary Law Status: Accepted Priority: Normal Assignee: Category: library Target version: 1.6.0 Keywords: Virtual VMWare Zones Xen HyperV kvm Branch: Hi The 'virtual' fact seems to report only for vmware. See the following from the mailing list (re Xen): 2009/3/9 Trevor Hemsley <[email protected]> manufacturer => Xen virtual => physical It appears that $virtual doesn't work on Xen :( It appears it doesn' work under Debian/Windows HyperV either:- g...@dv01:~ $ sudo facter virtual physical g...@dv01:~ $ sudo facter -v 1.5.1 g...@dv01:~ $ sudo facter operatingsystem Debian g...@dv01:~ $ It also doesn't seem to recognise a Solaris zone as a virtual, although it's arguable if it is or not:- g...@sv01:~ $ facter -v 1.5.2 g...@sv01:~ $ facter operatingsystem Solaris g...@sv01:~ $ sudo facter virtual g...@sv01:~ $ To detect a non-Global zone on Solaris, run the zonecfg command as root -- it will return exit code 1:- g...@sv01:~ $ zonecfg zonecfg can only be run from the global zone. g...@sv01:~ $ echo $? 1 Not sure how to detect HyperV or Xen. Gary -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
