9.10-STABLE upgrade VMWare Interface Problem

Status
Not open for further replies.

madmaxed

Cadet
Joined
Jan 20, 2016
Messages
4
I have been running FreeNAS 9.3-STABLE for about 2 months now. Got everything configured under ESXi 6.0 using the VMXNET3 interfaces as VMX3F0 and VMX3F1. Also have a Plex jail manually setup using directions found on here instead of the plug-in.

Upgraded from the GUI to 9.10-STABLE and my interfaces went to VMX0 and VMX1 upon reboot. From the command prompt I was able to figure out how to get VMX0 assigned so I could use the Web GUI. However, I cannot figure out how to get my jail reattached properly so the network interface of the jails is correct. I have VIMAGE selected for the jails, and I know if I turn this off I can select the "new" VMX0. But I would prefer to keep all my settings as they were.

Any insight would be greatly appreciated.
 

madmaxed

Cadet
Joined
Jan 20, 2016
Messages
4
I fixed my own problem. Had to update the vmxnet3.ko file manually in the /boot/modules directory.

Copied over the FreeBSDV10 version, and I'm back up and running on 9.10-STABLE.
 

InQuize

Explorer
Joined
May 9, 2015
Messages
81
Having the same problem.
After update to 9.10 had to reassign interface through console. File sharing functions work fine, but jails and plugins don't at all.
When I changed driver binary to one that comes with VMware Tools, everything went back to normal.

There was no such problem while switching between E1000 and VMXNet3 from VMware (at least on 9.3).. This tells me that code in 9.10 does not account for such things. Anyway, just a wild assumption, sadly I have zero free time to test now.

I wonder what issues may come later with future updates if I'll keep 3rd party driver?
Is there a way to manually fix jails while using driver given by iXsystems?
 

toadman

Guru
Joined
Jun 4, 2013
Messages
619
Interesting. I too had to change the interfaces to vmxN. I didn't change the binary, but didn't run into problems. But I'm not running jails either.

Currently the file /boot/modules/vmxnet3.ko is 38280 bytes. I'll have to check the latest vmtools binary.
 

InQuize

Explorer
Joined
May 9, 2015
Messages
81
I didn't change the binary, but didn't run into problems. But I'm not running jails either.

I believe driver itself is fine, but the new iface name or smth about it messes things with jail configs. Even after reassigning iface to vmx0 I was noticing errors about old vmx3f0 while trying to make things work. That's why I made an assumption about UI code.
Everything else seemed to work as expected.

Also, noticed behaviour (with any driver): system boots, jails get DHCP leases fine, I go to Plugins in GUI, page hangs for a min or so, but loads, while logs report about timeout for each jail. After that jails stop getting DHCP; static configuration worked.. After reboot process repeats.

Upd:
Apparently FreeNAS 9.10 ships with VMware FreeBSD 9.0 driver - same size, iface name.
I'm using one from 10.0

Code:
[root@nas /tmp/vmware-tools-distrib/lib/modules/binary/FreeBSD9.0-amd64]# ls -al
total 232  
drwxr-xr-x   2 root  wheel    256 Apr 13 05:25 . 
drwxr-xr-x  18 root  wheel   1024 Apr 13 05:25 .. 
-rw-r--r--   1 root  wheel  25560 Apr 13 05:25 vmblock.ko
-rw-r--r--   1 root  wheel  19624 Apr 13 05:25 vmmemctl.ko
-rw-r--r--   1 root  wheel  18928 Apr 13 05:25 vmxnet.ko
-rw-r--r--   1 root  wheel  38280 Apr 13 05:25 vmxnet3.ko    

[root@nas /tmp/vmware-tools-distrib/lib/modules/binary/FreeBSD10.0-amd64]# ls -al 
total 232 
drwxr-xr-x   2 root  wheel    256 Apr 13 05:25 . 
drwxr-xr-x  18 root  wheel   1024 Apr 13 05:25 .. 
-rw-r--r--   1 root  wheel  26832 Apr 13 05:25 vmblock.ko
-rw-r--r--   1 root  wheel  20096 Apr 13 05:25 vmmemctl.ko
-rw-r--r--   1 root  wheel  19288 Apr 13 05:25 vmxnet.ko
-rw-r--r--   1 root  wheel  37952 Apr 13 05:25 vmxnet3.ko                                                                        
                                       
[root@nas /boot/modules]# ls -al 
total 651 
drwxr-xr-x   2 root  wheel      12 Apr 13 04:30 .  
drwxr-xr-x  10 root  wheel      56 Apr 13 04:31 .. 
-r-xr-xr-x   1 root  wheel  147136 Apr 13 03:12 geom_raid5.ko 
-rw-r--r--   1 root  wheel     248 Apr 13 03:12 linker.hints  
-r-xr-xr-x   1 root  wheel  352464 Apr 13 03:12 vboxdrv.ko 
-r-xr-xr-x   1 root  wheel    9728 Apr 13 03:12 vboxnetadp.ko 
-r-xr-xr-x   1 root  wheel   27128 Apr 13 03:12 vboxnetflt.ko 
-rw-r--r--   1 root  wheel   26832 Apr 13 05:02 vmblock.ko 
-rw-r--r--   1 root  wheel   20096 Apr 13 05:02 vmmemctl.ko
-rw-r--r--   1 root  wheel   19288 Apr 13 05:02 vmxnet.ko 
-rw-r--r--   1 root  wheel   38280 Jan 21 02:59 vmxnet.ko.def  
-rw-r--r--   1 root  wheel   37952 Apr 13 05:02 vmxnet3.ko
 
Last edited:

madmaxed

Cadet
Joined
Jan 20, 2016
Messages
4
I don't think it's actually a VM Ware driver in 9.10. FreeBSD 10 integrated its own VMXNET3 driver, vmx(4) in the Man pages. What happens after the upgrade is that this built in vmx driver gets loaded instead of the VMWare driver. Causes interface to use the new naming convention, but breaks the jails.

I'm not versed enough in how to reconfigure a jail to use the correct interface with the new name. And I really don't want to wipe out my Plex jail and start over.
 

InQuize

Explorer
Joined
May 9, 2015
Messages
81
Same here. My plex has 60 gb of metadata. I just can't afford to wipe it and syncthing, which runs backups. Can't wait for full bhyve support..
 
Last edited:
Status
Not open for further replies.
Top