Part 10: Getting A Bit Hyper-V
Now that Xen & LVM are set up and the config file has been created, it’s time to spin things up and install Hyper-V Server. The following image shows Remmina Remote access with VNC and RDP connections configured and ready on the right, and the terminal showing the Xen domain list ready with only dom0 showing in the list, on the left.
Note: Prior to v4.5 the default toolstack for Xen was Xend. Xen now uses the XL toolstack as default (see here for details)
As part of preperation, a VNC connection should be created and saved. I’m using Remmina Remote Access. The connection format should be ipaddress:port. The IP address to connect to is the same IP address as the host machine (in this case, my machine IP 192.168.0.9) and the port is 5900 (the port number is incremented by 1 for each VM running) giving a connection address of 192.168.0.9:5900. There is no need to add username or password at this point.
RDP connections can be created as and when needed once a static IP address has been assigned to the server.
To start the VM, the following command is issued from the command prompt:
root@ripley:/home/canderson/vm# xl create hyperv-vm.cfg
Providing there are no errors in the cfg file Xen will show:
Parsing config from hyperv-vm.cfg
Installing Hyper-V Server:
Once the ‘create’ command has completed then a VNC session needs to be started. If there is no previous installation of Hyper-V Server then setup will start automatically. If there is an existing installation to be over-written then the following screen will be shown and a key must be pressed to initiate the setup program otherwise the existing installation will be started.
Press any key to start the installation (Remmina automatically captures the keyboard on gaining focus).
From this point on, the installation of Hyper-V Server is identical to what it would be if it was being installed on standard hardware.
After the server reboots, re-establish the VNC session and change the admin password.
Join me for Part 11 where we’ll install Windows Server 2012 R2 and manage Hyper-V server with the built-in tools.
And for the non binary speakers who are still hanging around, Part 11 is Part 3 in binary #geekhumour