SOLVED ESXi Virtualized HW Issue???

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
I am having an issue with a fresh install of 11.2-2.1 that I don't understand. I am running an ESXi 6.7 server (2x L5640 with 48GB ram plus drives) and have two VMs running. The first is my router using pfSense and the second is my NAS using various versions of FreeNAS from the 9.x days to 10.x back to 9.x then to 11.x. Throughout the whole time I have never had an issue setting up FreeNAS and installing the Plex plugin. The VM has 4 CPU cores and 8GB of memory alotted for it. I haven't had time to rebuild the server and get Plex running in the last few months and now that I am attempting to get it to work it will no longer install. I can install FreeNAS without an issue and then when I attempt to install Plex it downloads the 11.2-release jails baseline and then attempts to get an IP for the new Plex install but fails. I have manually setup the IP and was able to get the install to complete but then the Plex server was unable to connect to the internet and so it wouldn't download any of the metadata for my movies. In attempt to just see if it would work I redid the process in VMWare Workstation on my desktop and had no issues. I have attempted to build a new VM in the ESXi environment to see if there was some residual issue leftover but that also resulted in the same issue as before. I don't know what to try next.

This is an error I got trying to start a very basic jail using DHCP.
Error: concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/process.py", line 175, in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 128, in main_worker
res = loop.run_until_complete(coro)
File "/usr/local/lib/python3.6/asyncio/base_events.py", line 468, in run_until_complete
return future.result()
File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 88, in _run
return await self._call(f'{service_name}.{method}', serviceobj, methodobj, params=args, job=job)
File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 81, in _call
return methodobj(*params)
File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 81, in _call
return methodobj(*params)
File "/usr/local/lib/python3.6/site-packages/middlewared/schema.py", line 668, in nf
return f(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/middlewared/plugins/jail.py", line 581, in start
iocage.start()
File "/usr/local/lib/python3.6/site-packages/iocage_lib/iocage.py", line 1663, in start
callback=self.callback
File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_start.py", line 66, in __init__
self.__start_jail__()
File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_start.py", line 459, in __start_jail__
_callback=self.callback)
File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_common.py", line 90, in logit
_callback(content, exception)
File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_common.py", line 64, in callback
raise callback_exception(message)
RuntimeError: + Acquiring DHCP address: FAILED, address received: 0.0.0.0/8

Stopped test due to DHCP failure
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 165, in call_method
result = await self.middleware.call_method(self, message)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1141, in call_method
return await self._call(message['method'], serviceobj, methodobj, params, app=app, io_thread=False)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1078, in _call
return await self._call_worker(serviceobj, name, *args)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1105, in _call_worker
job,
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1036, in run_in_proc
return await self.run_in_executor(self.__procpool, method, *args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1021, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
RuntimeError: + Acquiring DHCP address: FAILED, address received: 0.0.0.0/8

Stopped test due to DHCP failure
 
Last edited:

Meyers

Patron
Joined
Nov 16, 2016
Messages
211
I'll just assume that you know what you're doing in virtualizing FreeNAS.

Is pfSense your DHCP server? This looks like a possible misconfiguration at that level. I would start the research there.
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
Thanks for the response. Yes the pfSense box is my DHCP server. I'm nearly 100% sure that it is operating correctly. The test I did on my desktop computer with FreeNAS in a VM worked fine and the same pfSense router is used for my whole network.

I am getting an additional error this time when I changed the virtual NIC from VMXNET 3 to E1000 I get:
bridge0: error setting interface capabilities on em0 0x1
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
Are you using iocage, if so that might be your culprit as it is trying to creat a bridge using your Freenas NIC.
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
Yes it's using iocage. I'm not entirely sure what that tells me though.
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
Yes it's using iocage. I'm not entirely sure what that tells me though.
Iocage is known to cause issue with network when used by Freenas. It causes loss of communication and other things that would not normally occur if each jail had a dedicated physical NIC.
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
Ok... Is there a work around to fix it or just out of luck? Also any idea why a fresh install in one location works but a second location has errors.
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
VNET seems to be one of the problem. For some reason, when an iocage is loaded last, the web GUI gets reassigned the latter address as far I can tell. resetting network config could help if stuck, but sometime this is not enough.
At least disabling the jails and re-enabling Freenas network config should work.
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
I've never had an issue with the web GUI. I only get an issue with the Plex plugin getting installed. If I manually set the IP the plugin will install and I technically can use it but the hall can't get to the internet so it can't download metadata.
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
Then the gateway IP is not set properly.
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
I've looked all over but can't figure out what is wrong. I even setup a generic jail and poked around trying to setup networking but it just fails. This only seems to happen in my ESXi environment. To note all my other VMs in my virtual stack have no issues.
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
Can Freenas GUI check for updates? does it have internet access?
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
Yes it can check for updates and it is able to download the 11.2-release files to start the plugin install.
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
That was before pluggin was installed, right?
 

svtkobra7

Patron
Joined
Jan 12, 2017
Messages
202
Likely covered / thought of, but doesn't the Port Group assigned to the FreeNAS VM need to contain both the following with VNET?
  • Promiscuous mode = Accept (or "Inherit from vSwitch" provided set there)
  • Forged trasmits = Accept (or "Inherit from vSwitch" provided set there)
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
Likely covered / thought of, but doesn't the Port Group assigned to the FreeNAS VM need to contain both the following with VNET?
  • Promiscuous mode = Accept (or "Inherit from vSwitch" provided set there)
  • Forged trasmits = Accept (or "Inherit from vSwitch" provided set there)

Thanks, I can honestly say that I hadn't thought of or looked into that. It was off and I just turned it on. I will test and report back.
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
That was it.... wow that was incredibly annoying. Thanks for all the help!
 

svtkobra7

Patron
Joined
Jan 12, 2017
Messages
202
That was it.... wow that was incredibly annoying. Thanks for all the help!
But so incredibly satisfying now that solved, eh?
Good for you and more thanks is owed @Apollo honestly - I just get lucky every now and again.
 

bbenz3

Explorer
Joined
Jan 22, 2012
Messages
70
But so incredibly satisfying now that solved, eh?
Good for you and more thanks is owed @Apollo honestly - I just get lucky every now and again.

Oh most definitely!!!!!!!!!!!!!

Yes thanks to Apollo for just asking questions. I know a lot but can often overlook the simplest of details.
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
Oh most definitely!!!!!!!!!!!!!

Yes thanks to Apollo for just asking questions. I know a lot but can often overlook the simplest of details.
Don't we all.
Enjoy.
 
Top