I tried XCP-ng in a lab today. The lab ran XenServer 7.6 from my previous experiments. I started long ago with XS 7.2 and 5 hosts in a single pool. The upgrade to XCP-ng 7.6 went smoothly. Continue reading Adventures in XCP-ng 7.6
It’s winter break, giving me time to bring systems down for their much needed maintenance. One of my tasks was to upgrade our XenServers. They’re not joined to the same pool for historical reasons. One of them is close to 8 years old, the other one is fairly new. For the first server I chose to reboot into the hypervisor after upgrading to 7.2, before upgrading to 7.3. A wise choice. Just for the fun of it, I chose not to reboot into the hypervisor on the second server between 7.2 and 7.3. This left me with the choice of restoring the old 7.1 version or performing a clean reinstall of 7.3. Neither option was inviting, so I had to reboot into the hypervisor prior to upgrading to 7.3. Lesson learned.
The irony of this story is that XenServer 7.4 was released two days ago. Luckily, I can use the new update feature and save me a trip to the server room.
- Download the required updates.
- Extract the
- Transfer the
XS*.xsupdatefiles to, say,
/tmp/xsupon the master.
- Login on the XenServer console.
- Delete old log files in
- Create if necessary, and change directory to
uuidlist=`for f in XS*; do xe patch-upload file-name=$f; done`
for u in $uuidlist; do xe patch-pool-apply uuid=$u; done
- Delete the
- Shutdown the running VMs and restart each node.
If you want to free some disk space by removing old patches, try:
for p in `xe patch-list --minimal | tr , ' '`; do xe patch-destroy uuid=$p; done
Note, this will also remove any pending or unapplied patches.
Also, make sure you give XenServer more than 4 GiB of disk space to
dom0 when installing the system, preferably 8 GiB or even 10 GiB.
[R]emove [the] DVD device from [the] problem[atic] virtual machine:
xe vm-list params=uuid name-label="<your-vm-name>"
xe vbd-list empty=true params=uuid vm-uuid=<your-vm-UUID>
xe vbd-destroy uuid=<vbd-UUID>