Logical Domains Manager Does Not Validate Disk Paths and Network Devices

Bug ID 6447740: The Logical Domains Manager does not validate disk paths and network devices.

Disk Paths

If a disk device listed in a guest domain's configuration is either non-existent or otherwise unusable, the disk cannot be used by the virtual disk server (vds). However, the Logical Domains Manager does not emit any warning or error when the domain is bound or started.

When the guest tries to boot, messages similar to the following are printed on the guest's console:

WARNING: /virtual-devices@100/channel-devices@200/disk@0: Timeout
connecting to virtual disk server... retrying

In addition, if a network interface specified using the net-dev= property does not exist or is otherwise unusable, the virtual switch is unable to communicate outside the physical machine, but the Logical Domains Manager does not emit any warning or error when the domain is bound or started.

Recover From an Errant net-dev Property Specified for a Virtual Switch

1. Issue the ldm set-vsw command with the corrected net-dev property value.

2. Reboot the domain hosting the virtual switch in question.

Recover From an Errant Virtual Disk Service Device or Volume

1. Stop the domain owning the virtual disk bound to the errant device or volume.

2. Issue the ldm rm-vdsdev command to remove the errant virtual disk service device.

3. Issue the ldm add-vdsdev command to correct the physical path to the volume.

4. Restart the domain owning the virtual disk.

Network Devices

If a disk device listed in a guest domain's configuration is being used by software other than the Logical Domains Manager (for example, if it is mounted in the service domain), the disk cannot be used by the virtual disk server (vds), but the Logical Domains Manager does not emit a warning that it is in use when the domain is bound or started.

When the guest domain tries to boot, a message similar to the following is printed on the guest's console:

WARNING: /virtual-devices@100/channel-devices@200/disk@0: Timeout
connecting to virtual disk server... retrying

Recover From a Disk Device Being Used by Other Software

1. Unbind the guest domain.

2. Unmount the disk device to make it available.

3. Bind the guest domain.

4. Boot the domain.