One response to “VMware – Failed to deploy ovf package invalid configuration for device ‘6’” Carl Fugate (@carlfugate) says: September 2, 2015 at 12:12 pm Thanks for the article. The resolution was quite simple by a) just corrected the port group binding prior the storage vmotion task or b) already move the VM away from the Cisco 1000v port group within the old environment.
You can move a virtual machine that was created in Workstation to a different host system or to a different location on the same host system. You can also move a virtual machine to a host system that has a different operating system.
Moving a virtual machine typically involves moving the files that make up the virtual machine. The path names for all files associated with a Workstation virtual machine are relative to the virtual machine directory.
When you move a virtual machine to a different host system or to a different location on the same host system, Workstation generates a new MAC address for the virtual network adapter. Workstation also generates a new MAC address when you rename a directory in the path to the virtual machine configuration file.
Familiarize yourself with how Workstation generates UUIDs for moved virtual machines. See Using the Virtual Machine UUID.
Verify that all virtual machine files are stored in the virtual machines directory.
Some files might reside outside of the virtual machines directory.
@cgtexmex I think this may be related to #4858 but a different error path possibly. I have found the following:
In step 6 we discover that the image store is inconsistent and we try to delete it so it can be recreated; however we have containerVMs using the store which prevents in use files from being erased.
I believe that the inconsistent image store error is because of An error occurred while communicating with the remote host seen in the portlayer log fragment below.
It looks like we cannot delete the actual data files for the VMDKs so we have xxx-delta.vmdk still existing, but no xxx.vmdk or manifest files.
I suspect that the invalid config is because of the missing vmdk descriptor file - however I've yet to confirm that this isn't a business as usual quirk of an NFS datastore.
On the NFS datastore server:
portlayer:
There is also evidence that the image file was deleted previously in a hostd.log - my working assumption is that this is the
rmi busybox call from the initial set of regression tests before the host is killed and that this is not a contributing factor - it did cause me to investigate however so it's noted here:
container-logs-issue4666.zip vpxd-5.log hostd.log hostd.log Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |