Messages in this thread | | | Date | Tue, 29 Jun 2010 19:41:38 -0400 | Subject | Re: Hypervisor detection from within a Linux VM | From | Chetan Loke <> |
| |
On Tue, Jun 29, 2010 at 5:44 PM, Anthony Liguori <anthony@codemonkey.ws> wrote: > On 06/29/2010 04:25 PM, Chetan Loke wrote: > It can be done entirely in userspace. Take a look at virt-what: > > http://people.redhat.com/~rjones/virt-what/ >
Just posted a patch for virt-what.in which can be used as a wrapper script. I will be using that for now.
>> Question: >> Q1)Is it possible to get this functionality as part of the stock >> kernel or is that a bad idea? I suspect there could be other >> users/apps who would need to know what *nix hypervisor(or a >> non-virtualized environment) they are >> running on? > > It might be reasonable to list the hypervisor signature as a field in > /proc/cpuinfo. There's also a /sys/hypervisor where such information could > go. >
I like the idea of spitting out a signature under /proc/cpuinfo primarily because everyone is familiar with that node.
> Regards, > Anthony Liguori
Regards Chetan Loke -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |