Wednesday, 18 September 2013
The vpxuser permission is used for vCenter Server when managing activities for the host. The vpxuser is created when an ESXi host is attached to vCenter Server.
vCenter Server has Administrator privileges on the host that it manages. For example, vCenter Server can move virtual machines to and from hosts and perform configuration changes needed to support virtual machines.
The vCenter Server administrator can perform most of the same tasks on the host as the root user and also schedule tasks, work with templates, and so forth. However, the vCenter Server administrator cannot directly create, delete, or edit users and groups for ESXi hosts. These tasks can only be performed by a user with Administrator permissions directly on each ESXi host.
Vmware Tools Installation not starting with this message "the application has failed to start because the application configuration incorrect reinstalling the application may fix the problem "
Friday, 13 September 2013
Wednesday, 11 September 2013
Resolving the CID mismatch error: The parent virtual disk has been modified since the child was created (1007969)
riptor files affected
- The datastore browser provided in the VMware vSphere Client or VMware Infrastructure Client do not distinguish between virtual machine descriptor (1) and flat or delta files (2). They are collapsed into singular entities to make datastore browsing simpler. As you need to distinguish between the two files, use the additional access methods provided in the referenced article.
- The web-based Datastore Browser, accessible via
https://server-ip, is used to browse VMFS datastores and distinguish between the virtual machine descriptor files and their corresponding associated binary files. You can copy the relevant file from the Datastore Browser for editing. The edited file can be uploaded to the datastore again via the vSphere Client.
- Due to the nature of the problem experienced, the quickest method for resolving the issue is with the Command Line Interface available on the individual ESX host. Utilize this method if you have sufficient background knowledge on command-line usage. Alternatively, you can use the VMware vSphere Command Line Interface (CLI) or VMware vSphere Management Assistant appliance (vMA) to obtain the virtual machine disk descriptor files for review.
- If you are unable proceed, please file a support request with VMware Technical Support. For more information, see Filing a Support Request in My VMware (2006985).
- The virtual machine's
vmware.logfile contains information which identifies the specific disk chain affected. Review the logs and note the location and files affected.
vmx| DISKLIB-LINK : Attach: Content ID mismatch (d0fdb25b != ef4854ee).
vmx| DISKLIB-CHAIN : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm.vmdk" : failed to open (The parent virtual disk has been modified since the child was created).
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002-delta.vmdk" : closed.
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000001-delta.vmdk" : closed.
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-flat.vmdk" : closed.
vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk' with flags 0xa (The parent virtual disk has been modified since the child was created).
vmx| DISK: Cannot open disk "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk": The parent virtual disk has been modified since the child was created (18).
vmx| Msg_Post: Error
vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk' or one of the snapshot disks it depends on.
vmx| [msg.disk.configureDiskError] Reason: The parent virtual disk has been modified since the child was created.----------------------------------------
vmx| Module DiskEarly power on failed.
Note: This indicates that the file
examplevm-000002.vmdkreferences its parent (which in itself references another parent file), one of which has been modified some time after
examplevm-000002.vmdkwas created. You must take corrective measures on any of these files:
- With the problem point (or points) determined, make backup copies of the disk descriptor files that require corrections or editing. In the example above, backups of
- Review the contents of each affected descriptor file and compare the mismatching values. For example:
examplevm-000001.vmdkwithout error. However, the base disk
examplevm.vmdkhas been modified, causing the error.
Correcting the Content ID mismatch
- Confirm that the disks reference each other:
Note: The linking or chain references are highlighted in blue. This example shows that
examplevm-000002.vmdkas a child of
examplevm-000001.vmdk, which in turn is a child of
examplevm.vmdk. These three disk files make up a singular virtual disk from the perspective of the virtual machine and guest operating system.
- Using a text editor, correct the mismatch at either of the two problem points. For more information, see Preferred Editors in Editing configuration files in VMware ESXi and ESX (1017022). You may either correct
examplevm.vmdk, per this example, or the
examplevm-000001.vmdkdisk file. In either circumstance, the
CIDrelationship must be valid.
examplevm.vmdkcan have its CID changed to
, making it match
parentCIDvalue can be changed to
examplevm.vmdk's base disk descriptor file's CID. You may also consider creating a CID value on your own.
Note: The CID consists of eight (8) hexadecimal lower-case digits (
ffffffff) with no delimiter characters.
Verifying the CID corrections
- Log into the VMware vSphere Client or VMware Infrastructure Client.
- Select the virtual machine in the Inventory and click the Summary tab.
- Under Resources, right-click the datastore that contains the virtual machine's configuration file and select Browse. The Datastore Browser opens.
- Locate the virtual machine's directory and files. You can minimize it for now, as it will be used in step 7.
- Right-click the virtual machine and choose Remove from inventory.
- When prompted, confirm your selection by clicking Yes. The virtual machine disappears from the inventory on the left.
- Restore the Datastore Browser from step 4, right-click the virtual machine's configuration file (for example,
examplevm.vmx), and choose Add to Inventory.
- Follow the on-screen prompts to bring the virtual machine back into the inventory.
Warning: Do not power on the virtual machine unless you have a valid copy or backup of all of its files. When the virtual machine has been powered on, further irreversible changes are applied to the disk structure.
- When ready, power on the virtual machine and verify the guest operating system's status. A file system integrity check may be performed to seek out and repair any complications that arise from the disk chain changes that caused the initial CID mismatch.
You can also verify if the CID mismatch has been corrected by running this command against the highest level snapshot :
: If there are messages in the results, the CID mismatch has not been corrected or there is still a mismatch in the snapshot hierarchy.
Alternative procedureTHE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Download two new unofficial study guides and be prepared for your VCAP and VCP exams!