can't ping/access ubuntu VM soon(ish) after reboot

[jaaassh]

I guess this is the difference:

Code:

[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33 Client 192.168.1.127 gone
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33 Statistics             events    Transmit/ RawEquiv ( saved)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  FramebufferUpdate   :      1 |         0/        0 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  LastRect            :      1 |        12/       12 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  tight               :     58 |     12174/  3146424 ( 99.6%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  RichCursor          :      1 |       255/      255 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  TOTALS              :     61 |     12441/  3146691 ( 99.6%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33 Statistics             events    Received/ RawEquiv ( saved)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  PointerEvent        :     47 |       282/      282 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  FramebufferUpdate   :      2 |        20/       20 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  SetEncodings        :      1 |        56/       56 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  SetPixelFormat      :      1 |        20/       20 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33  TOTALS              :     51 |       378/      378 (  0.0%)
[2019/01/11 15:58:33] (DEBUG) VMService.run():286 - ubuntu1804: 11/01/2019 10:58:33   other clients:

Some client 192.168.1.127 disappears? fwiw, 192.168.1.127 is freenas.

 

[KrisBee]

If your VM works again after a FreeNAS reboot, then I assume you've gone through its logs/systmed journal etc. for any indication of a possible cause of the virtual network crash. Powering off/stopping the VM once it has lost its network connection should tear down the associated tap device on the FreeNAS host. That should be seen in both the middlewared.log and in output of ifconfig. At that stage I'd expect your associated bridge to still be present. Rather than rebooting FN, surely you can delete and then recreate the appropriated bridge, adding your active NIC, at the CLI, and then try restarting your VM.

 

[dlavigne]

If this is still an issue after U2 comes out in a few weeks, it's worth reporting at bugs.freenas.org. If you end up creating a report, post the issue number here.