11.0 VM Can't access host via network?

[Tsaukpaetra]

Build FreeNAS-11-MASTER-201704280408 (83eff7b)

I have a Windows VM all set up and configured, and it seems to work well accessing the network and the internet in general, but when I try to access network services on the host FreeNAS server, it inexplicably fails. Basically, it can find it (by virtue of DNS), but any connections don't connect, as if the box were unplugged (note, not refused, TCP connections just timeout).

I'm thinking this might be an issue with how the host side complains about setting link properties:

Code:

root@bob:~ # tail /var/log/messages
Apr 29 14:41:06 bob kernel: bridge0: link state changed to DOWN
Apr 29 14:41:06 bob kernel: bridge0: link state changed to DOWN
Apr 29 14:41:06 bob bridge0: error setting interface capabilities on lagg0
Apr 29 14:41:06 bob kernel: bridge0: link state changed to UP
Apr 29 14:41:06 bob kernel: bridge0: link state changed to UP
Apr 29 14:41:06 bob kernel: cxl0: promiscuous mode enabled
Apr 29 14:41:06 bob kernel: cxl1: promiscuous mode enabled
Apr 29 14:41:06 bob kernel: lagg0: promiscuous mode enabled
Apr 29 14:41:07 bob kernel: tap0: link state changed to UP
Apr 29 14:41:07 bob kernel: tap0: link state changed to UP

If that's the case, I think I could get away with forcing the VM in question (at the moment I only have one) to use one of the unused ethernet ports on the server instead, but I can't try this because there's no such configuration option in the FreeNAS 11 UI...

Any hints?

 

[FreeNASftw]

You can pass through hardware (like a NIC) using the command line - precise instructions are available online.

I raised a bug about the lagg error a few days ago - I'm unsure exactly what capabilities it fails to set, so hopefully the IX gurus can see what's going on there.

Also, if you troubleshoot the lack of communication, do you get this error - "Windows Sockets registry entries required for network connectivity are missing"? - I'm working through this now.

 

[FreeNASftw]

I've updated the bug ticket with things I've tried.. Still no joy.
Bug #23579

 

[Tsaukpaetra]

Also, if you troubleshoot the lack of communication, do you get this error - "Windows Sockets registry entries required for network connectivity are missing"? - I'm working through this now.

Not getting that specific error, but I have noticed that network traffic slows down to the VM to a literal crawl after a few megabytes.

It's just so strange because I don't recall this much trouble when testing this on another machine (that's not a server, just a desktop).

 

[FreeNASftw]

If the other machine was only a desktop - did it have a LAGG interface or only a single?

 

[Tsaukpaetra]

If the other machine was only a desktop - did it have a LAGG interface or only a single?

You might be on to something, it was a normal desktop.

But, that's one of the reason I want to bind the VM to one of the other unused ethernet interfaces (that aren't in LAGG).

 

[Tsaukpaetra]

Disabled the LAGG, made no difference... :(
And here I was confident everything was going so well in testing...

 

[Tsaukpaetra]

So following all intuition, I decided to try a fresh install. Works fine!

Now I guess I just need to figure out how to compare the hardware configs of two VMs according to Windows...

 

[Tsaukpaetra]

Disabled the LAGG, made no difference... :(
And here I was confident everything was going so well in testing...

Ok, something in my network must have been borked. I did a whole whitewash of the networking system in Windows (deleted all the nics in the guest, reset winsock, etc). And now it seems to be working correctly.

Ugh.

 

[FreeNASftw]

I tried all that and got nowhere with mine. I tried changing the NIC from the Intel to the Virtio one, reset winsock etc... Nothing.

 

[Tsaukpaetra]

I tried all that and got nowhere with mine. I tried changing the NIC from the Intel to the Virtio one, reset winsock etc... Nothing.

Yeah my trick was VirtIO, delete absolutely everything under network adapters (had to "show hidden devices"), reset winsock reset a few other things, reboot (twice) and things were better. Other than that, I don't know what else you should try except maybe check there's an update for FreeNAS.

I'm also using version 136 of the VirtIO drivers.

 

[Tsaukpaetra]

Update: Nevermind, apparently there was a glitch in how I was starting and re-starting the VM so much that networking got screwed up on the FreeNAS side.
It broke half of the network to the point that wifi connected devices weren't able to connect and it basically looked like someone plugged in an ethernet cord straight back into the main switch (that the FreeNAS box was hooked up to. Makes sense when you think about it).

But now that I've rebooted and got that all cleared up, I'm back to square 2: Got good network connectivity, but the VM can't talk to the host at all.

This is what I'm getting in my logs at present:

Code:

May  2 15:39:17 bob kernel: igb1: link state changed to DOWN
May  2 15:39:17 bob kernel: igb1: link state changed to DOWN
May  2 15:39:22 bob kernel: igb1: link state changed to UP
May  2 15:39:22 bob kernel: igb1: link state changed to UP
May  2 15:40:05 bob tap0: Ethernet address: 00:bd:02:4b:fb:00
May  2 15:40:06 bob bridge0: Ethernet address: 02:54:72:d7:dc:00
May  2 15:40:06 bob kernel: tap0: promiscuous mode enabled
May  2 15:40:06 bob kernel: bridge0: link state changed to DOWN
May  2 15:40:06 bob kernel: bridge0: link state changed to DOWN
May  2 15:40:06 bob bridge0: error setting capabilities on lagg0: 22
May  2 15:40:06 bob bridge0: can't disable some capabilities on lagg0: 0x400702
May  2 15:40:06 bob kernel: bridge0: link state changed to UP
May  2 15:40:06 bob kernel: bridge0: link state changed to UP
May  2 15:40:06 bob kernel: cxl0: promiscuous mode enabled
May  2 15:40:06 bob kernel: cxl1: promiscuous mode enabled
May  2 15:40:06 bob kernel: lagg0: promiscuous mode enabled
May  2 15:40:07 bob kernel: tap0: link state changed to UP
May  2 15:40:07 bob kernel: tap0: link state changed to UP
May  2 15:48:24 bob kernel: tap0: link state changed to DOWN
May  2 15:48:24 bob kernel: tap0: link state changed to DOWN
May  2 15:48:25 bob bridge0: error setting capabilities on lagg0: 22
May  2 15:48:25 bob bridge0: can't disable some capabilities on lagg0: 0x400
May  2 15:48:35 bob tap0: Ethernet address: 00:bd:21:10:03:00
May  2 15:48:35 bob bridge0: error setting capabilities on lagg0: 22
May  2 15:48:35 bob bridge0: can't disable some capabilities on lagg0: 0x400702
May  2 15:48:35 bob kernel: tap0: promiscuous mode enabled
May  2 15:48:36 bob kernel: tap0: link state changed to UP
May  2 15:48:36 bob kernel: tap0: link state changed to UP

Mentioning https://bugs.freenas.org/issues/23447 because now that I'm back on the LAGG it could be still affecting this exact thing.