| Summary: | RFE: Higher granularity of hypervisor | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Marian Ganisin <mganisin> |
| Component: | inventory | Assignee: | beaker-dev-list |
| Status: | CLOSED CANTFIX | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.7 | CC: | bpeck, mcsontos, rmancy, stl, tools-bugs |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | Inventory | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-22 05:02:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Marian Ganisin
2011-12-14 06:36:16 UTC
Is there any way to distinguish these possibilities on the guest side? The hypervisor field is populated by the inventory scripts, which run on each Beaker system. Right now we figure out the hypervisor by executing the cpuid instruction(!) and examining the result. But that doesn't tell us anything about the hypervisor version or host operating system. The model does show which OS the kvm guest is running on: KVM RHEL 6.0.0 PC We only have rhel6 kvm guests. If you need rhel5 you should open a ticket. Unfortunately, hypervisors simply don't make this kind of information available to guests, so we can't report more exact information from the inventory scan. The man page for virt-what shows the kind of granularity that is feasible: http://people.redhat.com/~rjones/virt-what/virt-what.txt |