Description of problem: we recommend to power cycle all VMs after changing cluster level soon. but we do not have such info in Upgrade Guides[1][2]. Michal Skrivanek noted the power cycle in a thread with following text: ~~~ note that for migration improvements to be effective (4.0 feature) the cluster level would need to be further updated to 4.0 compatibility and migration policy would need to be changed from “Legacy” then. This 4.0 cluster update need to happen only AFTER all the former originally 3.5 VMs are power cycled and running properly as 3.6 VMs! Otherwise the same migration configuration tweaks may need to be applied (I suppose it’s mainly the bandwidth speed, but pending confirmation) ~~~ Version-Release number of selected component (if applicable): 4.0/4.1
Michal, could you prepare a text for this recommendation explaining reasoning for this please?
the text is in bug 1356027 doc text
Assigning to Byron for review.
Implemented review comments and merged.
This content has been published to: 4.1: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/administration_guide/#Changing_the_Cluster_Compatibility_Version https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/upgrade_guide/#Changing_the_Cluster_Compatibility_Version 4.0: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/administration_guide/#Changing_the_Cluster_Compatibility_Version https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/upgrade_guide/#Changing_the_Cluster_Compatibility_Version
Hello, Reopening this one per customer's request because in sentence "This is achieved by restarting the virtual machine" the word 'restart' is oftem read by customers as 'reboot', and those are 2 different things: 'reboot' could be thought of as an event triggered from inside guest OS (hence the same qemu process is still running on hypervisor even though guest OS inside has been reinitialized), and 'restart' is an action initiated from GUI or REST API (and implies shutting down current qemu process and starting new one instead, so that new qemu process could pick up new functionality of the new DC/cluster level). I would suggest to clarify term 'restart' in the above doc, e.g.: "This is achieved by restarting the virtual machine (power-cycle, or cold restart, initiated via Manager UI or REST API call, in contrast to 'warm reboot' initiated from within guest operating system)" Please let me know what you think. Please let me know if you have any further questions or concerns. -- Kind Regards, Igor Netkachev Technical Support Engineer Red Hat Global Support Services
Updated as per suggestion. Published to: 4.1: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/administration_guide/#Changing_the_Cluster_Compatibility_Version https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/upgrade_guide/#Changing_the_Cluster_Compatibility_Version 4.0: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/administration_guide/#Changing_the_Cluster_Compatibility_Version https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/upgrade_guide/#Changing_the_Cluster_Compatibility_Version