Virtualized Environments282 VMWare EnvironmentIn particular, you should make sure that the latest VMWare NetworkInterface Card driver (VmxNet driver) is actually installed andworking. Using this driver will actually improve performance andfailing to use it may result in creating an image that will not be boot-able by Image Manager Clients.Adding VM Support to Existing ImagesYou can modify an existing Image Manager virtual drive so that itcan be used to boot VMs. This virtual drive would usually be used toboot physical machines prior to enhancing it to support networkbooting VMs.The easiest way to achieve this is to use UbiBoot Extractor to extractthe required data from an existing VMWare guest running Windows,then use UbiBoot Inserter to insert the previously extracted data inyour existing image. Refer to “Adding Network Boot Devices to anImage” on page 87 for information about using UbiBoot Extractorand Inserter.Once your existing image has been enhanced to support VMwareguest network card as a boot device, you will have to boot a VM offthis image in order to install the rest of the drivers for the VM. Youwould usually do this operation in Admin mode (or in CVolWrite/Normal mode and then use CVolMerge to update the image).In order to boot your VM off a Neoware Image Manager virtualdisk, you must enable the VM to boot from the network using PXE(see below).Note that it is sometimes not possible to boot a VM image without ithaving a VMWare virtual disk drive (.vmdk file) attached to it, evenif that disk drive is not used. Therefore, you can attach the smallestpossible disk drive to your VM and never partition or format it.Also, use a dynamic non-persistent disk.When your VM can boot off the Neoware Image Manager virtualdisk, it will detect some new hardware. In order to provide the com-plete set of drivers, you would use VMWare tools.
