diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml
index f243a26cce2..d51e9fbae25 100644
--- a/docs/en-US/Release_Notes.xml
+++ b/docs/en-US/Release_Notes.xml
@@ -4201,10 +4201,51 @@ under the License.
- The package names have changed between 4.0 and 4.1, so upgrading the packages won't happen automatically with a yum update
+ If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step .
+ Community Packages
+ This section assumes you're using the community supplied packages for &PRODUCT;. If you've created your own packages and yum repository, substitute your own URL for the ones used in these examples.
+
+
+
+ The first order of business will be to change the yum repository for each system with &PRODUCT; packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.)
+ Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have &PRODUCT; packages installed.
+ This file should have content similar to the following:
+
+[apache-cloudstack]
+name=Apache CloudStack
+baseurl=http://cloudstack.apt-get.eu/rhel/4.0/
+enabled=1
+gpgcheck=0
+
+ If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.1/
+ If you're using your own package repository, change this line to read as appropriate for your 4.1.0 repository.
+
+
+ Now that you have the repository configured, it's time to install the cloudstack-management package. This will pull in any other dependencies you need.
+ $ sudo yum install cloudstack-management
+
+
+ For KVM hosts, you will need to upgrade the cloudstack-agent package:
+ $ sudo yum install cloudstack-agent
+ During the installation of cloudstack-agent, the RPM will copy your agent.properties, log4j-cloud.xml, and environment.properties from /etc/cloud/agent to /etc/cloudstack/agent.
+
+
+ Verify that the file /etc/cloudstack/agent/environment.properties has a line that reads:
+ paths.script=/usr/share/cloudstack-common
+ If not, add the line.
+
+
+ Restart the agent:
+
+ service cloud-agent stop
+ killall jsvc
+ service cloudstack-agent start
+
+
+
- Once you've upgraded the packages on your management servers, you'll need to restart the system VMs. Make sure port 8096 is open to do this.
+ Once you've upgraded the packages on your management servers, you'll need to restart the system VMs. Make sure port 8096 is open in your local host firewall to do this.
There is a script that will do this for you, all you need to do is run the script and supply the IP address for your MySQL instance and your MySQL credentials:
# nohup cloudstack-sysvmadm -d IP address -u cloud -p -a > sysvm.log 2>&1 &
You can monitor the log for progress. The process of restarting the system VMs can take an hour or more.