Professional Documents
Culture Documents
Configuring, Removing, and Adding Virtual Devices : Editing Hardware Settings, General Settings
the virtual device. The backing can be a physical device or a file that resides on the host.
Most backings are fully specified as part of the virtual machine configuration. For example,
for a device backed by a file, the exact location of the file is stored.
Client devices are the exception. When a virtual device is backed by a client device, the
actual connection is controlled from the actual VI Client instance that the user wants to
provide the backing. See Configuring Virtual Machine Options and Resources for more
information on using client devices.
To access the Virtual Machine Properties dialog box
1. In the inventory panel, select the virtual machine object for which you want to configure,
add, or remove devices.
2. Right-click and choose Edit Settings, or choose the Edit Settings link in the
information panel.
To see what type of change has been made to a device in this edit session
Use the Hardware tab in the Virtual Machine Properties dialog box to view settings for,
reconfigure, and remove virtual devices.
All items in the list on the left of the Hardware tab represent configurable virtual hardware
settings. Except for Memory and CPUs (if CPUs appears), each entry represents a single
virtual device.
The text of each item name is formatted in one of the following ways, with formats that
indicate the state of change for that device in this edit session.
Generally, a device is in one of the first three states. The remaining two states occur when a
device is being replaced in its original position and apply only to SCSI controllers and to NICs
on some hosts and virtual machines. For these two device types, you can choose from more
than one specific virtual device implementation. For example, a virtual SCSI controller can be
a Buslogic controller or an LSI Logic controller. When the device type is to be changed, the
old device is replaced by a new device while preserving as many of the settings and
connections as possible. The “replacement” and “replacing” states reflect this composite
operation.
Configuring, Removing, and Adding Virtual Devices : Editing Hardware Settings, General Settings : Devices
Not Affected by the Add or Remove Buttons
SCSI controllers are implicitly added and removed based on the assignment of devices to
them. If you change a device's SCSI node assignment, or add a new device, on a given
virtual SCSI bus number (for example, a SCSI node setting of (1:3) on virtual SCSI bus 1)
and no controller exists for that bus, a controller is immediately created. Similarly, when you
click OK after an edit session, any controllers whose buses are left empty are removed.
Generally, all the SCSI controllers in a virtual machine are of the same type, and that type is
based on the VMware software recommendation for the virtual machine's guest operating
system. If a virtual machine has been manually edited to have more than one kind of SCSI
controller and a new one is being implicitly created, its type is that of the existing controller
for the lowest-numbered bus with a controller.
Configuring, Removing, and Adding Virtual Devices : Editing Hardware Settings, General Settings :
Reconfiguring the Virtual Devices
Note: Even guest operating systems that support SMP might require reinstallation if the
number of processors or CPUs changes.
On hyperthreaded uniprocessor hosts, performance of virtual machines with virtual SMP
might slow to an unacceptable level.
To change the virtual processors configuration
1. In the Virtual Machine Properties dialog box Hardware tab, click CPUs.
2. Select the number of virtual processors for the virtual machine.
3. Click OK to save your changes and close the Virtual Machine Properties dialog box.
Configuring, Removing, and Adding Virtual Devices : Configuring Memory Settings for a Virtual Machine
Configuring, Removing, and Adding Virtual Devices : Configuring a Network Adapter (NIC)
because the Tools provide the driver needed by that adapter type. A Vlance adapter uses
a stock driver that the guest operating system provides and so does not require that the
Tools be installed on the virtual machine.
To change from the vmxnet to Vlance or Vlance to vmxnet adapter type:
a. To change from Vlance to vmxnet: If you are not confident that you are running the
latest version of the VMware Tools, close the Virtual Machine Properties dialog box and
install the latest Tools on the virtual machine. Re-open the Virtual Machine Properties
dialog box and click the Network Adapter you want to configure. Click the Change
Type button.
b. To change from vmxnet to Vlance: Click the Change Type button.
See your system documentation for your legacy system for further details.
Note: If your virtual machine was created on ESX Server 3.0 or greater and runs a 32-
bit guest operating system, the adapter type is Flexible. The Flexible adapter functions
as a Vlance adapter if the the adapter’s driver is the stock driver the guest operating
system. The Flexible adapter functions as a vmxnet adapter if the vmxnet driver has
been installed on the virtual machine as part of the VMware Tools installation.
If your virtual machine was created on ESX Server 3.0 or greater and runs a 64-bit guest
operating system, the adapter type is E1000. If you change a virtual machine from a 32-
bit to a 64-bit guest operating system, or the reverse, you must remove the existing
network adapter and replace it with a new one, or the virtual machine will not power on.
If you do a hardware upgrade on a legacy virtual machine, the adapter type for that
upgraded machine is as follows:
• If the adapter type was Vlance, the adapter type on the upgraded virtual machine is
Flexible. That adapter functions as a Vlance adapter would function. If you want to
obtain significantly better performance, you need only install the VMware Tools on the
virtual machine as described in Step 5a above.
• If the adapter type is vmxnet, the adapter type on the upgraded virtual machine is still
vmxnet. However, you cannot change this adapter’s type to Vlance, as you would have
been able to do on a legacy virtual machine.
6. Click OK to save your changes and close the Virtual Machine Properties dialog box.
To remove a Network Adapter
1. In the Virtual Machine Properties dialog box Hardware list, click the Network Adapter
you want to remove.
2. To remove the network adapter, click the Remove button.
If you do not want to remove it, click Restore.
3. Click OK to remove the network adapter and close the Virtual Machine Properties dialog
box.
Configuring, Removing, and Adding Virtual Devices : Configuring a CD-ROM or DVD-ROM Drive
You can configure up to two 1.44MB disk drives. You can use physical drives available on the
host computer, image (.flp) files, or client devices. However, a disk drive can be used only by
the host operating system or by one virtual machine at a time. If you run more than one
virtual machine simultaneously, you might want to select which one (if any) has access to the
drive. See To boot the virtual machine from a client CD-ROM.
Note: When you add or edit a file-backed disk drive on an ESX Server 3.0 host, the Browse
Datastore dialog box displays.
Conditions
To disable or enable access to a client device disk drive while the virtual machine is running,
choose the floppy disk client device icon in the toolbar.
To change the floppy drive configuration
1. In the Virtual Machine Properties dialog box Hardware list, click Floppy Drive.
2. Change the Device Status options as needed.
Device Status settings required privilege: Connection. This group is disabled if the
device is configured as a client device.
• Connected – Connect or disconnect the virtual floppy drive while the virtual machine
is running.
• Connect at power on – The drive is connected whenever you power on the virtual
machine. You can change this setting when the virtual machine is powered on or
powered off.
3. Select a Device Type option.
Device Type settings required privilege: Set Floppy Media.
• To boot from this floppy drive, see To boot the virtual machine from a client CD-ROM.
• Host Device – Choose the device from the drop-down menu.
• Use existing floppy image in datastore – Use an existing floppy image file.
• Create new floppy image – Create a new floppy image file.
Browse to a datastore location, type a name for the floppy image (.flp) file, and select
that file. A blank floppy image file is created when you use this configuration operation.
Note: The file is created immediately. This is not a persistent setting in the virtual
machine. If you edit the virtual machine’s configuration again immediately after
creating a new floppy image file, the new floppy drive is selected in the list, the Use
existing floppy option is selected, and the name of the file you created appears in the
pathname field.
See Adding a Floppy Drive for how to configure each option.
4. Click OK to save your changes and close the Virtual Machine Properties dialog box.
Note: If the Floppy device is set to connect to a client device, and the Connected check box
is selected, the Floppy settings appear greyed-out if you switch to another hardware device
and then come back to the Floppy tab. To restore the ability to edit these settings, close the
Virtual Machine Properties dialog box, and reopen it.
To remove an existing drive
1. In the Virtual Machine Properties dialog box Hardware list, click the Floppy Drive you
want to remove.
2. Click the Remove button.
3. Select the Removal option.
Click Restore to not remove the drive.
4. Click OK to remove the drive and close the Virtual Machine Properties dialog box.
7. Under I/O Mode, configure this serial port to use interrupt mode or polled mode.
8. If the software in a particular virtual machine will be polling the serial port in a method
for which yielding the CPU is not desirable, deselect the Yield CPU on Poll option.
The Yield CPU on Poll check box is selected by default. Because most software uses
interrupt-driven I/O, the assumption that polled I/O will be in a busywait loop is usually
valid. This behavior reduces the extra load on system resources caused by polled I/O.
Using one virtual machine to perform a “remote” debug on a second virtual machine
performs significantly better with this optimization turned on
9. Click OK to save your changes and close the Virtual Machine Properties dialog box.
To remove the serial port
1. In the Virtual Machine Properties dialog box Hardware list, click Serial Port.
2. Click the Remove button.
3. Click OK to remove the disk and close the Virtual Machine Properties dialog box.
Configuring, Removing, and Adding Virtual Devices : Viewing a USB Controller Configuration
Configuring, Removing, and Adding Virtual Devices : Adding a Virtual Device : Adding an Ethernet Adapter
(NIC)
Configuring, Removing, and Adding Virtual Devices : Adding a Virtual Device : Adding a Hard Disk
d. Click Next.
To use an existing virtual disk:
a. Browse and select the disk file path.
b. Click Next.
To use a mapped SAN LUN:
a. Select the LUN to use for the raw disk and click Next.
b. Select a datastore and click Next.
c. Select the compatibility mode:
Physical allows the guest operating system to access the hardware directly.
Virtual allows the virtual machine to use VMware snapshots and other advanced
functions.
d. Click Next.
5. Select a virtual device Node from the drop-down menu.
Under Virtual device node you can select which SCSI device identifier to use for the
drive. For example, if you select SCSI 0:2, the guest operating system recognizes the
drive as ID 2 on controller 0.
Disk Modes for ESX Server 3.0 and later
ESX Server 3.0 provides full virtual machine snapshotting. With snapshots, the Disk Mode
describes how the virtual hard disk participates in snapshots. Normally, the disk functions as
it would in a physical machine, with changes written to the disk controlled by the snapshot
mechanism. When you make a disk independent of the snapshot mechanism, snapshot
operations do not affect the disk contents. When a disk is independent, it can be:
• Persistent – The disk operates normally except that changes to the disk are permanent
even if the virtual machine is reverted to a snapshot.
• Nonpersistent – The disk appears to operate normally, but whenever the virtual
machine is powered off or reverted to a snapshot, the contents of the disk return to their
original state (all later changes are discarded).
Disk Modes for ESX Server 2.x
Versions of ESX Server earlier than 3.0 do not provide snapshots. Some of the functions of
snapshots were provided on a per-disk basis by a richer set of disk modes. On legacy virtual
machines, the following disk modes are possible:
• Persistent – The disk operates normally. Changes are immediately and permanently
written to the disk.
• Nonpersistent – The disk appears to operate normally while the virtual machine is
powered on, but when it is powered off, the disk contents revert to the original contents.
• Undoable – The disk appears to operate normally, but when the virtual machine is
powered off, choose whether to make changes to the disk permanent or discard them.
• Append – The disk appears to operate normally, but disk changes are kept separate
from the original values. Whenever the virtual machine is powered on, choose whether to
commit all the accumulated changes permanently, discard them, or continue recording
changes until the next power-on.
6. Click Next.
7. Review the information on the Ready to Complete page.
Make any needed changes to the appropriate page.
8. Click Finish.
Configuring, Removing, and Adding Virtual Devices : Adding a Virtual Device : Adding a SCSI Device
Conditions
Configuring, Removing, and Adding Virtual Devices : Adding a Virtual Device : Adding a DVD/CD-ROM Drive
b. If you select client, either select Pass through and select the check box to connect
exclusively to the virtual machine, or select ATAPI emulation.
c. If you select host, choose the drive from the drop-down list.
d. If you select host and you do not want the DVD/CD-ROM drive connected when the
virtual machine starts, deselect Connect at power on.
Use ISO Image
a. Enter the path and filename for the image file, or click Browse to navigate to the file
and select the file.
b. If you do not want the DVD/CD-ROM drive connected when the virtual machine starts,
deselect Connect at power on.
5. Click Next.
6. Specify the virtual device node the drive uses in the virtual machine.
7. Click Next.
8. Review the information on the Ready to Complete page.
Make any needed changes to the appropriate page.
9. Click Finish.
Configuring, Removing, and Adding Virtual Devices : Adding a Virtual Device : Adding a Floppy Drive
Configuring, Removing, and Adding Virtual Devices : Adding a Virtual Device : Adding a Serial Port
5. Deselect the Connect at power on check box if you want. By default, the serial port
starts connected when you power on the virtual machine.
6. If the software in a particular virtual machine will be polling the serial port in a method
for which yielding the CPU is not desirable, deselect the Yield CPU on Poll option.
The Yield CPU on Poll check box is selected by default. Because most software uses
interrupt-driven I/O, the assumption that polled I/O will be in a busywait loop is usually
valid. This behavior reduces the extra load on system resources caused by polled I/O.
Using one virtual machine to perform a “remote” debug on a second virtual machine
performs significantly better with this optimization turned on.
7. Click Next.
8. Review the information on the Ready to Complete page.
Make any needed changes to the appropriate page.
9. Click Finish.
Configuring, Removing, and Adding Virtual Devices : Adding a Virtual Device : Adding a Parallel Port