An updated virt-who package that fixes several bugs is now available for Red HatEnterprise Linux 6.

The virt-who package provides an agent that collects information about virtualguests present in the system and reports them to the subscription manager.This update fixes the following bugs:* Previously, the virt-who agent was too slow when reading the associationbetween hosts and guests from VMWare ESX systems. As a consequence, whencommunicating with large ESX (or vCenter) deployments, it took a lot of time tosend updates about virtual guests to the Subscription Asset Manager (SAM) andRed Hat Satellite. With this update, virt-who uses an improved method to obtainhost-guest association, which accelerates the aforementioned process.(BZ#1197596)* Prior to this update, the virt-who agent was not able to decrypt a passwordthat was encrypted by the virt-who-password utility. As a consequence, virt-whocould not authenticate against the remote virtualization server. With thisupdate, virt-who is able to decrypt the encrypted password correctly, and thusconnects to the virtualization server properly. (BZ#1197597)* Prior to this update, the virt-who agent ignored the HTTP proxy configurationin the ESX virtualization back end. As a consequence, virt-who did not use theproxy server when connecting to the ESX server, and the connection could fail.With this update, virt-who uses the http_proxy environment variable in ESX mode,thus fixing this bug. (BZ#1201157)* Previously, virt-who used the value of the “–esx-server” command-line optioninstead of the “–satellite-server” option value. As a consequence, virt-whoattempted to report a host-guest association to the ESX server instead ofsatellite, and thus failed. With this update, “–satellite-server” works asintended, and virt-who uses the correct server when connecting to Red HatSatellite. (BZ#1205520) Users of virt-who are advised to upgrade to this updated package, which fixesthese bugs.
Before applying this update, make sure all previously released erratarelevant to your system have been applied.For details on how to apply this update, refer to:https://access.redhat.com/articles/11258Red Hat Enterprise Linux Desktop (v. 6)

SRPMS:
virt-who-0.10-8.el6_6.3.src.rpm
    MD5: c13594cd0ce03b208fadec6164788d14SHA-256: 5365887cfc60035fd9b7642d6f57651c53d966aa2dda9cc7c4f16cc16a913f67
 
IA-32:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
x86_64:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
Red Hat Enterprise Linux HPC Node (v. 6)

SRPMS:
virt-who-0.10-8.el6_6.3.src.rpm
    MD5: c13594cd0ce03b208fadec6164788d14SHA-256: 5365887cfc60035fd9b7642d6f57651c53d966aa2dda9cc7c4f16cc16a913f67
 
x86_64:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
Red Hat Enterprise Linux Server (v. 6)

SRPMS:
virt-who-0.10-8.el6_6.3.src.rpm
    MD5: c13594cd0ce03b208fadec6164788d14SHA-256: 5365887cfc60035fd9b7642d6f57651c53d966aa2dda9cc7c4f16cc16a913f67
 
IA-32:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
PPC:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
s390x:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
x86_64:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
Red Hat Enterprise Linux Server EUS (v. 6.6.z)

SRPMS:
virt-who-0.10-8.el6_6.3.src.rpm
    MD5: c13594cd0ce03b208fadec6164788d14SHA-256: 5365887cfc60035fd9b7642d6f57651c53d966aa2dda9cc7c4f16cc16a913f67
 
IA-32:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
PPC:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
s390x:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
x86_64:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
Red Hat Enterprise Linux Workstation (v. 6)

SRPMS:
virt-who-0.10-8.el6_6.3.src.rpm
    MD5: c13594cd0ce03b208fadec6164788d14SHA-256: 5365887cfc60035fd9b7642d6f57651c53d966aa2dda9cc7c4f16cc16a913f67
 
IA-32:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
x86_64:
virt-who-0.10-8.el6_6.3.noarch.rpm
    MD5: b88658def1f3d220fff1698679b97512SHA-256: 2c9ef98fdbc2080edc3aae5a68dca9a4a033f6d8eab79f8eb9af6ec14bf7980f
 
(The unlinked packages above are only available from the Red Hat Network)
1197596 – virt-who performance issue for large ESX installation1205520 – virt-who uses wrong server when connecting to satellite

These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from:

Leave a Reply