Not sure if this is ideal, but I will describe what I've done to fix this.
# Tell DHCP client to speak to 10.10.X.X DHCP server at boot
# as our networking VLAN isn't passing usual DHCP requests using 255.255.255.255
# broadcast, this can be debugged via `dhcp -d -v ens160`
# add the single line between "--" use the IP of DHCP server
If the connection only needs to run the same list of commands on the ESXi host, one option to consider is using SSH forced commands. This feature allows you to force certain SSH keys to only run a given command on login.
This is handled through the authorized_keys file. On ESXi, it uses /etc/ssh/keys-root/authorized_keys for root logins and has this format:
I came to the following workaround since the /sbin/auto-backup.sh script didn't add the keys-<user>/* folder to the state.tgz archive:
Create the /etc/ssh/keys-<user> folder and the /etc/ssh/keys-<user>/authorized_keys file so that ssh commands can be executed from another machine (I won't go into details about this step, since there is ...
My build agent VM is Ubuntu 20.04 LTS, it did not have DHCP
pre-configured when I made a snapshot.
It should have.
If the VM had a static IP address when you took a snapshot of it, all clones created from that snapshot will try to use the same network config when they boot. This should not work at all, even if you wait when deploying them.
What I think is ...
Check the easy stuff first, on VM configuration:
Do you have any cd drive or iso connected?
Are more vCPUs enabled on VM that the limit allowed by your vSphere license?
Since you've enabled fault tolerance logging on the vMotion kernel, I suppose you have enabled and tested vMotion. Do this please if you haven't.
What is your ...