Bug 767468 - RFE: Higher granularity of hypervisor
Summary: RFE: Higher granularity of hypervisor
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: inventory
Version: 0.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard: Inventory
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-14 06:36 UTC by Marian Ganisin
Modified: 2018-02-06 00:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-22 05:02:42 UTC


Attachments (Terms of Use)

Description Marian Ganisin 2011-12-14 06:36:16 UTC
Description of problem:

For testing purposes we have to be able to request some particular version of hypervisor for reserved virtual machine. For example tests have to be executed on RHEL5 kvm, RHEL6 kvm or on ESX 4.1 and ESX 5.0.

However it doesn't seem to be possible at the moment.

Comment 1 Dan Callaghan 2012-02-27 01:21:49 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.

Comment 2 Bill Peck 2012-03-02 21:14:29 UTC
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.

Comment 4 Nick Coghlan 2014-08-22 05:02:42 UTC
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


Note You need to log in before you can comment on or make changes to this bug.