Citrix Systems 6.2.0 Preparing for Cloning a Windows VM Using VSS, Using XenCenter, Using the CLI

Page 43

without BIOS strings: immediately after its creation. If a VM does not have BIOS strings set when it is started, the standard XenServer BIOS strings will be inserted into it, and the VM will become BIOS-generic.

To allow installation of Reseller Option Kit (BIOS-locked) OEM versions of Windows, onto a VM running on a XenServer host, the BIOS strings of the VM will need to be copied from the host with which the ROK media was supplied.

In order to install the BIOS-locked media that came with your host, you will need to follow the steps below:

Using XenCenter

Click the Copy host BIOS strings to VM check box in the New VM Wizard.

Using the CLI

1.Run the vm-installcopy-bios-strings-fromcommand and specify the host-uuid as the host from which the strings should be copied (that is, the host that the media was supplied with):

xe vm-install copy-bios-strings-from=<host uuid> \ template=<template name> sr-name-label=<name of sr> \ new-name-label=<name for new VM>

This returns the UUID of the newly created VM. For example:

xe vm-install copy-bios-strings-from=46dd2d13-5aee-40b8-ae2c-95786ef4 \ template="win7sp1" sr-name-label=Local\ storage \ new-name-label=newcentos

7cd98710-bf56-2045-48b7-e4ae219799db

2.If the relevant BIOS strings from the host have been successfully copied into the VM, the command vm- is-bios-customizedwill confirm this:

xe vm-is-bios-customized uuid=<VM uuid>

For example:

xe vm-is-bios-customized \ uuid=7cd98710-bf56-2045-48b7-e4ae219799db

This VM is BIOS-customized.

Note:

When you start the VM, it will be started on the physical host from which you copied the BIOS strings.

Warning:

It is your responsibility to comply with any EULAs governing the use of any BIOS-locked operating systems that you install.

9.9. Preparing for Cloning a Windows VM Using VSS

The only supported way to clone a windows VM is by using the Windows utility sysprep to prepare the VM.

Computers running Windows operating systems are uniquely identified by a Security ID (SID). When cloning a Windows VM, it is important to take steps to ensure the uniqueness of the SID. Cloning an installation without taking the recommended system preparation steps can lead to duplicate SIDs and other problems. Because the SID identifies the computer or domain as well as the user, it is critical that it is unique. For more information, refer to the Microsoft Knowledge Base article 314828, "The Microsoft policy for disk duplication of Windows installations".

36

