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? Kind regards, Koen
On 10 Jan 2014, at 07:41, Koen Vanoppen wrote:
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?
look at dmidecode output, BIOS Manufacturer should be oVirt Thanks, michal
Kind regards,
Koen _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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?
Kind regards,
Koen
-- 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
On Fri, Jan 10, 2014 at 10:12 AM, 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.
I confirm that on three guest systems: CentOS 5.10, CentOS 6.4 and Fedora 20 all x86_64 I get: $ sudo /usr/sbin/dmidecode | grep -A2 "System Information" System Information Manufacturer: oVirt Product Name: oVirt Node This on oVirt 3.3.2 with Fedora 19 oVirt stable repo. nice to know. Thanks, Gianluca
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.
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
On 10 Jan 2014, at 14:18, Sven Kieske wrote:
Hi,
I'm not sure, but might this even be an security issue?
I don't think it's serious, it can easily be changed via a hook, there's also an RFE somehwere in queue for this to be configurable directly in UI (not much work, 3.5 perhaps) and since inside the guest you are not aware of migrations you can't really "trust" that value anyway
at least you could get an idea of the underlying infrastructure.
well, yes. But in addition in /etc/vdsm/vdsm.id you can define your very own host UUID but by default yes, after enough runs…. Thanks, michal
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 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-----Original message-----
From:Sven Kieske <S.Kieske@mittwald.de> Sent: Friday 10th January 2014 14:21 To: Dan Kenigsberg <danken@redhat.com> Cc: users@ovirt.org Subject: Re: [Users] Hypervisor info
Hi,
I'm not sure, but might this even be an security issue? at least you could get an idea of the underlying infrastructure.
Maybe, but it's already possible to detect nearly every virtualization platform (Hyper-V, VMware, XEN, KVM, VirtualBox...) - see "man virt-what"... Regards, René
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 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Yeah, I know that script, but it's a difference if you can tell the virtualization software or if you get information regarding the infrastructure beneath it. But I agree that the UUID is not that much information. We should just pay attention to not leak more information than necessary. This leads me to the question: Why does the UUID got exposed to the vm in the first place? Am 10.01.2014 15:12, schrieb René Koch:
Maybe, but it's already possible to detect nearly every virtualization platform (Hyper-V, VMware, XEN, KVM, VirtualBox...) - see "man virt-what"...
-- 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
participants (6)
-
Dan Kenigsberg -
Gianluca Cecchi -
Koen Vanoppen -
Michal Skrivanek -
René Koch -
Sven Kieske