Updated vdsm packages that fix a bug are now available.

VDSM is a management module that serves as a Red Hat Enterprise VirtualizationManager agent on Red Hat Enterprise Virtualization Hypervisor or Red HatEnterprise Linux hosts. All users managing Red Hat Enterprise Linux Virtualization hosts using Red HatEnterprise Virtualization Manager are advised to install these updated packages,which fixes these issues.Changes to the vdsm component:* Previously, migration start time was captured at the start of theMigrationSourceThread process. This meant that the migration would fail if thevirtual machine had to wait a long time to acquire the migration semaphore. Now,the migration start time is captured when migration begins. (BZ#1097341)* Previously, VDSM would not start correctly under certain conditions afterrebooting a hypervisor. This was caused by qemu-sanlock.conf not being persistedafter rebooting the hypervisor when the command ‘vdsm-tool configure –force’was run and libvirt sanlock was enabled. Now, qemu-sanlock.conf is persistedeven after rebooting hypervisors, making it possible for VDSM to startcorrectly. (BZ#1095303)* * Red Hat Enterprise Virtualization Hypervisor 6.5 added support formemory-based file systems (for the purposes of testing), which included codewith O(N^2) complexity. This introduced performance issues, such as high cpuconsumption by vdsm, in certain environments that utilized numerous storagedomains. Now, the additional support for memory-based file systems has beendisabled and does not contribute to performance problems. (BZ#1095907)* Previously, VDSM would report that virtual machines experiencing any I/O errorwere in a paused state. This was caused by the logic used by VDSM to check I/Oerrors received from libvirt. Now, the logic used to check such errors has beenrevised so that VDSM detects the nature of the error, allowing I/O errors to becorrectly reported and handled. (BZ#1090079)* Previously, migration of virtual machines between hypervisors would fail undercertain conditions, causing the virtual machine being migrated to crash. Thiswas caused by the logic used to clean up sockets for virtual machines after VDSMrestarted due to an unexpected failure. Now, the logic used to clean up socketsfor virtual machines has been revised so that VDSM correctly cleans up socketsafter VDSM is restarted, allowing virtual machines to migrate without issue.(BZ#1088906)* Previously, the getStorageDomainInfo action of the vdsClient command wouldfail when run under certain conditions. Now, the logic used to retrieveinformation on storage domains using the vdsClient command has been revised sothat the action returns information correctly. (BZ#1084970)* Previously, the vmHotplugDisk action would fail with the error “VolumeError:Bad volume specification”. This was caused by a multipath race condition thatwould result in a situation in which multipath was not given enough time tocreate the /dev/mapper entry for the LUN on the host on which the virtualmachine was running. Now, the logic used to scan for device visibility has beenrevised so that multipath has the time required for creating the /dev/mapperentry for the LUN on the host on which the virtual machine is running.(BZ#1066413)* Previously, VDSM would report that a storage domain was active even although alink for that storage domain was not present in the /rhev/data-center/SPUUIDdirectory. This would occur when the host was in a non-operational state and wasable to connect to the storage pool but was not able to connect to any storagedomains. Now, the logic for refreshing storage domain links has been revised sothat those links will be created correctly for storage domains even under thesecircumstances. (BZ#1066409)
Before applying this update, make sure all previously-released erratarelevant to your system have been applied.This update is available via the Red Hat Network. Details on how touse the Red Hat Network to apply this update are available athttps://access.redhat.com/site/articles/11258Red Hat Enterprise Virtualization 3

SRPMS:
vdsm-4.13.2-0.17.el6ev.src.rpm
    MD5: 7016b944173ae0ff4b1cb7a0b425664fSHA-256: b08d203e98f5a1814023a682a65b9a6f90f9c70fe28b61d6c77a8eb22aa4341f
 
x86_64:
vdsm-4.13.2-0.17.el6ev.x86_64.rpm
    MD5: 870299ddb14179cef26a3db60b067ebfSHA-256: 068e3422b3f91af3d050cb5cdf6cb14ec51b440ba5391ad7a091c1c1aa548a2a
vdsm-cli-4.13.2-0.17.el6ev.noarch.rpm
    MD5: 15de8fda60b238be98bc1d5446c4c083SHA-256: 9d4f430e3cb8814a7076d9ff3a2b2c64d7f16dcb3dc230a6e5d034c8cf9c2bf5
vdsm-debuginfo-4.13.2-0.17.el6ev.x86_64.rpm
    MD5: b014834c9047c66e676f83a35dbee450SHA-256: 9412e0848b76219afa2dbec25427d906369306539891244116f784b5aa06826a
vdsm-hook-vhostmd-4.13.2-0.17.el6ev.noarch.rpm
    MD5: 170892f49b76f36cc4249259720dd8a8SHA-256: bfb5f50948f7b9a267463c4f4d08ca62bb663b04073d9afbbac3302c0dbfc1ce
vdsm-python-4.13.2-0.17.el6ev.x86_64.rpm
    MD5: 805a57c47deef7e17086d66a6c686905SHA-256: a0719c80a966d692678d9db7d89b7f6bc39750d9a6411b15c3125fe72256e0b8
vdsm-reg-4.13.2-0.17.el6ev.noarch.rpm
    MD5: 2a1e7f5b8576acda47ab861757e19451SHA-256: 06cc4280f4a0ffcab9c6cb9f34ca0ebaa9e305e1632fff2935a1c049bb53b1c6
vdsm-xmlrpc-4.13.2-0.17.el6ev.noarch.rpm
    MD5: 4bde616cf687eecfbe1081bbd914bd61SHA-256: 1447341225d865059d65445574e4472199d438921e6f0c91e4ea47128eb98df5
 
Red Hat Enterprise Virtualization 3.3

SRPMS:
vdsm-4.13.2-0.17.el6ev.src.rpm
    MD5: 7016b944173ae0ff4b1cb7a0b425664fSHA-256: b08d203e98f5a1814023a682a65b9a6f90f9c70fe28b61d6c77a8eb22aa4341f
 
x86_64:
vdsm-bootstrap-4.13.2-0.17.el6ev.noarch.rpm
    MD5: 30a849757ff43230ccf6b6b351e7d58eSHA-256: a241a86085dcfe1873de6c85ed38cdefe24f06d061a2dac8917f8607c0623324
 
(The unlinked packages above are only available from the Red Hat Network)
1066409 – [vdsm] storage domain is reported as ‘active’ by host, even though its link under /rhev/data-center/SPUUID/ is missing1066413 – vmHotplugDisk failed with “VolumeError: Bad volume specification”1084946 – vdsm libvirt and sanlock daemons need to be restarted after upgrading to sanlock 2.81084970 – [vdsm] getStorageDomainInfo fails due to key ‘info’ missing from poolInfo for master domain1088906 – VM migration back to original host fail on “file exists”1090079 – vdsm reports guest as paused on any IO error, even if libvirt/qemu policy is set to “report”1095303 – /etc/libvirt/qemu-sanlock is not persisted and vdsm fails to start on reboot1095907 – VDSM is consuming a lot of cpu time even with no active VMs1097341 – The start time for ‘migration_max_time_per_gib_mem’ appears to be calculated too early.

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