Automation

Hi,

I'm trying to establish a connection between a series of existing virtual disks and a certain VM. So far, I have been able to connect all of my thin-provisioned disks without any problems with the following line:

$targetVM | New-HardDisk -DiskPath ($disk.Filename)

However, this command seems to not always function when it comes to thick-provisioned disks, resulting in the following error message:

http://puu.sh/9xBs9/a73fd64b20.png

I'm currently trying to get a workaround going for thick disks, but I'm out of ideas.

Thanks in advance.

Have a look at Re: Adding copied harddisk (VMDK) to a VM

I've tried both adding the "-Persistence Persistent" to the New-HardDisk cmdlet and using your add-HD command. I'm still getting the same error on vSphere client. I've managed to narrow the problem down to thick-provisioned disks that are considered Persistent, if that helps.

EDIT: Nevermind that, looks like some thick disks that are considered non-Persistent also fail their connection to the VM.

Bump.

Did you already check the vpxd log on the vCenter ?

Sometimes there is more info on why a specific method fails.

So! I just now got to look at the vpxd log on my vCenter, and this is what it looks like after attempting to connect a thick provisioned disk to one VM:

http://puu.sh/9GFht/4d4073312c.png

The error seems to be something along those lines repeated multiple times:
"Could not find entry for host vim.HostSystem:host-67 in overhead map generated for DRS for vm /vpx/vm/#XYZ"

My vCenter then generates a dump file on the issue:

http://pastebin.com/8rDRD0mm

Any help with deciphering the following bits of information would be greatly appreciated.

I'm not to sure that message, which is no error btw, but an informational message, has anything to do with the issue you are seeing.

I would look around the entry for the ReconfigVM method that is called to add the disk.

Here is some information regarding the issue found in our vpxd logs. I couldn't post the entire log because it's too large for pastebin:

http://pastebin.com/7UK29vVP

It looks as if the BackingInfo is missing.

That object should have the datastore and the VMDK file path.

Was this when you did the New-Harddisk cmdlet ?

Yes, this is immediately following an attempt to connect the disk to a VM using the New-HardDisk cmdlet in the following manner:

$targetVM = Get-VM asg-vlcenter

$targetVM | New-HardDisk -DiskPath ($disk.Filename)

And the Add-HD function is showing the same errors in the vpxd log ?

Just wanted to say the issue has been resolved. Using the Add-HD function and having my script sleep for a couple of seconds between each added disk seems to work just fine.

Thanks for the help!