One method that's pretty solid for QEMU (save folks who pass in custom DMI table values to qemu) is the BIOS data available via dmidecode (or /sysfs/dmi); would need to look at Power and arm for equivalent (likely some device tree bits in /sysfs). Openstack exports a BIOS manufacture of Openstack, the default QEMU bios exposes QEMU and SeaBIOS. These would be good indicators for the the majority of default installs. Obviously it can be worked around since the invoker can specify whole DMI table values (or pass a complete dmi table blob from the host into the guest) but we don't have to be foolproof.
On Fri, Jan 23, 2015 at 5:21 PM, Serge Hallyn <1414...@bugs.launchpad.net> wrote: > So did we come up with a good way to detect not being on bare metal? > > In fact ksm gets enabled by /etc/init/qemu-kvm which is only installed > on a subset of architectures so using virt-what may be a possibliity, > however I'd still prefer not to add virt-what as a dependency if we can > come up with a better way. > > > ** Changed in: qemu (Ubuntu) > Status: New => Triaged > > ** Changed in: qemu (Ubuntu) > Importance: Undecided => High > > -- > You received this bug notification because you are subscribed to qemu in > Ubuntu. > https://bugs.launchpad.net/bugs/1414153 > > Title: > qemu should not enable KSM on nested guests > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1414153/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1414153 Title: qemu should not enable KSM on nested guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1414153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
