diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml
index a594183bbef..210ecf7e00b 100644
--- a/docs/en-US/Release_Notes.xml
+++ b/docs/en-US/Release_Notes.xml
@@ -144,6 +144,129 @@ under the License.
Upgrade Instructions
This section contains upgrade instructions from prior versions of CloudStack to &PRODUCT; 4.1.1. We include instructions on upgrading to &PRODUCT; from pre-Apache versions of Citrix CloudStack (last version prior to Apache is 3.0.2) and from the releases made while CloudStack was in the Apache Incubator.
If you run into any issues during upgrades, please feel free to ask questions on users@cloudstack.apache.org or dev@cloudstack.apache.org.
+
+ Upgrade from 4.1.0 to 4.1.1
+ This section will guide you from &PRODUCT; 4.1.0 versions to &PRODUCT; 4.1.1.
+ Any steps that are hypervisor-specific will be called out with a note.
+ We recommend reading through this section once or twice before beginning your upgrade procedure, and working through it on a test system before working on a production system.
+
+
+ Most users of &PRODUCT; manage the installation and upgrades of &PRODUCT; with one of Linux's predominant package systems, RPM or APT. This guide assumes you'll be using RPM and Yum (for Red Hat Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+ Create RPM or Debian packages (as appropriate) and a repository from the 4.1.1 source, or check the &PRODUCT; downloads page at http://cloudstack.apache.org/downloads.html for package repositories supplied by community members. You will need them for step or step .
+ Instructions for creating packages from the &PRODUCT; source are in the Installation Guide.
+
+
+ Stop your management server or servers. Run this on all management server hosts:
+ # service cloudstack-management stop
+
+
+ If you are running a usage server or usage servers, stop those as well:
+ # service cloudstack-usage stop
+
+
+ Make a backup of your MySQL database. If you run into any issues or need to roll back the upgrade, this will assist in debugging or restoring your existing environment. You'll be prompted for your password.
+ # mysqldump -u root -p cloud > cloudstack-backup.sql
+
+
+ If you are using Ubuntu, 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 APT repository, substitute your own URL for the ones used in these examples.
+
+
+
+ The first step is to confirm that your sources list is pointed to the correct 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/apt/sources.list.d/cloudstack.list on any systems that have &PRODUCT; packages installed.
+ This file should have one line, which contains:
+ deb http://cloudstack.apt-get.eu/ubuntu precise 4.1
+ If the line above is not correct, correct it. Note that if you're using your own package repository, change this line to read as appropriate for your 4.1.1 repository.
+
+
+ Now update your apt package list:
+ $ sudo apt-get update
+
+
+ Now that you have the repository configured, it's time to update the cloudstack-management package. This will pull in any other dependencies and updates you need.
+ $ sudo apt-get install cloudstack-management
+
+
+ On KVM hosts you will need to also upgrade the cloudstack-agent package:
+ $ sudo apt-get install 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 cloudstack-agent stop
+ killall jsvc
+ service cloudstack-agent start
+
+
+
+
+
+ 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 step is to confirm that your yum configuration is pointed at the correct 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.1/
+ enabled=1
+ gpgcheck=0
+
+ If the file above is not correct, correct it. Note that if you're using your own package repository, change the baseurl line to read as appropriate for your 4.1.1 repository.
+
+
+ Now that you have the repository configured, it's time to update the cloudstack-management package.
+ $ sudo yum update cloudstack-management
+
+
+ For KVM hosts, you will need to update the cloudstack-agent package.
+ $ sudo yum update 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 cloudstack-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 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.
+ # tail -f sysvm.log
+ The output to sysvm.log will look something like this:
+
+ Stopping and starting 1 secondary storage vm(s)...
+ Done stopping and starting secondary storage vm(s)
+ Stopping and starting 1 console proxy vm(s)...
+ Done stopping and starting console proxy vm(s).
+ Stopping and starting 4 running routing vm(s)...
+ Done restarting router(s).
+
+
+
+
Upgrade from 4.0.x to 4.1.1
This section will guide you from &PRODUCT; 4.0.x versions to &PRODUCT; 4.1.1.