wiki.getshifting.com

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


fixvmnetworkdisconnectedaftervmotion

Fix: VM gets Network Disconnected After vMotion

Summary: A possible cause for a disconnected VM after a vMotion
Date: Around 2014
Refactor: 26 January 2025: Checked links and formatting.

Symptom: after a vMotion the network card gets disconnected, and even when the box is checked, still the VM is not getting connected.
Issue: The vSwitch gets created with 120 ports by default, if the number of VMs/NICs goes over this there are no ports left. This is not checked by vMotion/DRS/HA so no warnings will be displayed. To solve it, vMotion the VMs back, change the number of ports of the vSwitch and reboot the host.

fixvmnetworkdisconnectedaftervmotion.txt · Last modified: by 127.0.0.1

Exception: Git command failed to perform periodic pull: From https://dev.azure.com/getshiftingcom/Documentation/_git/knowledge * branch main -> FETCH_HEAD fatal

Exception: Git command failed to perform periodic pull: From https://dev.azure.com/getshiftingcom/Documentation/_git/knowledge * branch main -> FETCH_HEAD fatal

An unforeseen error has occured. This is most likely a bug somewhere. It might be a problem in the gitbacked plugin.

More info has been written to the DokuWiki error log.