Xen also available as LiveCD at http://www.xen.org/download/LiveCD/livecd-xen-3.2-0.8.2-i386.iso & http://www.xen.org/download/LiveCD/livecd-xen-3.2-0.8.2-amd64.iso
Not too sure what's xen Cloud Platform cd
Xen for some reasons don't want to shutdown (poweroff). This could be due to dom0 running on the hypervisor. The system running on Dom0 not able to shutdown the hypervisor.
- Microsoft Hyper-V Server 2008 R2
- part of Microsoft Windows Server 2008 R2
If you want a reasonable working system, install Microsoft Windows Server 2008 R2 and use the Hyper-V console that comes with it.
The following servers run happily on Hyper-V
- Windows 2003 32 bit
- Windows 2003 64 bit
- windows 2008 32 bit
- Windows 2008 64 bit
- Windows SBS 2003 32 bit
- Windows SBS 2008 64 bit
- The mouse don't work on remote desktop to Hyper-V console (I would prefer vmware esx/esxi to over come this shortcoming)
- Grub4Dos based boot system has trouble under Hyper-V (This is not an issue with vmware esx/esxi)
- Make sure VT enabled in BIOS
- Make sure you connect to Legacy Network (non-default) http://technet.microsoft.com/en-us/library/cc770380.aspx
- Dell PowerEdge 1950 (1U) and 2950 (2U) are known good candidates for hosting Hyper-V
- Server consolidation
- Saves Money as we don’t need as many physical boxes
- smaller foot print in the lab (space / Power / cables / cooling)
- Server management cost is reduced as the number of physical boxes reduced
- No need for physical CD
- No need to burn CD
- No need to insert the CD (Physical presence)
- No Need to take out the CD (Physical presence)
ESXi - free version
.vmdk - Virtual Machine Disk file format
.VMX file – this file is the primary configuration file for a virtual machine.
Enabling SSH in VMware Hypervisor.
Press ALT F1 at the physical console of the system and type 'unsupported' and then the root password of the machine. From there uncomment ssh in /etc/inetd.conf and restart services with a /sbin/services.sh restart.
Moving VM's in VMware ESXi
Connect to the hypervisor that your VMDK files are on via ssh. From there you can navigate to the vmx and vmdk files you wish to migrate under the /vmfs directory. Your VM's should be under /vmfs/volumes/datastore#. Once you are in the directory you wish to migrate you can use SCP to copy the physical disk files to the other machine. With a command similar to scp * root@hostname:/vmfs/volumes/ datastore#/vm-dir. You will need to have the destination directory created ahead of time. Once the files have copied you will need the specific command VMware-cmd for the registration of the VM with the hypervisor and to power on the VM. A command similar to VMware-cmd -H hostname_of_hypervisor -s register /vmfs/volumes/datastorename/vm-dir/vm.vmx datacenter-name resource-pool. The easiest way to register VM's is through the VMware Console. VM's can be registered with the hypervisor by navigating
to the datastore on the summary tab under the main hypervisor in the GUI. Double click on the datastore to browse the files. Right click on the VMX file you wish to register and select add to inventory.
Now that our VM has been moved and registered we are ready to boot it. You can do this from the remote command line with VMware-cmd -H hostname_of_hypervisor /vmfs/volumes/datastorename/vm-dir/vm.vmx start or through the GUI.
- vim-cmd vmsvc/getallvms
- vim-cmd vmsvc/power.getstate
- vim-cmd vmsvc ---- returns full list
For getting delay in power on BIOS (useful in super fast machine). Add line in .vmx file
- bios.bootDelay = "5000"
- bios.forceSetupOnce = "TRUE"
What you'll need
- VMware Player:
- The easiest way to get a finished VM running; all you need to do is point the VM information file at
vmplayer, and you're good to go.
- VMware kernel modules for Linux:
- All VMware products on Linux use kernel modules to get monitoring and networking functionality working, so you'll need those.
- A text editor:
- We'll be doing some hacking of configuration and VM information files, which means your favourite text editor.
- GNU Parted:
- In order for us to tell VMware about the hard disk, we need to know a few things about the disk; we'll also be doing a little hacking of the partition table. Parted allows us to do this from the command line, and quite easily too.
Stage 1: Setting up a virtual hard disk
unit scommand, which tells Parted to print out its values in terms of disk sectors: we'll be using these values in the VMDK file. Also note the second
unitcommand, to provide the values in cylinders; that allows us to fetch the disk geometry in CHS format.
Stage 2: The VMware information file
Stage 3: Setting up Windows
windows.iso; this is the Tools CD image. If you feel like wasting a CD, burn the image to one, or you can mount the image as a drive using Daemon Tools or similar software.
C:\VMToolsor something similar. Then dump the following into a
ToolsHelperLock.txtin the same directory. The lock file will be used by the helper script to work out if it needs to reboot. Once you've done this, add the script to your Start Menu's Startup folder, and you'll be away.
Stage 4: Virtual Windows
Snags: Getting the network running
iptablestrickery, so I'm putting it in as a part of this guide.
192.168.1.0/24, so I decided to put the virtual network at
192.168.58.0/24. This means the host gets an address of
192.168.58.1on the NAT network, and the VM's network connection gets a static IP of
192.168.58.2; it also means the following changes to the Linux host's configuration:
ra0has had a virtual interface added, dedicated to the transfer of traffic for the virtual machine NAT. The particular configuration files you need to change may differ depending on the distribution; the changes above are from my Gentoo system.
In the End: Windows in a VM
- No 2 Windows licenses
- No need to keep track of changes and synch between the 2 windows installations.
- Autoprotect (?)
- Instant suspend/resume