VM starts and crashes when I login with VNC

[rares_p]

Hello guys,

I have FreeNAS-11.1-U2. I just did all the updates right now.
I tried to make a new VM, assigned a Zvol for it, added the boot image, so all is good.
I strat it and it strats.
But when I connect to it with the VNC, it crashes instantly.
I have created and deleted the VM so many times to no avail.

I have 16GB of RAM and Intel(R) Xeon(R) CPU W3520 @ 2.67GHz CPU.

Please point me in the right direction. How can I at least debug it? See the errors?

Thanks in advance,
Rares

 

[dlavigne]

What is the hardware on the system?

Do you have any other VMs or jails running? If so, how many?

Are there any errors in /var/log/messages related to the crash?

 

[rares_p]

This is a copy and paste from FreeNAS System page:

Build FreeNAS-11.1-U2

Platform Intel(R) Xeon(R) CPU W3520 @ 2.67GHz

Memory 16329MB

System Time Tue, 27 Feb 2018 10:21:47 +0200

Uptime 10:21AM up 17:21, 1 user

Load Average 0.74, 0.78, 0.80

This is the only one VM that I have and there is only one more jail for Syncthing.
I gave 2GB of RAM and 1 Core to the VM.

/var/log/messages doesn't say anything related:

I did a tail -f /var/log/messages and when I start the VM I just get
kernel: tap0: link state changed to UP
and when I connect with the VNC I instantly get
kernel: tap0: link state changed to DOWN

 

[digity]

Hello guys,

I have FreeNAS-11.1-U2. I just did all the updates right now.
I tried to make a new VM, assigned a Zvol for it, added the boot image, so all is good.
I strat it and it strats.
But when I connect to it with the VNC, it crashes instantly.
I have created and deleted the VM so many times to no avail.

I have 16GB of RAM and Intel(R) Xeon(R) CPU W3520 @ 2.67GHz CPU.

Please point me in the right direction. How can I at least debug it? See the errors?

Thanks in advance,
Rares

I ran into this issue before; you have to have a Westmere (XEON X5600 series) or higher/newer CPU for VMs in FreeNAS to run successfully (https://forums.freenas.org/index.php?threads/cant-add-more-than-cpu-to-vm.55397/).

 

[rares_p]

Thanks for the reply.
However, what's puzzling to me is the fact that the VM starts and even if I leave it for a while, it stays on.
Only when I connect with VNC it crashes instantly.
It may be that the CPU does not support this kind of stuff, yet, why does it start in the first place?

 

[digity]

Thanks for the reply.
However, what's puzzling to me is the fact that the VM starts and even if I leave it for a while, it stays on.
Only when I connect with VNC it crashes instantly.
It may be that the CPU does not support this kind of stuff, yet, why does it start in the first place?

Either it never really runs, it just appears to be running and VNCing in reveals this and updates it's status (to not running/stopped) or the VM is running but hanging or something with VNC forces a real check of the unrestricted guest access instruction set in the CPU and stops immediately when it sees the CPU doesn't actually support it. I forget which.

Sent from my SM-G955U using Tapatalk