($support) = $source =~ /(Windows XP)|(XenServer 5.6)/;
echo “This article is regarding $support\n”
Good evening, all.
So, March 31, 2014 marked the end-of-life for our XenServer 5.6 series. Soon, April 8, 2014 will be fast upon us and will mark the end of Windows XP. The point?
You may be upgrading your XenServer to the latest version to sustain your Windows XP SP3 32-bit virtual machines. Legacy apps, time to transition to Windows 7, etc. Don’t worry as there is no judgement here: I run XP as well on my own XenServer. What can I say? I have older apps, development tools, and other items that are just engrained in me right now and I don’t have the time to test these on Windows 7.
This article is focusing on exactly that: we have the template in XenServer 6.2 SP1 and you will want to update XenTools, right? While I cannot help you with Windows XP updates or things “Microsoft”, I can convey to my colleagues, clients, and partners that the para-virtualization tools for Windows XP SP3 can be installed as I have tested this locally to sustain my VMs with XenServer 6.2 SP1.
If you are installing another version of XenServer (6.0, 6.0.2, or 6.1) then disregard the rest of this article!
First, complete the upgrade to XenServer 6.2 and apply SP1. Once all systems are “checked and ready for launch”, read on to see if the following tips will help you complete the upgrade of XenTools on your Windows XP SP3 VMs under XenServer 6.2 Sp1.
Secondly, from your Windows XP VMs, mount the xs-tools.iso and begin the install process. Follow the tools installation guide and you should be prompted to reboot the host. Once you select “reboot” note if you come across the following visual from XenCenter. If so, then the rest of this article is for you!!!
This means that, well, your Windows XP SP3 VM will reboot, but you can only access safe mode – if that. I know because I tested this on my Windows XP SP3 VM.
The solution is quite straight forward. Ensure the VM is shutdown and from your stand alone (or primary) XenServer, access the command line.
Find out the UUID of your VM by executing:
xe vm-list name-label=”Name of Your Windows XP SP3 VM”
The output should be similar to the following and all we want is the UUID of the VM:
[root@bucketbox ~]# xe vm-list name-label=winxp32sp3
uuid ( RO) : 0d27658c-784b-77b0-9670-fcfb63899d1a
name-label ( RW): winxp32sp3
power-state ( RO): halted
So, to wrap things up we take the UUID of the Windows XP SP3 VM and change the device_id value:
xe vm-param-set uuid=<UUID of your VM, ie 0d27658c-784b-77b0-9670-fcfb63899d1a> platform:device_id=0001
This updates the metadata for tools and you can now proceed to start the VM. You should see (in XenCenter) the trinity of “Start Suspend and Reboot” illuminated!
And this is from my Virtual Desktop to you.