[ Pobierz całość w formacie PDF ]
stopped reporting the device to the engine. But libvirt still held a
reference to the removed device. If the user attempted to create the
device again, the attempt failed because libvirt still holds a reference to
the non-existent device.
Broken networks are now removed from libvirt before new networks are set
up. The re-creation of broken networks no longer causes exceptions.
BZ#925967
Previously, debugging messages displayed on the TUI (textual user
interface) after the hypervisor was registered to the rhevm server.
A patch prevents debugging messages from being displayed on the TUI after
the hypervisor registers to the rhevm server.
BZ#921595
Previously, VDSM assumed that display networks were backed by bridges.
The management network's address was sometimes provided where the display
network's address should have been provided.
A call now replaces the bridge-specific information retrieval with a call
that retrieves the name of the device (which can be a bridge or other
supported network device. Only after the device name has been retrived is
the address of that device retrieved.
The correct display network address is now returned, and display networks
now work on non-virtual machine networks.
BZ#882667
Previously metadata related to the file storage domain was wrongly reported
as missing. This meant that during some race conditions, attaching and
detaching ISO domains and export domains led to those domains being put in
a non-operational state.
VDSM now verifies the existence of file storage domain metadata. ISO
domains and export domains no longer fall into a non-operational state due
to an inability to find file storage domain metadata.
BZ#911799
Previously, the content of the command "tree " did not
match the output of the sosreport "su_vdsm_-s_.bin.sh_-c.usr.bin.tree_-
l_.rhev.data-center" file.
That command now matches the output of that sosreport file.
56
Chapter 7. RHSA-2013:0886 VDSM
BZ#920074
Previously, VDSM filled /var/log/messages with useless warnings (Storage
Domain warnings reporting that namespaces had already been registered were
especially frequent among these). VDSM logs were rotated every hour, which
made it impossible to access logs older than an hour. This made it
impossible to analyze logs more than one hour old.
vdsm-4.10.2-16.0.el6ev.x86_64 does not fill /var/log/messages with "vdsm
Storage.StorageDomain WARNING Resource namespace" messages.
BZ#905930
Previously (in vdsm-4.10.2-4.0.el6ev.x86_64), when the guest agent was
installed on a guest and you had configured authentication against directory
services, using SSO (single sign-on) to log in to a user account through the
User Portal delivered you into a desktop in which the screen was locked.
In vdsm-4.10.2-16.0.el6ev.x86_64, SSO delivers you into a desktop in which
the screen has not been locked.
BZ#91854 1
Previously, the VM Channels Listener thread stalled, which blocked
communication between VDSM and the hosted guest agents.
A patch prevents the VM Channels Listener thread from stalling, removing
the block in communication between VDSM and the hosted guest agents.
BZ#9104 4 5
Previously, live migrating a preallocated file (e.g. NFS) virtual disk to a
different storage domain failed because of a problem in the preparation of
the volumes at the destination.
Now, it is possible to regularly live migrate preallocated file virtual
disks to a other storage domains.
BZ#875775
Previously, the --force option was not turned on in the vgextend command if
the physical volume was in use.
This meant that it was impossible to extend a storage domain if its
associated physical volume was in use.
The --force option has now been turned on in the vgextend command, even
when the physical volume is in use.
It is now possible to extend a storage domain when its associated physical
volume is in use.
BZ#912308
57
Red Hat Enterprise Virtualization 3.2 Technical Notes
BZ#912308
When the vdsm.log file is removed, either manually or by logrotate, the
supervdsm user can create the log file and set its ownership to root:root.
When this happens, the vdsmd service is stopped until the user resets the
vdsm.log ownership to vdsm:kvm, and restarts the service. This update
separates supervdsm log to a supervdsm.log file, so after vdsm.log is
rotated it remains owned by vdsm:kvm.
BZ#920532
Previously, attaching a large number of storage domains could result in
failure; some but not all of the storage domains would attach.
Now, attaching a large number of storage domains works as expected.
BZ#878667
VDSM hooks for hotplugging (and hot unplugging) NICs have been added.
BZ#958119
Previously, ksmState did not change with /sys/kernel/mm/ksm/run changes,
but changed only when a virtual machine was started or stopped. This meant
that the value of ksmState did not accurately reflect its state.
The value of ksmState is now accurate.
BZ#852956
Domain codes and libvirt error codes were mixed by mistake, so restarting
the libvirt daemon caused the libvirt client socket to close on Red Hat
Enterprise Virtualization Manager. In addition, libvirt reported internal
errors if libvirtd is restarted or stopped, for example after a crash. This
update resolves the mixed codes and adds missing error codes. Restarting
libvirtd now correctly restarts VDSM connections.
BZ#907587
Previously, VDSM was unable to provide Red Hat Enterprise Virtualization
Manager with all CPU information for AMD Bulldozer CPU architecture. This
was because the AMD Bulldozer architecture consists of "modules", which are
represented both as separate cores and separate threads. Management
applications must choose between the thread-based approach and the core-
based approach.
Libvirt now provides XML output that contains more information about the
processor topology so that management applications like VDSM are able to
extract the information they require.
BZ#918666
58
Chapter 7. RHSA-2013:0886 VDSM
Previously, when new bonds were added via the setupNetwork method (through
either the GUI or the SDK), the validation of bonding options fails and the
setupNetworks for the bond failed to apply. This was because the procedure
that checked for existing bond device options was performed by determining
whether sysfs exposed the bonds for the requested device.
The bond required for validation is now created before the setupNetwork
method is called. The bonding options check is now performed successfully,
and requests for bonded networks comply with the rest of the network
validation done by setupNetworks. In the case of incorrect bonding options,
meaningful errors are provided to the user.
BZ#919201 [ Pobierz całość w formacie PDF ]
zanotowane.pl doc.pisz.pl pdf.pisz.pl wyciskamy.pev.pl
stopped reporting the device to the engine. But libvirt still held a
reference to the removed device. If the user attempted to create the
device again, the attempt failed because libvirt still holds a reference to
the non-existent device.
Broken networks are now removed from libvirt before new networks are set
up. The re-creation of broken networks no longer causes exceptions.
BZ#925967
Previously, debugging messages displayed on the TUI (textual user
interface) after the hypervisor was registered to the rhevm server.
A patch prevents debugging messages from being displayed on the TUI after
the hypervisor registers to the rhevm server.
BZ#921595
Previously, VDSM assumed that display networks were backed by bridges.
The management network's address was sometimes provided where the display
network's address should have been provided.
A call now replaces the bridge-specific information retrieval with a call
that retrieves the name of the device (which can be a bridge or other
supported network device. Only after the device name has been retrived is
the address of that device retrieved.
The correct display network address is now returned, and display networks
now work on non-virtual machine networks.
BZ#882667
Previously metadata related to the file storage domain was wrongly reported
as missing. This meant that during some race conditions, attaching and
detaching ISO domains and export domains led to those domains being put in
a non-operational state.
VDSM now verifies the existence of file storage domain metadata. ISO
domains and export domains no longer fall into a non-operational state due
to an inability to find file storage domain metadata.
BZ#911799
Previously, the content of the command "tree " did not
match the output of the sosreport "su_vdsm_-s_.bin.sh_-c.usr.bin.tree_-
l_.rhev.data-center" file.
That command now matches the output of that sosreport file.
56
Chapter 7. RHSA-2013:0886 VDSM
BZ#920074
Previously, VDSM filled /var/log/messages with useless warnings (Storage
Domain warnings reporting that namespaces had already been registered were
especially frequent among these). VDSM logs were rotated every hour, which
made it impossible to access logs older than an hour. This made it
impossible to analyze logs more than one hour old.
vdsm-4.10.2-16.0.el6ev.x86_64 does not fill /var/log/messages with "vdsm
Storage.StorageDomain WARNING Resource namespace" messages.
BZ#905930
Previously (in vdsm-4.10.2-4.0.el6ev.x86_64), when the guest agent was
installed on a guest and you had configured authentication against directory
services, using SSO (single sign-on) to log in to a user account through the
User Portal delivered you into a desktop in which the screen was locked.
In vdsm-4.10.2-16.0.el6ev.x86_64, SSO delivers you into a desktop in which
the screen has not been locked.
BZ#91854 1
Previously, the VM Channels Listener thread stalled, which blocked
communication between VDSM and the hosted guest agents.
A patch prevents the VM Channels Listener thread from stalling, removing
the block in communication between VDSM and the hosted guest agents.
BZ#9104 4 5
Previously, live migrating a preallocated file (e.g. NFS) virtual disk to a
different storage domain failed because of a problem in the preparation of
the volumes at the destination.
Now, it is possible to regularly live migrate preallocated file virtual
disks to a other storage domains.
BZ#875775
Previously, the --force option was not turned on in the vgextend command if
the physical volume was in use.
This meant that it was impossible to extend a storage domain if its
associated physical volume was in use.
The --force option has now been turned on in the vgextend command, even
when the physical volume is in use.
It is now possible to extend a storage domain when its associated physical
volume is in use.
BZ#912308
57
Red Hat Enterprise Virtualization 3.2 Technical Notes
BZ#912308
When the vdsm.log file is removed, either manually or by logrotate, the
supervdsm user can create the log file and set its ownership to root:root.
When this happens, the vdsmd service is stopped until the user resets the
vdsm.log ownership to vdsm:kvm, and restarts the service. This update
separates supervdsm log to a supervdsm.log file, so after vdsm.log is
rotated it remains owned by vdsm:kvm.
BZ#920532
Previously, attaching a large number of storage domains could result in
failure; some but not all of the storage domains would attach.
Now, attaching a large number of storage domains works as expected.
BZ#878667
VDSM hooks for hotplugging (and hot unplugging) NICs have been added.
BZ#958119
Previously, ksmState did not change with /sys/kernel/mm/ksm/run changes,
but changed only when a virtual machine was started or stopped. This meant
that the value of ksmState did not accurately reflect its state.
The value of ksmState is now accurate.
BZ#852956
Domain codes and libvirt error codes were mixed by mistake, so restarting
the libvirt daemon caused the libvirt client socket to close on Red Hat
Enterprise Virtualization Manager. In addition, libvirt reported internal
errors if libvirtd is restarted or stopped, for example after a crash. This
update resolves the mixed codes and adds missing error codes. Restarting
libvirtd now correctly restarts VDSM connections.
BZ#907587
Previously, VDSM was unable to provide Red Hat Enterprise Virtualization
Manager with all CPU information for AMD Bulldozer CPU architecture. This
was because the AMD Bulldozer architecture consists of "modules", which are
represented both as separate cores and separate threads. Management
applications must choose between the thread-based approach and the core-
based approach.
Libvirt now provides XML output that contains more information about the
processor topology so that management applications like VDSM are able to
extract the information they require.
BZ#918666
58
Chapter 7. RHSA-2013:0886 VDSM
Previously, when new bonds were added via the setupNetwork method (through
either the GUI or the SDK), the validation of bonding options fails and the
setupNetworks for the bond failed to apply. This was because the procedure
that checked for existing bond device options was performed by determining
whether sysfs exposed the bonds for the requested device.
The bond required for validation is now created before the setupNetwork
method is called. The bonding options check is now performed successfully,
and requests for bonded networks comply with the rest of the network
validation done by setupNetworks. In the case of incorrect bonding options,
meaningful errors are provided to the user.
BZ#919201 [ Pobierz całość w formacie PDF ]