Bug 1249440
| Summary: | systemd-detect-virt does not identify rhev/ovirt | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ryan Barry <rbarry> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-daemons |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | jsynacek, lnykryn, msekleta, systemd-maint-list |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-11 07:53:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ryan Barry
2015-08-03 01:52:11 UTC
RHEV/ovirt is just a name of a product, underlying virtualization technology is KVM. 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 (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? |