5.0

2 On the Hardware tab, select the virtual hard disk and click Remove.
3 Click OK to save your changes.
Using Lock Files to Prevent Consistency Problems on Virtual Hard Disks
A running virtual machine creates lock files to prevent consistency problems on virtual hard disks. Without
locks, multiple virtual machines might read and write to the disk, causing data corruption.
Lock files have a .lck suffix and are created in subdirectories in the same directory as the virtual disk (.vmdk)
files. A locking subdirectory and lock file are created for .vmdk files, .vmx files, and .vmem files.
A unified locking method is used on all host operating systems so that files shared between them are fully
protected. For example, if one user on a Linux host tries to power on a virtual machine that is already powered
on by another user with a Windows host, the lock files prevent the second user from powering on the virtual
machine.
When a virtual machine powers off, it removes the locking subdirectories and the lock files. If the virtual
machine cannot remove these locking controls, one or more stale lock files might remain. For example, if the
host system fails before the virtual machine removes its locking controls, stale lock files remain.
When the virtual machine restarts, it scans any locking subdirectories for stale lock files and, when possible,
removes them. A lock file is considered stale if the lock file was created on the same host system that is now
running the virtual machine and the process that created the lock is no longer running. If either of these
conditions is not true, a dialog box warns you that the virtual machine cannot be powered on. You can delete
the locking directories and their lock files manually.
Locks also protect physical disk partitions. Because the host operating system is not aware of this locking
convention, it does not recognize the lock. For this reason, you should install the physical disk for a virtual
machine on the same physical disk as the host operating system.
Moving a Virtual Hard Disk to a New Location
A key advantage of virtual hard disks is their portability. Because the virtual hard disks are stored as files on
the host system or a remote computer, you can move them easily to a new location on the same computer or
to a different computer.
For example, you can use Player on a Windows host system to create virtual hard disks, move the disks to a
Linux computer, and use the disks with Player on a Linux host system.
Configuring Virtual Ports
You can add virtual parallel (LPT) ports and virtual serial (COM) ports to a virtual machine. A Player virtual
machine can use up to three parallel ports and up to four virtual serial ports.
n
Add a Virtual Parallel Port to a Virtual Machine on page 83
You can attach up to three bidirectional parallel (LPT) ports to a virtual machine. Virtual parallel ports
can output to parallel ports or to files on the host system.
n
Configure a Virtual Parallel Port on a Linux 2.6.x Kernel Host on page 84
Linux 2.6.x kernels that support parallel ports use the modprobe
modulename and modprobe parport_pc
modules. Player requires that the parallel port PC-style hardware option (CONFIG_PARPORT_PC) is built
and loaded as a kernel module.
n
Configure Permissions for a Parallel Port Device on a Linux Host on page 84
Some Linux distributions do not grant a virtual machine access to the lp and parport devices by default.
If this is the case on your Linux host system, you must add the VMware user to the group that has
permission to access those devices.
Getting Started with VMware Player
82 VMware, Inc.