6.2. Installing a Windows XP Guest as a fully virtualized guest

6.2. Installing a Windows XP Guest as a fully virtualized guest

virt-manager can install Windows XP as a fully-virtualized guest. However there are some extra steps which must be followed in order to complete the installation successfully. This section explains the installation process and extra steps needed to get Windows XP fully virtualized guests installed.

Itanium® support

Presently, Red Hat Enterprise Linux hosts on the Itanium® architecture do not support fully virtualized windows guests. This section only applies to x86 and x86-64 hosts.

  1. First you start virt-manager and select the New tab to create a new virtual machine. As you install a Windows based virtual machine you need to select the option to install a Fully virtualized guest:

  2. Next you choose a descriptive system name:

  3. Specify the location for the ISO image you want to use for your Windows installation:

  4. Select the storage backing store, either a file based image can be used or a partition or logical volume:

  5. Specify the virtual machine resources such as CPU and Memory:

  6. Before the installation will continue you will see the summary screen. Press Finish to proceed to the actual installation:

  7. Now the actual Windows installation will start. As you need to make a hardware selection it is important that you open a console window very quickly after the installation has started. Once you press Finish make sure you set focus to the virt-manager summary window and select your newly started Windows guest. Double click on the system name and a console window will open. Quickly press F5 to select a new HAL, once you get the dialog box in the Windows install select the 'Generic i486 Platform' tab (you can scroll through the selections using the Up and Down arrows.

  8. The installation will proceed like any other standard Windows installation:

  9. You will be asked to partition your drive:

  10. After your drive has been formatted Windows will start copying the files onto your new hard drive:

  11. After setup has completed your Windows virtual machine will be rebooted:

  12. You will have to halt the virtual machine after its initial reboot as you need to manually edit the virtual machine's configuration file which is located in /etc/xen/VirtualMachineName. You can halt the virtual machine using the xm destroy WindowsGuest command, where WindowsGuest is the name of your virtual machine.

  13. You will need to modify the disk entry and add a cdrom entry to the config file. The old entry will look similar to the following:

    disk = [ 'file:/var/lib/xen/images/winxp.dsk,hda,w' ]

    and the new entry should look like the following:

    disk = [ 'file:/var/lib/xen/images/winxp.dsk,hda,w' ,
    'file:/xen/pub/trees/MS/en_winxp_pro_with_sp2.iso,hdc:cdrom,r', ]
  14. Now you can restart your Windows virtual machine using the xm create WindowsGuest command, where WindowsGuest is the name of your virtual machine.

  15. Once you open the console window you will see Windows continuing with the setup phase:

  16. If your installation seems to get stuck during the setup phase you can restart the virtual machine using the command mentioned above. This will usually get the installation to continue. As you restart the virtual machine you will see a Setup is being restarted message:

  17. After setup has finished you will see the Windows boot screen:

  18. Now you can continue with the standard setup of your Windows installation:

  19. After you completed the setup process you will be presented with your new Windows desktop or login screen:

Note: This documentation is provided {and copyrighted} by Red Hat®, Inc. and is released via the Open Publication License. The copyright holder has added the further requirement that Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. The CentOS project redistributes these original works (in their unmodified form) as a reference for CentOS-5 because CentOS-5 is built from publicly available, open source SRPMS. The documentation is unmodified to be compliant with upstream distribution policy. Neither CentOS-5 nor the CentOS Project are in any way affiliated with or sponsored by Red Hat®, Inc.