Upgrade FreeNAS 11.3 -> TrueNAS12: VM does not start

[darthvader42]

The upgrade from FreeNAS 11.3 to TrueNAS12 worked flawlessly except one thing: I do have an Ubuntu VM which does not start any more.
Upon a manual start via the UI I do get this error message:

```
Error: Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 137, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1206, in _call
return await self.run_in_executor(prepared_call.executor, methodobj, *prepared_call.args)
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1110, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 977, in nf
return f(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/vm.py", line 1595, in start
self.vms[vm['name']].start(vm_data=vm)
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/vm.py", line 173, in start
raise CallError(
middlewared.service_exception.CallError: [EFAULT] VM will not start as VNC Device: 192.168.178.3:6143 device(s) are not available.
```

Any idea what went wrong and how this can be fixed?

 

[Samuel Tai]

Did your installation change IPs? The exception indicates the VNC device couldn't bind to 192.168.178.3 to offer port 6143.

 

[darthvader42]

IP addresses didn't change. The Freenas/truenas box gets 192.168.178.24 statically assigned by the router. Long time ago (>1year) I did use indeed 192.168.178.3 for freenas.
I've changed the VNC device's `bind` setting to `0.0.0.0` - this one was empty before. After that change the VM starts up nicely.
I suspect the culprit was some hidden leftover from a very old configuration manifestated in `bind` being empty.
Thanks for your help. I'll mark this as solved.

 

[Gaspetaahl]

I had exactly the same issue, also the bind adress was empty and changing it to 0.0.0.0 fixed the problem. This happened after I updatet from 12.-U1.1 to 12.U2.0
maybe this is a bug or at least an uncoveniet migration that could be addressed in a further update?

 

[peterwyss]

I have the same problem, but I can't find a setting for bind.