Context Navigation

Changes between Initial Version and Version 1 of Ticket #13873, comment 1

initial	v1
3	3	1. If you have the vboxnetadp module loaded (which is required for host-only networking) then when you start VB a vboxnet0 interface gets created. VB only needs to be started once for that to get created and it is left assigned even if you close down VB. It is the presence of that vboxnet interface which seems to cause the problem with resume. If you don't have a vboxnet interface assigned on your host then suspend/resume works OK (i.e. if you don't ever load vboxnetadp, i.e. if you don't want to use host-only networking on any guest).
4	4
5		2. Now if you suspend and resume your host with vboxnet0 present, vboxnet0 sometimes (usually for me) "steals" the main ~~DHCP provided IP address normally assigned to my default host enp3s0 interface~~. The host enp3s0 interface is left un-assigned so the host boots without any network connectivity.
	5	2. Now if you suspend and resume your host with vboxnet0 present, vboxnet0 sometimes (usually for me) "steals" the main static IP address normally assigned to my default host enp3s0 interface [The static IP address is configured as a "manual" address within NetworkManager]. The host enp3s0 interface is left un-assigned so the host boots without any network connectivity.
6	6
7	7	3. If I use the GNOME network control panel to disable vboxnet0, and then enable enp3s0, then enp3s0 gets it's IP address back and all is well.