Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
virt-what doesn't display xen-domU for a RHEL6.8 paravirtualized guest domain on RHEL5.11 Xen host.
Version-Release number of selected component (if applicable):
Host RHEL5.11 with latest xen and kernel xen:
kernel-xen-2.6.18-408.el5
xen-3.0.3-147.el5_11
Guest RHEL6.8 with:
kernel-2.6.32-642.el6.x86_64
virt-what-1.11-1.2.el6.x86_64
How reproducible: Always
Steps to Reproduce:
1. Create a RHEL6.8 paravirtualized guest domain on RHEL5.11 Xen host.
2. Login to the guest system and run command "virt-what".
Actual results:
The result of virt-what is:
[root@dhcp-66-145-125 ~]# /usr/sbin/virt-what
xen
The other information of the guest "xen-domU" is missing.
Expected results:
The result should include the "xen-domU" information as in the man page.
[root@dhcp-66-145-125 ~]# /usr/sbin/virt-what
xen
xen-domU
Additional info:
1. The latest source code of virt-what (virt-what-1.15) has modified this issue in xen part of file virt-what.in, using this code the virt-what works as expected.
# Check for Xen.
if [ "$cpuid" = "XenVMMXenVMM" ]; then
echo xen; echo xen-hvm
skip_qemu_kvm=true
elif [ -d "${root}/proc/xen" ]; then
echo xen-hypervisor
if grep -q "control_d" "${root}/proc/xen/capabilities" 2>/dev/null; then
echo xen-dom0; echo print-dom0
else
echo xen-domU; echo print-domU
fi
skip_qemu_kvm=true
skip_lkvm=true
...
2. There is once a bug on RHEL6.1 https://bugzilla.redhat.com/show_bug.cgi?id=671126 which is fixed on virt-what-1.3-4.4.el6, but the directory structure of xen pv guest changed, so I suggest to change this part of code accordingly to get the exactly guest information.
Comment 2Richard W.M. Jones
2016-06-15 14:33:48 UTC
Possibly we should just rebase virt-what in RHEL 6 to fix this.
Anyway, I am going to dev-ack this, but based on the history of
never being able to get virt-what into the RHEL ACL, I wouldn't
hold your breath on this bug being fixed any time soon.
Packager version:
virt-what-1.11-1.3.el6.ppc64
Steps to Reproduce:
1. Create a RHEL6.8 paravirtualized guest domain on RHEL5.11 Xen host.
2. Login to the guest system and run command "virt-what".
Result:
[root@dhcp-66-145-125 ~]# virt-what
xen
xen-domU
So verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0748.html
Description of problem: virt-what doesn't display xen-domU for a RHEL6.8 paravirtualized guest domain on RHEL5.11 Xen host. Version-Release number of selected component (if applicable): Host RHEL5.11 with latest xen and kernel xen: kernel-xen-2.6.18-408.el5 xen-3.0.3-147.el5_11 Guest RHEL6.8 with: kernel-2.6.32-642.el6.x86_64 virt-what-1.11-1.2.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a RHEL6.8 paravirtualized guest domain on RHEL5.11 Xen host. 2. Login to the guest system and run command "virt-what". Actual results: The result of virt-what is: [root@dhcp-66-145-125 ~]# /usr/sbin/virt-what xen The other information of the guest "xen-domU" is missing. Expected results: The result should include the "xen-domU" information as in the man page. [root@dhcp-66-145-125 ~]# /usr/sbin/virt-what xen xen-domU Additional info: 1. The latest source code of virt-what (virt-what-1.15) has modified this issue in xen part of file virt-what.in, using this code the virt-what works as expected. # Check for Xen. if [ "$cpuid" = "XenVMMXenVMM" ]; then echo xen; echo xen-hvm skip_qemu_kvm=true elif [ -d "${root}/proc/xen" ]; then echo xen-hypervisor if grep -q "control_d" "${root}/proc/xen/capabilities" 2>/dev/null; then echo xen-dom0; echo print-dom0 else echo xen-domU; echo print-domU fi skip_qemu_kvm=true skip_lkvm=true ... 2. There is once a bug on RHEL6.1 https://bugzilla.redhat.com/show_bug.cgi?id=671126 which is fixed on virt-what-1.3-4.4.el6, but the directory structure of xen pv guest changed, so I suggest to change this part of code accordingly to get the exactly guest information.