I bridge my ethernet on local machine so the virtual guest has an external IP as well.
The question are:
a) why it takes around a minute for bridge to come up after I wake up the computer from sleep. Is this normal? I’m seeing the same on at least two machines.
and
b) even more annoying is that virtual guest looses connection for good - i have to shut it down, close virtual manager and start it again to get an active connection. And even this does not work all the time.
My bridge is nothing fancy, just wires up ethernet and that’s it
Mar 07 12:48:19.017480 MYHOST kernel: r8169 0000:08:00.0 enp8s0: Link is Down
Mar 07 12:48:19.017718 MYHOST kernel: nm-br0: port 1(enp8s0) entered learning state
…
Mar 07 12:48:19.019403 MYHOST kernel: nvme nvme0: D3 entry latency set to 10 seconds
Mar 07 12:48:19.019478 MYHOST kernel: nvme nvme0: 16/0/0 default/read/poll queues
…
Mar 07 12:48:19.020218 MYHOST kernel: r8169 0000:08:00.0 enp8s0: Link is Down
….
Mar 07 12:48:19.020523 MYHOST kernel: nm-br0: port 1(enp8s0) entered disabled state
Mar 07 12:48:19.020693 MYHOST kernel: nm-br0: topology change detected, propagating
…
Mar 07 12:48:19.022219 MYHOST kernel: PM: suspend exit
Mar 07 12:48:19.590057 MYHOST kernel: r8169 0000:08:00.0 enp8s0: Link is Up - 1Gbps/Full - flow control off
Mar 07 12:48:19.590418 MYHOST kernel: nm-br0: port 1(enp8s0) entered blocking state
Mar 07 12:48:19.590437 MYHOST kernel: nm-br0: port 1(enp8s0) entered listening state
Mar 07 12:48:21.080852 MYHOST kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 07 12:48:21.105833 MYHOST kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 07 12:48:21.105909 MYHOST kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 07 12:48:21.105923 MYHOST kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 07 12:48:21.105946 MYHOST kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 07 12:48:34.769827 MYHOST kernel: nm-br0: port 1(enp8s0) entered learning state
Mar 07 12:48:50.130547 MYHOST kernel: nm-br0: port 1(enp8s0) entered forwarding state
Mar 07 12:58:40.369294 MYHOST kernel: nm-br0: port 2(vnet0) entered blocking state
Mar 07 12:58:40.369331 MYHOST kernel: nm-br0: port 2(vnet0) entered disabled state
Mar 07 12:58:40.369348 MYHOST kernel: vnet0: entered allmulticast mode
Mar 07 12:58:40.369369 MYHOST kernel: vnet0: entered promiscuous mode
Mar 07 12:58:40.369384 MYHOST kernel: nm-br0: port 2(vnet0) entered blocking state
Mar 07 12:58:40.369399 MYHOST kernel: nm-br0: port 2(vnet0) entered listening state
Mar 07 12:58:55.825832 MYHOST kernel: nm-br0: port 2(vnet0) entered learning state
Mar 07 12:59:11.185824 MYHOST kernel: nm-br0: port 2(vnet0) entered forwarding state
Mar 07 12:59:11.185950 MYHOST kernel: nm-br0: topology change detected, sending tcn bpdu
Mar 07 13:06:52.057923 MYHOST kernel: nm-br0: port 2(vnet0) entered disabled state
Mar 07 13:06:52.057998 MYHOST kernel: vnet0 (unregistering): left allmulticast mode
Mar 07 13:06:52.058021 MYHOST kernel: vnet0 (unregistering): left promiscuous mode
Mar 07 13:06:52.058030 MYHOST kernel: nm-br0: port 2(vnet0) entered disabled state
Mar 07 13:07:19.356894 MYHOST kernel: nm-br0: port 2(vnet1) entered blocking state
Mar 07 13:07:19.356946 MYHOST kernel: nm-br0: port 2(vnet1) entered disabled state
Mar 07 13:07:19.356970 MYHOST kernel: vnet1: entered allmulticast mode
Mar 07 13:07:19.356994 MYHOST kernel: vnet1: entered promiscuous mode
Mar 07 13:07:19.357013 MYHOST kernel: nm-br0: port 2(vnet1) entered blocking state
Mar 07 13:07:19.357026 MYHOST kernel: nm-br0: port 2(vnet1) entered listening state
Mar 07 13:07:34.481831 MYHOST kernel: nm-br0: port 2(vnet1) entered learning state
Mar 07 13:07:49.841828 MYHOST kernel: nm-br0: port 2(vnet1) entered forwarding state
Mar 07 13:07:49.841954 MYHOST kernel: nm-br0: topology change detected, sending tcn bpdu
