Customization failures #17
Comments
|
Hi @kodempsey, You've done everything right, apparently the ESXi host that is performing the guest operations cannot customize the guest type Ubuntu because doesn't have the capability to do so. This is most likely due to the version of the ESXi running on the hypervisor host (not vCenter), please double check your ESXi version and post it here, the plugins are tested against my homelab which runs ESXi 5.5 GA. |
|
Unfortunately I'm not an administrator so I don't seem to be able to view licensing information in vcenter. If I go to the about dialog on the vSphere client app, it says: VMware vCenter Server I can find out from our IT guys if there is more specific version information you are looking for? I am curious though, why customization seems to work as expected when I deploy a virtual machine from a template that I have built manually within vsphere? I would have though if the vSphere server version was unable to do customizations on ubuntu 14.04 16bit that this would not be possible. Best regards, Kristian
|
|
Ask IT for the ESXi version they're running in the host or cluster you're targeting in your Vagrantfile. |
|
This is all I could find in the vSphere client. If these aren't what you're need I'll have to wait until next Monday sorry as it's the weekend here now. Both hosts in the cluster have this at the top of the pane: VMware ESXi, 5.5.0, 2068190 Both also have this in the summary section: (Updated) ESXi-5.5.0-20140302001-standard |
|
That's enough, I will try to reproduce the error on your build. |
|
Hi Fabio, Have you had a chance to try and reproduce this issue yet? Is there anything else I can do to help isolate the problem? Best regards, Kristian |
|
@kodempsey I just noticed that your network configuration is wrong: config.vm.network :public_network,
ip: "192.168.0.1",
netmask: "255.255.255.0",
gateway: "192.168.0.255",
dns_server_list: ['192.168.0.255'],
dns_suffix_list: ['domain']You cannot have your gateway and dns on |
|
Hi Fabio, Sorry, I missed that. I have just tried again with the following however and it still fails customisation: config.vm.network :public_network, Did you manage to get it working with my builds? Regards, Kristian |
|
I was able to get around this by using the following referenced in the sample configuration vcenter.enable_vm_customization = false in my case, i just added it with the rest of the vcenter config options |
|
I have seen this issue where vcenter does not know the template has vmware tools installed on it. |
|
IMHO I think this should be closed because it due to VMware tools, not Vagrant nor the vagrant-vsphere plugin. I solved this by downloading the vmware tools linux.iso from the esxi host. In my packer build I installed vmware tools using the linux.iso. My image successfully runs on esxi and VMware tools runs OK. |
Hi Fabio,
I get customization failures immediately after the vm is cloned from the template in vcenter. I created a box using gosddc/packer-post-processor-vagrant-vmware-ovf with the ubuntu.json (trusty64) template from gosddc/packer-templates. My vagrant file is a default Vagrant file modified based on your example (see below).
I'm using a ubuntu trusty 64 desktop development environment with the following:
Our vcenter is at version 5.5.0 update 2. If I create a ubuntu trusty 64 server vm manually in vcenter, install vmware tools (not latest version) and convert it to a template, i'm able to then deploy a virtual machine with customizations via the wizard and it succeeds. If I try and deploy a virtual machine with customizations via the wizard with the template uploaded by vagrant-vcenter, it fails with the same error as logged below. If I convert both templates to vms, there are several notable differnces in the settings dialog - most notable is the vm version is 8 for the hand rolled vm, and vmx-9 for the vagrant-vcenter one. I can provide more info here if necessary.
Is there something obviously wrong i'm doing or am I perhaps just using an invalid combination of package versions? Any insight would be greatly appreciated.
Best regards,
Kristian
The text was updated successfully, but these errors were encountered: