RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1249440 - systemd-detect-virt does not identify rhev/ovirt
Summary: systemd-detect-virt does not identify rhev/ovirt
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-03 01:52 UTC by Ryan Barry
Modified: 2016-11-11 07:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-11 07:53:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ryan Barry 2015-08-03 01:52:11 UTC 
Description of problem:
systemd-detect-virt reports ovirt/rhev guests as "kvm" instead of 'ovirt' or 'rhev'

Version-Release number of selected component (if applicable):
systemd-208-20.el7_1.5.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Run systemd-detect-virt in a rhev/ovirt guest
2.
3.

Actual results:
kvm

Expected results:
ovirt (or rhev, as appropriate)

Additional info:
This can be checked in dmidecode:
Manufacturer: oVirt
Product Name: oVirt Node

Product Name: RHEV Hypervisor

(it's also oVirt Node/RHEV Hypervisor for the guests)
Comment 2 Lukáš Nykrýn 2015-08-03 11:31:16 UTC 
RHEV/ovirt is just a name of a product, underlying virtualization technology is KVM.
Comment 3 Ryan Barry 2015-08-03 14:23:44 UTC 
The idea behind filing this bug is that configuration management systems (including puppet) currently detect whether systems are running on ovirt/rhev, regardless of what the underlying technology is. It allows fingerprinting systems to add them to host groups more easily.

virt-what currently has the same bug, meaning that puppet (as an example) correctly detects ovirt/rhev if facter is run as a non-root user, but detects kvm if virt-what is used. salt already uses systemd-detect-virt where available.

On these platforms, ovirt/rhev guests will not be identified, and this is not a bug in salt or anything else using systemd-detect-virt. 

This detecting (via dmi for a kvm guest) appears to already be done for oracle. Adding ovirt/rhev is very easy, matches the existing pattern, and has advantages for users of systemd-detect-virt
Comment 4 Michal Sekletar 2015-08-03 19:59:42 UTC 
(In reply to Ryan Barry from comment #3)

> This detecting (via dmi for a kvm guest) appears to already be done for
> oracle. Adding ovirt/rhev is very easy, matches the existing pattern, and
> has advantages for users of systemd-detect-virt

It seems to me that comparison with oracle case is only partially applicable to this bug. Oracle Virtualbox is standalone virtualization technology which recently got ability to use KVM instead as a back-end. However ovirt is only management layer. Those two are very different situations, because in former case all units which had ConditionVirtualization=oracle would not start in case you use Virtualbox with KVM.

I think this deserves discussion upstream. Can you please open issue on GitHub about this?
Comment 5 Jan Synacek 2016-11-11 07:53:57 UTC 
No response for over a year. Plus, comment 2.
Note You need to log in before you can comment on or make changes to this bug.