Issue #2169 has been updated by Adrian Bridgett.
I think part of the problem is that what you see has changed between different Xen versions. The second part being the only way I could see on _new_ domUs to tell that it was a Xen domain. The 3rd part being a tighter version of the original code which won't set dom0s as domUs. The first part being the old way to detect domUs which I left in as I didn't know if the second part worked on _old_ Xen Domus. ---------------------------------------- Bug #2169: xen domu/dom0 fact broken on new xen kernels http://projects.reductivelabs.com/issues/2169 Author: Adrian Bridgett Status: Re-opened Priority: Normal Assigned to: community - Category: library Target version: unplanned Complexity: Unknown Keywords: (see #1558 too) I'm running 2.6.26 dom0 and domU under Xen. On the host _both_ /proc/sys/xen/independent_wallclock and /proc/xen/capabilities exist, on the guest, neither exist. I can't see anything else under /proc/ on DomU, however /sys/bus/xen exists on both (/sys/bus/xen-backend exists on the dom0 but I believe this could also exist in DomUs providing devices to other domUs). I now use this snippet of code: <pre> # new Xen domains have this in dom0 not domu :( if FileTest.exists?("/proc/sys/xen/independent_wallclock") result = "xenu" end if FileTest.exists?("/sys/bus/xen") result = "xenu" end if FileTest.exists?("/proc/xen/capabilities") txt = File.read("/proc/xen/capabilities") if txt =~ /control_d/i result = "xen0" end end </pre> without this, the dom0 was reported as xenu and the domUs were not reported as being under xen at all -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
