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:
You can use the python script lsvmbus in /usr/sbin to get information about devices on the Hyper-V virtual machine bus (VMBus) similiar to information commands like lspci.
The tool is now present in the tools\hv folder in upstream kernel.
Please take the necessary steps to include lsvmbus in 7.3 or post release.
Version-Release number of selected component (if applicable):
7.3 and future releases
Windows platforms: all / independent
Hi Vitally,
When check latest hyperv-daemons-0-0.30.20161211git.el7.x86_64.rpm, looks that it does not have dependency on hyperv-tools-0-0.30.20161211git.el7.noarch.rpm, could you please help to confirm whether this is by purpose?
[root@rhel7-3 ~]# rpm -qpR hyperv-daemons-0-0.30.20161211git.el7.x86_64.rpm
hypervkvpd = 0-0.30.20161211git.el7
hypervvssd = 0-0.30.20161211git.el7
hypervfcopyd = 0-0.30.20161211git.el7
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadIsXz) <= 5.2-1
(In reply to xuli from comment #4)
> Hi Vitally,
>
> When check latest hyperv-daemons-0-0.30.20161211git.el7.x86_64.rpm, looks
> that it does not have dependency on
> hyperv-tools-0-0.30.20161211git.el7.noarch.rpm, could you please help to
> confirm whether this is by purpose?
If we add the dependency there it'll become mandatory for everyone who already has hyperv-daemons installed and it looks like an overkill: hyperv-tools package is not really required for hyperv-daemons, one can easily live without it. Please let me know what you think, I can add the dependency if you think it's worth it.
Hi Chris,
Yes, it is already picked up in 7.4.
Need to install hyperv-tools separately, and it's repo located at /compose/Server-optional/x86_64/os/.
[root@dhcp-10-77 ~]# rpm -qa | grep -i hyperv
hypervvssd-0-0.30.20161211git.el7.x86_64
hypervkvpd-0-0.30.20161211git.el7.x86_64
hyperv-daemons-0-0.30.20161211git.el7.x86_64
hyperv-daemons-license-0-0.30.20161211git.el7.noarch
hypervfcopyd-0-0.30.20161211git.el7.x86_64
hyperv-tools-0-0.30.20161211git.el7.noarch
Verify pass on 7.4 Beta release, so close this bug.
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://access.redhat.com/errata/RHBA-2017:1882