- VT capable OVH server (All OVH & Kimisufi except C-05g)
- Host must have enough RAM and HD for Windows minimum requirements
- Working install of XenServer installed on Host
- NFS ISO Server/repository - Static IP Linux VPS or server with 10-50gb free space
- Access to Windows Server 2008 and Windows 7 setup ISOs
- Local Windows XP pro, Vista Pro or Win7 local computer to run Citrix XENCENTER control panel software and Remote Desktop
- Access to OVH Manager admin account to assign failover IPs
After successfully creating Debian VPS slices on my XenServer, I decided to try getting some Windows flavors going on my slices. Here's a tutorial on how I managed to get a Windows server 2008 R2 VM slice runnning using OVH's Alpha version of XenServer in conjunction with XenCenter for Windows management client. Like most, I was excited to see the Windows templates available in XenServer after installation, only to find that they are empty containers. I got the "No Boot Device" Error after creating my Windows VM's. So I searched around for some answers.
I have also gotten a 32 Bit Version of Windows 7 Enterprise going as well which is a personal copy that I uploaded to my NFS ISO server. I'm sure many have been able to do this as well, and I look forward to any suggestions on how I could streamline and simplfy my Windows installs. But since I haven't seen many tuts here, I decided to add my experience. Follow along carefully, because even one step missed could lock up the whole process!!
ASSIGN Virtual MAC addresses
Before starting this project, it's wise to assign your failover IP's new mac addresses and names in your OVH manager. Since we are using XenServer
Since OVH and Xenserver don't have ISO versions of Windows Server 2008 or Windows 7 in the Xen ISO repository, we'll have to get copies for ourselves. Many versions of Windows are freely available to download from M$ themselves.
Of course you'll have to purchase a serial key in order to activate the software. Although I can't help that portion of this tutorial, I will say that Google and the nice folks at Win7Vista are of immense help in undestanding all of it.
Once you have working ISO versions of Windows server 2008 or Windows 7 available, you'll create an ISO NFS share on 2nd linux computer or VPS share. It must have it's own IP address.. I found that I had to create one outside of the server domain controller in the folder: /var/opt/xen/iso_import, because I quickly ran out of space.
I also tried to create an NFS server in my Windows 7 local computer, but couldn't get the configuration down. The software created for NFS use is clunky and difficult to use. I settled on sharing a portion of a spare Debian 4 VPS I had available. Here's what I did..
On the Debian VPS that I'm creating the NFS server
Then I install NFS server and it's dependencies:
NFS Server Configuration
apt-get install nfs-kernel-server nfs-common portmap
NFS exports from a server are controlled by the file /etc/exports. Each line begins with the absolute path of a directory to be exported, followed by a space-seperated list of allowed clients.
Edit the file according to the example format
/home/vps_iso xxx.xxx.xxx.xxx(rw) www.first.com(ro)
- Where /home/vps_iso is the share
- Where xxx.xxx.xxx.xxx is the computer you'll be connecting from (The Host where Windows will reside). In this case I was connecting through my Kimsufi host server that I was running XenServer 5.5 on..
- Where "<www.first.com>" is an OPTIONAL second client server that needs access to the NFS share. You can use an IP address as well.
- Where "ro" is Read-Only and "rw" is Read-Write Access to the directory.
Force NFS to reread the config file
Crtl+X, Y and enter to CLOSE and SAVE
Now I had to get my ISOs to my share on the NFS server. The easiest way i found was to use wget.
On my NFS server:
Or via FTP
Once it's finished, I rename it to something more manageable:
mv 7600.16385.090713-1255_x64fre_server_eval_en-us-GRMSXEVAL_EN_DVD.iso Windows_Server_2008_r2.iso