Image 43
Contents Citrix XenServer 6.2.0 Virtual Machine Users Guide Trademarks Contents VM Migration with XenMotion and Storage XenMotion Importing the Demo Linux Virtual Appliance Windows VM Release Notes Setting Up a Red Hat Installation Server Overview About this DocumentXenServer Documentation Creating VMs Virtual MachinesOther Methods of VM Creation Importing an Exported VM XenServer ToolsPage Supported Guests, Virtual Memory, and Disk Size Limits Supported Guests and Allocating ResourcesOperating System Minimum Maximum Minimum Disk Space 4GB 8GB Operating System Experimental GuestsXenServer Product Family Virtual Device Support Deprecated GuestsVirtual device Linux VMs Windows VMs VM Block Devices Template Name Description Basic Procedure for Creating a Windows VMCreating Windows VMs Available Windows TemplatesAttaching an ISO Image Library Using XenCenter to Create a VMTo create a Windows 7 32-bit VM Page Installing a Windows VM from an ISO Repository Using the CLI Using the CLI to Create a Windows VMCreating Linux VMs Distribution Vendor Install From Network From CD RepositoryCreating a Linux VM by Installing from a Physical CD/DVD Network Installation Notes Creating a Linux VM by Installing From an ISO ImageTo install Debian using a preseed file Advanced Operating System Boot ParametersTo install Rhel Using a Kickstart File To install the guest agent Installing the Linux Guest AgentLinux Distribution Installation Notes Additional Installation Notes for Linux DistributionsIP address Preparing to Clone a Linux VMAdditional Debian Notes Machine NamePage Storage XenMotion VM Migration with XenMotion and Storage XenMotionXenMotion and Storage XenMotion XenMotionLive VDI Migration Migrating a VM using XenCenterLimitations and Caveats To Move Virtual Disks Updating XenServer Tools for Windows VMs To uninstall the XenServer ToolsUpdating VMs Updating Windows Operating SystemsPage Creating vApps Creating a vApp using XenCenterVApps Managing vApps in XenCenterTo start a vApp Start and shutdown vApps using XenCenterDeleting vApps using XenCenter Deleting vAppsTo export a vApp Importing and Exporting vAppsTo import a vApp Advanced Notes for Virtual Machines VM Boot BehaviorPersist XenDesktop Private Desktop Mode Reset XenDesktop Shared Desktop ModeInstalldir/xensetup.exe /S /norestart To Enable Remote Desktop on a Windows VM Windows Volume Shadow Copy Service VSS providerConnecting to a Windows VM Using Remote Desktop To enable the Windows XenServer VSS providerTime Handling in Linux VMs Time Handling in Windows VMsTo set individual Linux VMs to maintain independent times Installing a VM from Reseller Option Kit BIOS-locked MediaGuest OS Dependent wallclock Independent wallclock Using XenCenter Preparing for Cloning a Windows VM Using VSSUsing the CLI Cloning Windows VMs Assigning a GPU to a Windows VM for Use with XenDesktopTo detach a Windows VM from a GPU using the xe CLI To assign a GPU to a Windows VM using XenCenterTo assign a GPU to a Windows VM using xe CLI To detach a Windows VM from a GPU using XenCenterDetach the GPU from the VM by entering the following Importing the Demo Linux Virtual Appliance To Import the Demo Linux Virtual Appliance Using XenCenterUseful Tests Page Supported Formats Importing and Exporting VMsFormat Description Attribute Description Open Virtualization Format OVF and OVAXVA Format Disk Image Formats VHD and VmdkXVA Version 1 Format Operating System FixupImporting VMs Transfer VMTo use the RawVDI transfer protocol Importing VMs from OVF/OVA To Import VMs from OVF/OVA using XenCenterPage Importing Disk Images To Import VMs from a Disk Image using XenCenterImporting VMs from XVA To Import VMs from XVA Files VM using XenCenterExporting VMs To Import a VM from XVA using the xe CLIExporting VMs as OVF/OVA To Export VMs as OVF/OVA using XenCenter Exporting VMs as XVA To Export VMs as XVA Files using XenCenterTo Export VMs as XVA Files using the xe CLI Release Notes Appendix A. Windows VM Release NotesRed Hat Enterprise Linux 4.5 to Appendix B. Linux VM Release NotesPreparing a Rhel 4.5 to 4.8 guest for cloning Red Hat Enterprise LinuxSuse Enterprise Linux 10 SP3 CentOSOracle Enterprise Linux Suse Enterprise Linux 10 SP1Ubuntu Creating an ISO on a Linux computer Appendix C. Creating ISO ImagesOn a Windows computer Enabling a Graphical Console on Debian Squeeze VMs Appendix D. Enabling VNC for Linux VMsConfiguring GDM to use VNC Determining the Location of your VNC Configuration FileVNC Screen Resolution Firewall SettingsCreate the xinetd.d file, /etc/xinetd.d/vnc-server-stream Enabling VNC for RHEL, CentOS, or OEL 6.x VMsChecking for a VNC Server Setting up SLES-based VMs for VNCEnabling Remote Administration Modifying the xinetd ConfigurationTo Open the VNC Port on Sles 10.x VMs Firewall To Open the VNC Port on Sles 11.x VMs Firewall Checking RunlevelsNFS Appendix E. Setting Up a Red Hat Installation ServerCopying Installation Media Enable Remote AccessHttp FTPControlling Linux VM Crashdump Behaviour Appendix F. Troubleshooting VM ProblemsTo enable saving of Linux VM crash dumps VM CrashesTroubleshooting Boot Problems on Linux VMs