Unable to start VM after Truenas Upgrade

Pushead

Cadet
Joined
Oct 19, 2021
Messages
2
Hey TrueNas Users,

I just upgraded my Freenas installation to Truenas and face some issues.
One of them is that a single VM refuses to start.


Fehler: Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 138, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1224, in _call
return await self.run_in_executor(prepared_call.executor, methodobj, *prepared_call.args)
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1128, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 979, in nf
return f(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/vm.py", line 1599, in start
self.vms[vm['name']].start(vm_data=vm)
File "/usr/local/lib/python3.9/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.76:5900 device(s) are not available.


The ip referenced is an old IP the Freenas system used until 9 months ago. With the new IP the VM was running fine until the system got updated.
Do you have an idea how I can fix this issue?

Best regards,
Pushead
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Delete and re-add the VNC device for this VM.
 

Pushead

Cadet
Joined
Oct 19, 2021
Messages
2
Hello Samuel. Thanks that helped me alot. Seems like the Bind was empty. Adding 0.0.0.0 solved the problem.
Bind.png
 
Top