Improve VM detection when running inside recent versions of VirtualBox
authorMichael Prokop <mika@grml.org>
Fri, 11 May 2018 07:07:48 +0000 (09:07 +0200)
committerMichael Prokop <mika@grml.org>
Fri, 11 May 2018 07:12:22 +0000 (09:12 +0200)
commit5b6b38a1878586cbd91c514c037f4f84bb60fbfc
tree3e7420869d561b9bbfff66bbba36881d842e3ce7
parent27c1e0a3df6f670d6c364ff950a23960ae075ae7
Improve VM detection when running inside recent versions of VirtualBox

When running e.g. inside VirtualBox 5.2.6 + 5.2.10 on Windows
virt-what and imvirt report different results than expected, as in:

| # virt-what
| virtualbox
| kvm
|
| # imvirt
| KVM

Explicitely check for VMware, KVM + VirtualBox and don't stop
at first hit. Check for expected VM technology within its output
instead of relying on a single string comparison.

Thanks: Martin Besser for the bugreport and providing the relevant output
autoconfig.functions