On Wed, 10 Jun 2009 09:32:24 -0400, Paul Nasrat wrote: > 2009/6/10 Thomas Mueller <[email protected]>: >> >> A kvm virtualized guest has devices with Qumranet as manufacturer. >> >> Gotchas: kvm is/uses a "fork" of qemu. i saw a patch that detects the >> processor name and then sets "qemu". this needs to be done before so >> that this patch overwrites the result. > > I'm in the middle of cleaning up virtual.rb and adding tests for 2292, > so I'll add this functionality as well.
also on plain qemu the devices seem to be Qumranet. :/ but i found this while searching the maillinglist archives: "The preferred way of doing this is checking CPUID leaf 0x4000 0000 for the signature "KVMKVMKVM". Most hypervisors (KVM, Xen, VMware, and Hyper- V) are adopting this as the preferred detection mechanism." (http:// article.gmane.org/gmane.comp.emulators.kvm.devel/20539) this seems to be the only way to distinguish qemu and kvm, but maybe a generic way to distinguish all the full-virtualizer? don't know how to access this "leaf 0x4000 0000". - Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
