How to Apply Citrix XenServer Hotfixes without causing Virtual Machine to Corrupt on Apache CloudStack
Summary
This article describes how to apply Citrix XenServer hotfixes without causing the virtual machine to corrupt on the Apache CloudStack.
Public Hotfixes
For all public hotfixes, see http://support.citrix.com/product/xens/v5.6sp2/hotfix/general/public/.
Note: Avoid installing superseded hotfixes.
CTX128416 - Hotfix XS56EFP1003 - For XenServer 5.6 Feature Pack 1
CTX129267 - Hotfix XS56EFP1006 - For XenServer Feature Pack 1
CTX129479 - Hotfix XS56EFP1007 - For XenServer 5.6 Feature Pack 1
CTX130293 - Hotfix XS56EFP1008 - For XenServer 5.6 Feature Pack 1
Note: Verify if driver update is required.
Recommendations
- Disable C-States - For more information, see CTX127395 - Hosts Become Unresponsive with XenServer 5.6 on Nehalem and Westmere CPUs.
- Increase dom0 memory, if required - For more information, see CTX126531 - How to Configure dom0 Memory in XenServer 5.6 or Later.
- Highly recommended - Upgrade to XenServer 5.6 SP2 (To download the service pack, you must login to My Account onhttp://www.citrix.com/).
Procedure
CloudStack earlier than 2.2.14
Complete one of the following solutions to apply the hotfix:
Solution-1: CloudStack distributes virtual machines across the hosts automatically
To apply Citrix XenServer hotfix:
- Shut down all VMs without XenServer Tools (except system VMs like a virtual machine router).
- Using the CloudStack user interface, move the host to Maintenance Mode.
Note: This step must evacuate all VMs from the host and ensure that VMs do not start on the host. - Restart the VMs without XenServer Tools installed at this point. The VMs will start on a different host.
- Update the host with latest XenServer hotfixes:
http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Update the host with latest XenServer drivers:
http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Restart the host.
- Using the CloudStack user interface:
- Move the host out of maintenance mode.
- Migrate any VMs back to the host.
The hotfix will be successfully installed.
Solution-2: Administrator selects the location to migrate the non-system VMs
To apply Citrix XenServer hotfix:
- In the CloudStack database, set allocation_state to Disabled on the host to prevent new VMs from starting on that host.
- Migrate all the non-system VMs from the host.
Note: VMs with XenTools must migrate without any errors. - Shut down all VMs without XenServer Tools except system VMs like a virtual machine router.
- Using the CloudStack user interface, move the host to Maintenance Mode.
Note: This step must evacuate the system VMs from the host and ensure that VMs do not start on the host. - Restart the VMs without installing the XenServer Tools. However, the VMs will start on a different host.
- Update the host with latest XenServer hotfixes:
http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Update the host with latest XenServer drivers:
\http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Restart the host.
- Set the allocation_state to Enabled mode on the host (in CloudStack database).
- Using the CloudStack user interface:
- Move the host out of Maintenance Mode.
- Migrate any VMs back to the host.
The hotfix will be successfully installed.
Complete one of the following solutions to apply the hotfix:
Solution-1: CloudStack automatically distributes the VMs across the hosts
- Shut down all VMs without XenServer Tools (except system VMs like a virtual machine router).
- Using the CloudStack user interface, move the host to Maintenance Mode.
Note: This step should evacuate all VMs from the host and ensure that VMs do not start on the host. - Restart the VMs without XenServer Tools installed at this point. VMs will start on a different host.
- Update the host with latest XenServer hotfixes:
http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Update the host with latest XenServer drivers:
http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Restart the host.
- Using the CloudStack user interface:
- Move the host out of Maintenance Mode.
- Migrate any VMs back to the host.
The hotfix will be successfully installed.
Solution-2: Administrator selects the location to migrate non-system VMs
To apply Citrix XenServer hotfix:
- In the CloudStack database, set allocation_state to Disabled on the host to prevent new VMs from starting on that host.
- Migrate all non-system VMs from the host (VMs with XenTools should migrate without any problems).
- Shut down all VMs without XenServer Tools (except system VMs like a virtual machine router).
- Move the host to Maintenance Mode using the CloudStack user interface.
Note: This step must evacuate the system VMs from the host and ensure that VMs do not start on the host. - Restart VMs without XenServer Tools installed at this point. VMs will start on a different host.
- Update the host with latest XenServer hotfixes:
http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Update the host with latest XenServer drivers:
http://support.citrix.com/product/xens/v5.6fp1/hotfix/general/public/ - Restart the host.
- Set allocation_state back to Enabled on the host (in the CloudStack database).
- Using the CloudStack user interface:
- Move the host out of Maintenance Mode.
- Migrate any VMs back to the host.
The hotfix will be successfully installed.
More Information
CTX133465 - Possible Virtual Machine Corruption if XenServer Hotfix is not Applied
CTX133467 - Virtual Machine Corruption on CloudStack without XenServer Hotfixes Installed - Highly Recommended Hotfixes for XenServer 5.6 Service Pack 2
No comments:
Post a Comment