Search the VMware Knowledge Base (KB)
View by Article ID

Customizing a Guest Operating System That Uses an LVM Other Than Microsoft LDM Fails (1488)

  • 13 Ratings


Why does customization of a guest operating that uses a Logical Volume Manager (LVM) other than the Microsoft Logical Disk Manager (LDM) fail?


Customizing a guest operating system that uses a Logical Volume Manager (LVM) other than the Microsoft Logical Disk Manager (LDM) is not supported.

Customization of such a guest operating system fails because the LVM software usually encodes the volume to partition mapping in a proprietary format outside the disk's partition tables, thereby making the partitions inaccessible to the image customization software.

Windows Dynamic Disks use the Microsoft LDM, so customization of a Windows guest operating system installed on a Dynamic Disk is supported.

Typically, this problem manifests as an error message saying that the system partition could not be found despite the partition being formatted with a supported file system. This problem can occur with Windows and Linux guests. For example, customizing a Linux guest operating system that uses a LVM results in the following error message:

        CustomizeImage failed:Error: 0x800004005 source: 
        ImgCustDisk::FindLinuxSystemPartition Description: Could not
        system partition -- /etc/ must reside on an Ext2/Ext3

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 13 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 13 Ratings