Example 1: unsupported root disk layouts for encapsulation

Figure: Boot, swap and root configured on three primary partitions, and free space on the disk shows an example of an unsupported layout with boot, swap and root configured on three primary partitions, and some existing free space on the disk.

Figure: Boot, swap and root configured on three primary partitions, and free space on the disk

Boot, swap and root configured on three primary partitions, and free space on the disk

This layout, which is similar to the default Red Hat layout, cannot be encapsulated because only one spare primary partition is available, and neither the swap partition nor the free space lie within an extended partition.

Figure: Workaround by reconfiguring swap as a logical partition shows a workaround by configuring the swap partition or free space as an extended partition, and moving the swap area to a logical partition (leaving enough space for a logical partition to hold the private region).

Figure: Workaround by reconfiguring swap as a logical partition

Workaround by reconfiguring swap as a logical partition

The original swap partition should be deleted. After reconfiguration, this root disk can be encapsulated.

Figure: Workaround by reconfiguring /boot as a directory shows another possible workaround by recreating /boot as a directory under /, deleting the /boot partition, and reconfiguring LILO or GRUB to use the new/boot location.

Figure: Workaround by reconfiguring /boot as a directory

Workaround by reconfiguring /boot as a directory

Warning:

If the start of the root file system does not lie within the first 1024 cylinders, moving /boot may render your system unbootable.

After reconfiguration, this root disk can be encapsulated.

More Information

Example 3: supported root disk layouts for encapsulation

Example 1: supported root disk layouts for encapsulation