Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Geoff Nichols assigned an issue to Unassigned Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: Geoff Nichols Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: Geoff Nichols Labels: triaged virtualization windows Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Branan Riley commented on FACT-1813 Re: Windows virtual machines on QEMU/KVM servers not detected as virtual This may be a duplicate of FACT-1806 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Scott McClellan assigned an issue to Casey Williams Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: Scott McClellan Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Scott McClellan updated an issue Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: Scott McClellan Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title John Ruck updated an issue Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: John Ruck I use QEMU to host KVM virtual machines (probably not the best VM solution, but it is one that I figured out and works for me). One thing I have noticed is that Windows guest machines are not identifying themselves as being virtual (is_virtual == false) while Linux guest machines are. For what it is worth I have tried to patch this out myself, but the only source I have been able to identify for the is_virtual logic comes from here (https://github.com/Jimdo/facter/blob/master/lib/facter/virtual.rb)) which seems to no longer be what is used (in looking around in the facter GitHub repository I have not been able to identify the new equivalent code). My "fix" was to add a if result.nil? and computersystem.manufacturer =~ /QEMU/ result = "qemu"endblock near the end of the "virtual" function as this seems to properly identify a QEMU hosted machine on Windows. Running facter on the windows machines doesn't show a "virtual" fact anymore, so I am guessing there is a new scheme in use for the is_virtual processing.My "patch" works fine on the windows machines, but since it uses the virtual fact it also seems to mess up some of the Linux machines on my network now (physical machines are showing as virtual) so I am now at a point of either needing an official patch to resolve this or at least have somebody point me to where the current code is that is doing the is_virtual determinations so that I can see if I can come up with a working patch for the new methodology. If somebody can point me to where the new logic exists I can try to build a proper patch myself, or if this has provided enough information to patch in QEMU detection to the current system that would also be great. 2018-01-31 UpdateOk, I think I have figured out what needs to be changed for the new is_virtual detection system, but as the code is now in compiled c/c++ I cant do patch like I was doing before. Here is the wmic output on a Windows machine the problem is hitting:PS C:\> wmicwmic:root\cli>computersystemAdminPasswordStatus AutomaticManagedPagefile AutomaticResetBootOption AutomaticResetCapability BootOptionOnLimit BootOptionOnWatchDog BootROMSupported BootStatusBootupState CaptionChassisBootupState ChassisSKUNumber CreationClassName CurrentTimeZone DaylightInEffect Description DNSHostName Domain DomainRole EnableDaylightSavingsTime FrontPanelResetStatus HypervisorPresent InfraredSupported InitialLoadInfo InstallDate KeyboardPasswordStatus LastLoadInfo Manufacturer Model Name NameFormat NetworkServerModeEnabled NumberOfLogicalProcessors NumberOfProcessors OEMLogoBitmap OEMStringArray PartOfDomain PauseAfterReset PCSystemType PCSystemTypeEx PowerManagementCapabilities PowerManagementSupported PowerOnPasswordStatus PowerState PowerSupplyState PrimaryOwnerContact PrimaryOwnerNameResetCapability ResetCount ResetLimit Roles Status SupportContactDescription SystemFamily SystemSKUNumber SystemStartupDelay
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title John Ruck updated an issue Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: John Ruck I use QEMU to host KVM virtual machines (probably not the best VM solution, but it is one that I figured out and works for me). One thing I have noticed is that Windows guest machines are not identifying themselves as being virtual (is_virtual == false) while Linux guest machines are. For what it is worth I have tried to patch this out myself, but the only source I have been able to identify for the is_virtual logic comes from here (https://github.com/Jimdo/facter/blob/master/lib/facter/virtual.rb)) which seems to no longer be what is used (in looking around in the facter GitHub repository I have not been able to identify the new equivalent code). My "fix" was to add a if result.nil? and computersystem.manufacturer =~ /QEMU/ result = "qemu"endblock near the end of the "virtual" function as this seems to properly identify a QEMU hosted machine on Windows. Running facter on the windows machines doesn't show a "virtual" fact anymore, so I am guessing there is a new scheme in use for the is_virtual processing.My "patch" works fine on the windows machines, but since it uses the virtual fact it also seems to mess up some of the Linux machines on my network now (physical machines are showing as virtual) so I am not now at a point of either needing an official patch to resolve this or at least have somebody point me to where the current code is that is doing the is_virtual determinations so that I can see if I can come up with a working patch for the new methodology. If somebody can point me to where the new logic exists I can try to build a proper patch myself, or if this has provided enough information to patch in QEMU detection to the current system that would also be great. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title John Ruck created an issue Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Issue Type: Bug Affects Versions: FACT 3.9.3 Assignee: Unassigned Created: 2018/01/29 4:41 AM Environment: Windows 10 Pro VM hosted on a Ubuntu 14.04.5 LTS server via QEMU/KVM Priority: Normal Reporter: John Ruck I use QEMU to host KVM virtual machines (probably not the best VM solution, but it is one that I figured out and works for me). One thing I have noticed is that Windows guest machines are not identifying themselves as being virtual (is_virtual == false) while Linux guest machines are. For what it is worth I have tried to patch this out myself, but the only source I have been able to identify for the is_virtual logic comes from here (https://github.com/Jimdo/facter/blob/master/lib/facter/virtual.rb)) which seems to no longer be what is used (in looking around in the facter GitHub repository I have not been able to identify the new equivalent code). My "fix" was to add a if result.nil? and computersystem.manufacturer =~ /QEMU/ result = "qemu" end block near the end of the "virtual" function as this seems to properly identify a QEMU hosted machine on Windows. Running facter on the windows machines doesn't
