A quick post about an annoyance I encountered while recomposing a View Horizon Linked-Clone desktop pool to multiple local datastores. In this situation multiple replicas will be created from the Parent VM.
These replicas are created simultaneously; however during this process the task pane in the vCenter Server shows many .vmdk access errors on the parent VM and as a result replicas are created one after the other.
VMware KB “Deploying multiple virtual machines in VMware vCenter Server 5.x and 6.0.x from the same template fails with the error: vmdk access error (2114026)” explains that this issue occurs because of locked –ctk.vmdk files. These files are part of the Change Block Tracking (CBT) mechanism. The KB provides instructions how to modify the settings of the Parent VM by disabling CBT.
However after editing the .vmx file and deleting the –ctk.vmdk files from the datastore, the files reappeared immediately. To resolve this behavior, SSH to an ESXi host and browse to the datastore where the Parent VM is located.
Then, edit ALL .vmdk files and remove or comment out the line starting with; changeTrackPath=.
Now, the –ctk.vmdk files will be gone for good.
To prevent third-party applications from enabling CBT, you can add the following line to the .vmx file of the Parent VM: ctkDisallowed=”true”.
As always, I thank you for reading and welcome your comments.
The folks at VMware are very excited to announce the upcoming VMware vSphere Beta Program. This program enables participants to help define the direction of the most widely adopted industry-leading virtualization platform. Folks who want to participate in the program can now indicate their interest by filling out this simple form. The vSphere team will grant access to the program to selected candidates in stages. This vSphere Beta Program leverages a private Beta community to download software and share information. We will provide discussion forums, webinars, and service requests to enable you to share your feedback with us.
You can expect to download, install, and test vSphere Beta software in your environment or get invited to try new features in a VMware hosted environment. All testing is free-form and we encourage you to use our software in ways that interest you. This will provide us with valuable insight into how you use vSphere in real-world conditions and with real-world test cases, enabling us to better align our product with your business needs.
Some of the many reasons to participate in this beta opportunity:
- Receive early access to the vSphere Beta products
- Interact with the vSphere Beta team consisting of Product Managers, Engineers, Technical Support, and Technical Writers
- Provide direct input on product functionality, configurability, usability, and performance
- Provide feedback influencing future products, training, documentation, and services
- Collaborate with other participants, learn about their use cases, and share advice and learnings
To make the most of it, you have already deployed vSphere 5.5 and 6.0 in a portion of your environment. As a good participant, you are expected to:
- Online acceptance of the Master Software Beta Test Agreement will be required prior to visiting the Private Beta Community
- Install beta software within 3 days of receiving access to the beta product
- Provide feedback within the first 4 weeks of the beta program
- Submit Support Requests for bugs, issues and feature requests
- Complete surveys and beta test assignments
- Participate in the private beta discussion forum and conference calls