We are currently evaluating Veeam. Our configuration will be rather small in the light of most VMware deployments. We will have two servers and we plan to use one as fallback server for the other in case of an emergency. To achive this most of the guests are replicated between the hosts.
After I configured replication and let it run for a few times, I tested the failover scenario with two different Windows 2008 server (one SP2, the other R2). The replicas seemed to start without a problem, but were unreachable. After inspection I discovered that the virtual NIC wasn't connected and forcing a connect resulted in an 'Invalid configuration for device '0' error . The only way I have found to fix this is:![Vmware vm shows invalid Vmware vm shows invalid](/uploads/1/2/4/8/124804897/661992888.jpg)
1: Remove the NIC from the guest (using Virtual Machine Properties)![Vmware Vmware](http://blog.mrpol.nl/wp-content/uploads/2013/01/012913_0943_SolvingtheI2.png)
2: Add the NIC again but uncheck connect at power on (the guest will hang if you forget this)
3: Start the guest and wait until the login prompt
4: Force connection
5: It works
The funny thing is that it will not only work, but the newly added NIC will even have the settings of the original one.
BTW, the reason that I found this so quickly was that the same thing happened when I tried to run a VM that I moved from an ESXi host on an ESX host. And then, I didn't find this solution so soon .
Ideas anyone?
Jan
After I configured replication and let it run for a few times, I tested the failover scenario with two different Windows 2008 server (one SP2, the other R2). The replicas seemed to start without a problem, but were unreachable. After inspection I discovered that the virtual NIC wasn't connected and forcing a connect resulted in an 'Invalid configuration for device '0' error . The only way I have found to fix this is:
Mar 07, 2017 @zaksoup @cunnie I am using bosh create-env with init configuration, issue is still there,but i noticed one spec difference when asked out IaaS guys to give hostd logs from 2 vsphere env. There is a difference in deviceChange.backing.parent, in vsphere 5.5 it is null where as in in vsphere 6 it points to stemcell vmdk, and the vmdk delete is occurring in vsphere 6 where this property is.
![Vmware vm shows invalid Vmware vm shows invalid](/uploads/1/2/4/8/124804897/661992888.jpg)
1: Remove the NIC from the guest (using Virtual Machine Properties)
![Vmware Vmware](http://blog.mrpol.nl/wp-content/uploads/2013/01/012913_0943_SolvingtheI2.png)
2: Add the NIC again but uncheck connect at power on (the guest will hang if you forget this)
3: Start the guest and wait until the login prompt
4: Force connection
5: It works
The funny thing is that it will not only work, but the newly added NIC will even have the settings of the original one.
BTW, the reason that I found this so quickly was that the same thing happened when I tried to run a VM that I moved from an ESXi host on an ESX host. And then, I didn't find this solution so soon .
Ideas anyone?
Jan
Posted by4 years ago
Archived
VSphere fails to deploy OVF package
OK so I created an OVF package (using workstation version 10) for a virtual machine I've built (just a basic win8 machine I made to test all this out and learn with) and I'm trying to import it into vsphere 5.5.
I go through the steps pointing it to the ovf template for the machine, leave the name the same, give it thin provision and when it's trying to deploy, it says 'Failed to deploy OVF package: Invalid configuration for device '5'.'
I am going through this virtual machine's hardware configuration trying to figure out what could be causing this error and I'm stumped. Google search doesn't offer much to go with (at lest for a device 5 error)
I've got the CD drive unchecked to not connect at power on (I tried turning on legacy emulation first) and connection set to auto detect.
I've got the LAN set to NAT with that also unchecked so it doesn't connect at power on
I changed USB controller setting from usb 3.0 to 2.0 which changed the original error message of device 6 to device 5.
I set sound card to not connect at power on
If I go to the change hardware compatibility wizard, it has 'compatible with ESX server' checked by default.
I'm pretty much stumped on this one and no google searching can point to what in particular vSphere considers to be device 5.
Can anyone provide any info on what I could be doing wrong here? I feel like it should not be putting up this bad of a fight :|
I have a couple other virtual machines I built to mess around with and have not tried exporting those and importing them into VSphere yet but I may do that monday if I can't find anything on this error before then.
EDIT: I fixed it.
I right clicked on the test VM and went to 'Manage' -> 'Change Hardware Compatibility'
In the hardware wizard, I selected Workstation 8.0 instead of 10.0, re-exported it and it imported into vSphere without any issues. I fired it up and everything is working.
67% Upvoted