johnjaylward
Dabbler
- Joined
- Oct 23, 2014
- Messages
- 37
Build FreeNAS-9.10-STABLE-201606270534 (dd17351)
Platform Intel(R) Xeon(R) CPU E5-2603 0 @ 1.80GHz
Memory 65474MB
I have 8 jails total. The first 7 are all working fine with VIMAGE enabled. The 8th jail I tried to used VIMAGE as well, but I can't seem to get the networking to work properly on it. When VIMAGE is active, I can't seem to ping the jail from other machines or download large files (like `portsnap fetch extract` or even `pkg upgrade`) from within the jail.
The jail is brand new (I deleted it about 3 times already and recreated it). Once I disabled VIMAGE on the single faulty jail, ping suddenly worked, and now I can run `pkg upgrade` successfully.
Does anyone know why this would be the case? Is there a hard limit in FreeBSD/FreeNAS for the number of jails that can have their own network stack? I don't feel like 8 jails is a lot, I'm sure there are people running more than that without issue.
Is there a good way to debug the issue to see why VIMAGE isn't working?
Platform Intel(R) Xeon(R) CPU E5-2603 0 @ 1.80GHz
Memory 65474MB
I have 8 jails total. The first 7 are all working fine with VIMAGE enabled. The 8th jail I tried to used VIMAGE as well, but I can't seem to get the networking to work properly on it. When VIMAGE is active, I can't seem to ping the jail from other machines or download large files (like `portsnap fetch extract` or even `pkg upgrade`) from within the jail.
The jail is brand new (I deleted it about 3 times already and recreated it). Once I disabled VIMAGE on the single faulty jail, ping suddenly worked, and now I can run `pkg upgrade` successfully.
Does anyone know why this would be the case? Is there a hard limit in FreeBSD/FreeNAS for the number of jails that can have their own network stack? I don't feel like 8 jails is a lot, I'm sure there are people running more than that without issue.
Is there a good way to debug the issue to see why VIMAGE isn't working?