Hi,
I'm not sure, but might this even be an security issue?
at least you could get an idea of the underlying infrastructure.
I'll dig into which infos are furthermore provided
when I get some time..
Am 10.01.2014 11:18, schrieb Dan Kenigsberg:
On Fri, Jan 10, 2014 at 09:12:39AM +0000, Sven Kieske wrote:
> Hi,
>
> yeah of course, there are various scripts for that
> i. e.
http://www.dmo.ca/blog/detecting-virtualization-on-linux/
>
> (google is your friend)
>
> the (afaik) fastest way to detect ovirt is:
>
> dmidecode | grep oVirt
>
> but this needs root privileges.
>
> HTH
>
> Am 10.01.2014 07:41, schrieb Koen Vanoppen:
>> Dear all,
>>
>> Because of our puppet integration at work, it would like to know if there
>> is a way in ovirt to know, from WITHIN a virtual machine, the hypervisor on
>> wich the vm is running?
And unfortunately, you can even tell the UUID of the specific host on
top of which the VM was first started via
dmidecode -s system-serial-number
in the guest. This feature is unfortunate, as it cannot really be
trusted (it does not update upon migration), and breaks an important
abstraction.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen