VT-x: (disabled in BIOS) HLT,PAUSE, can this do Freenas 11 with VM?

[leifnel]

Sorry if I have overlooked the obvious, but I have been strugling all night with a Virtualbox'ed machine won't start after a minor upgrade to FreeNAS-9.10.2-U6 (561f0d7a1)

dmesg say

CPU: Intel(R) Xeon(R) CPU E5320 @ 1.86GHz (1862.09-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x6f7 Family=0x6 Model=0xf Stepping=7
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x4e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA>
AMD Features=0x20100800<SYSCALL,NX,LM>
AMD Features2=0x1<LAHF>
VT-x: (disabled in BIOS) HLT,PAUSE
TSC: P-state invariant, performance statistics

When trying to start the virtual machine I get this error (truncated, but I can add more if needed)

Code:

xception Object
(
	[message:protected] => The virtual machine 'test' has terminated unexpectedly during startup with exit code 1
	[string:Exception:private] => 
	[code:protected] => 0
	[file:protected] => /usr/local/www/phpvirtualbox/lib/vboxconnector.php
	[line:protected] => 2382
	[trace:Exception:private] => Array
		(
			[0] => Array
				(
					 => /usr/local/www/phpvirtualbox/lib/vboxconnector.php
					[line] => 928
					[function] => remote_progressGet
					[class] => vboxconnector
					[type] => ->
					[args] => Array
						(
							[0] => Array
								(
									[progress] => 1ce602f982f5ad1e-000000000000003e
									[_persist] => Array
										(
											[vboxHandle] => 1ce602f982f5ad1e-000000000000003c
										)

									[fn] => progressGet
								)

						)

				)

 

[rvassar]

It looks like you have virtualization turned off. Have you tried enabling VT-x in the BIOS?

 

[joeschmuck]

Sorry if I have overlooked the obvious, but I have been strugling all night with a Virtualbox'ed machine won't start after a minor upgrade to FreeNAS-9.10.2-U6 (561f0d7a1)

Are you saying that it ran fine on a previous version of FreeNAS, if yes, what version and did you try to roll back to that version?

 

[leifnel]

The machine is 120km away, so changing something in bios is not really an option right now. If I get near the machine, I might try to change the setting in bios.

Luckily I could go into system -> boot and select a previous version, from septermber 2016, and my virtualbox virtual machine could run again.
At right now my conclusion is "if it ain't broke, don't fix it", and hope that the machine is safe from intruders behind the firewall.