1,798
edits
Changes
New page: <table border="0" cellspacing="0" width="100%"> <tr> <td width="20%">Previous<td align="center">[[Xen Virtualizati...
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[Installing and Running Windows XP or Vista as a Xen HVM domainU Guest|Previous]]<td align="center">[[Xen Virtualization Essentials|Table of Contents]]<td width="20%" align="right">[[Adding USB Devices to a Xen HVM domainU Guest|Next]]</td>
<tr>
<td width="20%">Installing and Running Windows XP or Vista as a Xen HVM domainU Guest<td align="center"><td width="20%" align="right">Adding USB Devices to a Xen HVM domainU Guest</td>
</table>
<hr>
This chapter of [[Xen Virtualization Essentials]] will cover in detail the steps necessary to install and run Microsoft Windows Vista as a virtualized Xen guest.
Since Windows Vista falls into the Xen category of an unmodified operating system (in other words an operating system that has not been altered specifically to run on the Xen hypervisor) paravirtualization is not an option. The best way, therefore, to virtualize Windows Vista is to configure it as a Xen Hardware Virtual Machine (HVM) guest. For information about the primary differences between paravirtualization, hardware virtualization and full virtualization read the chapter of this book entitled [[An Overview of Virtualization Techniques]].
== Requirements for Xen Windows Server 2008 Virtualization ==
This chapter assumes that the Xen host system is running a Xen enabled kernel and that the standard Xen tools (specifically ''xm'') are also installed. In addition, hardware virtualization requires that the host system hardware include either Intel-VT or AMD-V virtualization support. In order to verify this run the following commands on the host system:
For Intel CPUs:
<pre>
grep vmx /proc/cpuinfo
</pre>
For AMD CPUSs:
<pre>
grep svm /proc/cpuinfo
</pre>
If neither of the above command produce output then it is likely these features are unavailable and that your hardware is unable to run Xen HVM guests.
== Windows Vista Installation Media ==
In order to install Windows Vista as a Xen HVM guest the next requirement is the operating system installation media. This is likely to be in the form of a DVD. Alternativiely, if the media was downloaded from the Microsoft web site, it will be in the form of an ISO image file. Installation may be performed directly from the DVD, from an ISO image, or the contents of the DVD may be copied to an ISO image file on the host system.
To create an ISO image simply insert the DVD into a drive, unmount it if it automounts and then run the following command (substituting ''/dev/cdrom'' for your DVD drive device):
<pre>
dd if=/dev/cdrom of=winvista.iso
</pre>
== Preparing Storage Space for Windows Vista ==
Obviously, the Windows Vista guest system will need disk space into which it can install itself and subsequently execute. This space can take the form of either a physical disk drive connected to the host system or a disk image file accessible to the host system. If a physical disk drive is available for the guest, make a note of the device name. This is typically a device beginning with /dev/sd or /dev/hd followed by a letter (for example /dev/sdc or /dev/hdb).
If a disk image is required one may be created using the ''dd'' command-line tool:
<pre>
dd if=/dev/zero of=xenwinvista.img bs=1024k seek=10000 count=0
</pre>
The above command creates a 10Gb image file named ''xenwinvista.img''.
== Creating the Xen Windows Vista Configuration File ==
The next step involves the creation of a domainU configuration file suitable for installing Windows Vista as a Xen guest.
The following file is an example configuration file with the minimal settings required for a Windows Vista Xen guest:
<pre>
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 1024
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
shadow_memory = 8
name = "xenwinvista"
vif = [ 'type=ioemu, bridge=xenbr0' ]
acpi = 1
apic = 1
disk = [ 'file:/home/xen/xenwinvista.img,hda,w', 'file:/home/xen/winvista.iso,hdc:cdrom,r' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="dc"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''
serial='pty'
usbdevice='tablet'
</pre>
The above example assumes that Windows Vista is going to be installed into a disk image and that the installation media is an ISO image file. If, on the other hand, a physical disk is to be used the disk directive might appear as follows (where ''/dev/sdb'' is replaced with the appropriate physcial device name):
<pre>
disk = [ 'phy:/dev/sdb,hda,w', 'file:/home/xen/winvista.iso,hdc:cdrom,r' ]
</pre>
Similarly, the ''disk = '' directive can be modified to perform the installation from a physical DVD drive as in the following example (where ''/dev/hdc'' is modified to reflect the physical device on your host system):
The above line maps physical disk drive ''/dev/sdb'' on the host to ''/dev/hda'' on the guest and ''/dev/hdc'' on the host as the CD/DVD device on the guest (note that the CD/DVD device name on your host may be different depending on your Linux distribution).
Alternatively, if a disk image file is to be used as the disk drive the line might instead read:
<pre>
disk = [ 'phy:/dev/sdb,hda,w', 'phy:/dev/hdb,hdc:cdrom,r' ]
</pre>
A number of the configuration settings shown in the above example are to enable a graphical console for our Windows Vista guest operating system. Xen provides a choice of VNC or SDL for supporting a graphical console when the guest is running. For example the following settings select VNC:
<pre>
vnc = 1
sdl = 0
</pre>
whilst the following selects SDL:
<pre>
vnc = 0
sdl = 1
</pre>
Both SDL and VNC work very well in terms of displaying Windows in a graphical console, although VNC has some distinct advantages over SDL. Firstly, VNC provides greater flexibility than SDL in terms of remote access to the domainU graphical console. With VNC it is possible to connect to the graphical console from other systems, either on the local network or even over the internet. Secondly, when you close a VNC viewer window the guest domain continues to run allowing you to simply reconnect to carry on where you left off. Closing an SDL window, however, immediately terminates the guest domainU system resulting in possible data loss.
By default Xen does not automatically start the VNC console when the domainU guest starts up. In order to have the graphical console spawned automatically, the ''vncconsole = 1'' setting is included.
<pre>
vncconsole=1
</pre>
A number of other configuration options are available to modify the guest environment but the above settings are the minimal settings recommended to run a Windows guest with Xen. Once the configuration file is complete save it as xenwinvista.cfg.
== Starting the Xen Windows Vista HVM Guest ==
With the configuration complete the next step is to start up the Xen guest environment:
<pre>
xm create xenwinvista.cfg
Using config file "./xenwinvista.cfg".
Started domain xenwinvista
</pre>
After a few seconds the VNC or SDL console (depending on the configuration settings) will appear and the Windows Vista installation process will begin. The following figure shows the Windows Vista instance running as a Xen HVM guest displaying in a VNC window:
[[Image:xen_windows_vista_running.jpg|Windows Vista running as a Xen HVM guest]]
<hr>
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[Installing and Running Windows XP or Vista as a Xen HVM domainU Guest|Previous]]<td align="center">[[Xen Virtualization Essentials|Table of Contents]]<td width="20%" align="right">[[Adding USB Devices to a Xen HVM domainU Guest|Next]]</td>
<tr>
<td width="20%">Installing and Running Windows XP or Vista as a Xen HVM domainU Guest<td align="center"><td width="20%" align="right">Adding USB Devices to a Xen HVM domainU Guest</td>
</table>
<tr>
<td width="20%">[[Installing and Running Windows XP or Vista as a Xen HVM domainU Guest|Previous]]<td align="center">[[Xen Virtualization Essentials|Table of Contents]]<td width="20%" align="right">[[Adding USB Devices to a Xen HVM domainU Guest|Next]]</td>
<tr>
<td width="20%">Installing and Running Windows XP or Vista as a Xen HVM domainU Guest<td align="center"><td width="20%" align="right">Adding USB Devices to a Xen HVM domainU Guest</td>
</table>
<hr>
This chapter of [[Xen Virtualization Essentials]] will cover in detail the steps necessary to install and run Microsoft Windows Vista as a virtualized Xen guest.
Since Windows Vista falls into the Xen category of an unmodified operating system (in other words an operating system that has not been altered specifically to run on the Xen hypervisor) paravirtualization is not an option. The best way, therefore, to virtualize Windows Vista is to configure it as a Xen Hardware Virtual Machine (HVM) guest. For information about the primary differences between paravirtualization, hardware virtualization and full virtualization read the chapter of this book entitled [[An Overview of Virtualization Techniques]].
== Requirements for Xen Windows Server 2008 Virtualization ==
This chapter assumes that the Xen host system is running a Xen enabled kernel and that the standard Xen tools (specifically ''xm'') are also installed. In addition, hardware virtualization requires that the host system hardware include either Intel-VT or AMD-V virtualization support. In order to verify this run the following commands on the host system:
For Intel CPUs:
<pre>
grep vmx /proc/cpuinfo
</pre>
For AMD CPUSs:
<pre>
grep svm /proc/cpuinfo
</pre>
If neither of the above command produce output then it is likely these features are unavailable and that your hardware is unable to run Xen HVM guests.
== Windows Vista Installation Media ==
In order to install Windows Vista as a Xen HVM guest the next requirement is the operating system installation media. This is likely to be in the form of a DVD. Alternativiely, if the media was downloaded from the Microsoft web site, it will be in the form of an ISO image file. Installation may be performed directly from the DVD, from an ISO image, or the contents of the DVD may be copied to an ISO image file on the host system.
To create an ISO image simply insert the DVD into a drive, unmount it if it automounts and then run the following command (substituting ''/dev/cdrom'' for your DVD drive device):
<pre>
dd if=/dev/cdrom of=winvista.iso
</pre>
== Preparing Storage Space for Windows Vista ==
Obviously, the Windows Vista guest system will need disk space into which it can install itself and subsequently execute. This space can take the form of either a physical disk drive connected to the host system or a disk image file accessible to the host system. If a physical disk drive is available for the guest, make a note of the device name. This is typically a device beginning with /dev/sd or /dev/hd followed by a letter (for example /dev/sdc or /dev/hdb).
If a disk image is required one may be created using the ''dd'' command-line tool:
<pre>
dd if=/dev/zero of=xenwinvista.img bs=1024k seek=10000 count=0
</pre>
The above command creates a 10Gb image file named ''xenwinvista.img''.
== Creating the Xen Windows Vista Configuration File ==
The next step involves the creation of a domainU configuration file suitable for installing Windows Vista as a Xen guest.
The following file is an example configuration file with the minimal settings required for a Windows Vista Xen guest:
<pre>
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 1024
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
shadow_memory = 8
name = "xenwinvista"
vif = [ 'type=ioemu, bridge=xenbr0' ]
acpi = 1
apic = 1
disk = [ 'file:/home/xen/xenwinvista.img,hda,w', 'file:/home/xen/winvista.iso,hdc:cdrom,r' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="dc"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''
serial='pty'
usbdevice='tablet'
</pre>
The above example assumes that Windows Vista is going to be installed into a disk image and that the installation media is an ISO image file. If, on the other hand, a physical disk is to be used the disk directive might appear as follows (where ''/dev/sdb'' is replaced with the appropriate physcial device name):
<pre>
disk = [ 'phy:/dev/sdb,hda,w', 'file:/home/xen/winvista.iso,hdc:cdrom,r' ]
</pre>
Similarly, the ''disk = '' directive can be modified to perform the installation from a physical DVD drive as in the following example (where ''/dev/hdc'' is modified to reflect the physical device on your host system):
The above line maps physical disk drive ''/dev/sdb'' on the host to ''/dev/hda'' on the guest and ''/dev/hdc'' on the host as the CD/DVD device on the guest (note that the CD/DVD device name on your host may be different depending on your Linux distribution).
Alternatively, if a disk image file is to be used as the disk drive the line might instead read:
<pre>
disk = [ 'phy:/dev/sdb,hda,w', 'phy:/dev/hdb,hdc:cdrom,r' ]
</pre>
A number of the configuration settings shown in the above example are to enable a graphical console for our Windows Vista guest operating system. Xen provides a choice of VNC or SDL for supporting a graphical console when the guest is running. For example the following settings select VNC:
<pre>
vnc = 1
sdl = 0
</pre>
whilst the following selects SDL:
<pre>
vnc = 0
sdl = 1
</pre>
Both SDL and VNC work very well in terms of displaying Windows in a graphical console, although VNC has some distinct advantages over SDL. Firstly, VNC provides greater flexibility than SDL in terms of remote access to the domainU graphical console. With VNC it is possible to connect to the graphical console from other systems, either on the local network or even over the internet. Secondly, when you close a VNC viewer window the guest domain continues to run allowing you to simply reconnect to carry on where you left off. Closing an SDL window, however, immediately terminates the guest domainU system resulting in possible data loss.
By default Xen does not automatically start the VNC console when the domainU guest starts up. In order to have the graphical console spawned automatically, the ''vncconsole = 1'' setting is included.
<pre>
vncconsole=1
</pre>
A number of other configuration options are available to modify the guest environment but the above settings are the minimal settings recommended to run a Windows guest with Xen. Once the configuration file is complete save it as xenwinvista.cfg.
== Starting the Xen Windows Vista HVM Guest ==
With the configuration complete the next step is to start up the Xen guest environment:
<pre>
xm create xenwinvista.cfg
Using config file "./xenwinvista.cfg".
Started domain xenwinvista
</pre>
After a few seconds the VNC or SDL console (depending on the configuration settings) will appear and the Windows Vista installation process will begin. The following figure shows the Windows Vista instance running as a Xen HVM guest displaying in a VNC window:
[[Image:xen_windows_vista_running.jpg|Windows Vista running as a Xen HVM guest]]
<hr>
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[Installing and Running Windows XP or Vista as a Xen HVM domainU Guest|Previous]]<td align="center">[[Xen Virtualization Essentials|Table of Contents]]<td width="20%" align="right">[[Adding USB Devices to a Xen HVM domainU Guest|Next]]</td>
<tr>
<td width="20%">Installing and Running Windows XP or Vista as a Xen HVM domainU Guest<td align="center"><td width="20%" align="right">Adding USB Devices to a Xen HVM domainU Guest</td>
</table>
