> Create Virtual Machines
> Create the virtual machines by doing one of the following:

> • | (Recommended) Create from scratch, using the VMware Virtual Infrastructure Client. This approach is outlined below.

> • | (Not Recommended) Create by converting a physical machine to a virtual machine, using either the standalone version of VMware Converter or the version integrated with VirtualCenter. VMware Converter images the target PC and migrates it into VMware VI3. This method is not recommended for production because this method doesn’t result in an optimal virtual machine. This method is a “quick and dirty” conversion in the event that you want to try out Pano VDS, or if you have a virtual machine that you can’t recreate from scratch.

> To create a desktop virtual machine from scratch:
> To create a virtual machine from scratch, use the VMware Infrastructure Client (VMware VIC).

> 1. | Using the VMware VIC, connect to VirtualCenter.

> 2. | Launch the New Virtual Machine Wizard (File > New > Virtual Machine...), then select Custom as the baseline settings for the virtual machine.

> 3. | Follow the wizard’s instructions to create the initial virtual machine, specifying values for the following settings:

> Parameter | Description
> Name and Location | A descriptive and unique name for your virtual machine template (for example, xptemplate). The location of the virtual machine can be any folder in your datacenter inventory. Pano Logic recommends that you name the folder Templates.
> Host/Cluster | The standalone ESX host or ESX host that is part of a cluster that will be used to run this virtual machine. The location of the initial virtual machine or template does not specify where future virtual machines will reside: you can change this host/cluster at anytime.
> Resource Pool | If your ESX server resources are divided into resource pools, you can assign these resource pools to this virtual machine.
> Datastore | The location where files associated with the virtual machine should be stored.
> Guest Operating System | The operating system that you will install on the virtual machine. It’s best practice that the template name include the name of the operating system (for example, xptemplate).
> CPUs | The number of virtual processors that will be presented to the virtual machine. A single processor is sufficient for most of your users.
> Memory | The amount of memory to allocate to each virtual machine that you create from the template. 512MB is enough for most users running typical Microsoft Office applications. In rare cases where your users are running memory intensive applications, allocate 1 GB.
> Network | The number of virtual network adapters that the virtual machine needs to use. Most virtual desktops need only one network adapter.
> I/O Adapters | BusLogic drivers that come pre-installed with Windows XP are sufficient for Pano VDS users. (For VDI-based deployments, VMware recommends the LSI Logic adapter. However, the LSI Logic driver is not included as part of the Windows XP installation. You must download and add it during the OS installation.)
> Disk | Because you are creating a new virtual machine, choose Create a new virtual disk.
> Disk Capacity | The disk space that you assign to the virtual machine. Assign at least 10 GB. It’s a best practice to store as much of the user’s data on a network share rather than on the virtual machine (locally). When saving locally, ask users to save to My Documents, and back up that data.
> Advanced Options | Accept the default Virtual Device Node. Also, there’s no need to specify a Mode.

> Tip: A few things to consider:

> • | Physical-to-Virtual (P2V)

> Except in select cases Pano Logic does not recommend using a Physical-to-Virtual (P2V) conversion to create a DVM template. A P2V conversion yields large disk image that is difficult to manage in a VDI environment. Other drawbacks associated with a P2V conversion include preservation of any “OS faults” that the physical machine might have had.

> • | DVM disk size

> The size of the virtual disk of a DVM should be kept to a minimum. Large disks will consume more Storage resources and make it longer to provision new DVMs.

> 4. | Before you start the Windows installation, do the following:

> a. | From VirtualCenter, locate the virtual machine that you just created, power on the virtual machine, and select Edit Settings.

> b. | Edit the following hardware settings:

> • | Ensure the CD/DVD drive is present and configured to connect at power on.

> • | Ensure the CD/DVD Device Type is configured to point at the Windows CD or ISO image.

> • | Ensure a Floppy Drive is present and does not connect at power on. The Connect at power on option enables the DVM to boot from that device.

> • | Ensure the Floppy Drive’s Device Type is configured to point at the BusLogic image: /vmimages/floppies/vmscsi-1.2.0.2.flp. This driver improves SCSI virtual disk performance.

> • | Launch the BIOS setup screen by selecting the Force BIOS Setup option.

> • | From VirtualCenter, go to the virtual machine, and click the Console tab.

> • | Click the Boot tab and change the order of the boot options to (1) CD-ROM drive (2) Hard drive, and (3) Removable Devices.

> Next Step(s):

> 1. | (Windows XP) Install Pano Device USB Support

> 2. | Install Windows XP or Vista

Did you find what you're looking for?
v2.5.1