This system does not suppot virtualization

[Lcs_26]

When I try to create a VM truenas throws an error saying that my system does not support virtualization, but the processor is compatible with VT-x with EPT (Xeon E3 1240v3, Intel s1200v3rps board). Could it be related to the gpu? I don't have one installed right now.

 

[elvisimprsntr]

I think some BIOS have a setting to enable/disable VT-x

 

[jgreco]

You need not only for everything to be COMPATIBLE, but also for these features to be ENABLED. You may need to dig into your mainboard manual and BIOS settings, which are the usual fix.

 

[Samuel Tai]

When I try to create a VM truenas throws an error saying that my system does not support virtualization, but the processor is compatible with VT-x with EPT (Xeon E3 1240v3, Intel s1200v3rps board). Could it be related to the gpu? I don't have one installed right now.

According to the S1200V3RPS manual, p. 105, you need to enable the following options in the Advanced->Processor Configuration section of your BIOS:

• Intel(R) Virtualization Technology: Enabled (default is Disabled)
• Intel(R) VT for Direct I/O: Enabled (default is Disabled)
  • Interrupt Remapping: Enabled (default is Enabled)
  • Pass-through DMA Support: Enabled (default is Enabled)

Your CPU, according to Intel ARK, supports VT-x with EPT and VT-d, so once you enable VT-x and VT-d in your BIOS and reboot, you should be able to create VMs in TrueNAS.

 

[Lcs_26]

I can't access the BIOS, as some USB setting whose name I can't remember is disabled, and because of that keyboard won't work before boot. I tried clearing CMOS but the problem persists.

 

[Samuel Tai]

How did you clear CMOS? According to the manual, p. 202-203, you need to access jumper J2K6

and use the procedure in block 10.1:

10.1 BIOS Default Jumper Block

1. This jumper resets BIOS Setup options to their default factory settings.
2. Power down the server and unplug the power cords.
3. Open the chassis and remove the Riser #2 assembly.
4. Move BIOS DFLT jumper from the default (pins 1 and 2) position to the Set BIOS Defaults position (pins 2 and 3).
5. Wait 5 seconds then move the jumper back to the default position of pins 1 and 2.
6. Install riser card assembly.
7. Install Power Cords.
8. Power on system.
   
   Note: BIOS Error Manager should report a 5220 error code (BIOS Settings reset to default settings).

You really should consult the manual yourself, as this is a problem specific to your motherboard, and not a TrueNAS issue.

 

[Lcs_26]

How did you clear CMOS? According to the manual, p. 202-203, you need to access jumper J2K6

View attachment 47832

and use the procedure in block 10.1:

10.1 BIOS Default Jumper Block

1. This jumper resets BIOS Setup options to their default factory settings.
2. Power down the server and unplug the power cords.
3. Open the chassis and remove the Riser #2 assembly.
4. Move BIOS DFLT jumper from the default (pins 1 and 2) position to the Set BIOS Defaults position (pins 2 and 3).
5. Wait 5 seconds then move the jumper back to the default position of pins 1 and 2.
6. Install riser card assembly.
7. Install Power Cords.
8. Power on system.
   
   Note: BIOS Error Manager should report a 5220 error code (BIOS Settings reset to default settings).

You really should consult the manual yourself, as this is a problem specific to your motherboard, and not a TrueNAS issue.

I know. I asked on another forum about the BIOS issue and they told me the same, clear CMOS. It seems like by default the USB setting is disabled, so it is like an infinite cycle, you have to turn on something on the bios in order to access the bios. I'm desperate about this situation. Thx btw

 

[jgreco]

Check to see if there is access through the serial port, via IME, or via BMC. Intel has historically been really good about making their devices accessible in the data center. The jumpers above suggest both IME and BMC are potentially available.

 

[Lcs_26]

Check to see if there is access through the serial port, via IME, or via BMC. Intel has historically been really good about making their devices accessible in the data center. The jumpers above suggest both IME and BMC are potentially available.

Sorry but I get lost here. I have no idea about that, do I need a rs232 to usb adapter?

 

[jgreco]

It looks like there is a serial (DE-9) and VGA (DE-15) port on the back panel, based on the picture above. If you were to connect a terminal up to the serial port, it is possible that when you boot the system, it will mirror the console output to the serial (which is how you can tell if this is a useful option), and if so, it is also listening for keystrokes on the serial port. You can do this by connecting another PC to it using a terminal software package. Try common speeds of 9600, 57600, and 115200 bps, and make sure to disable hardware handshaking.

Historically, this is how some Intel systems such as the ISP1100 were commonly deployed at data centers, and serial management is one of the reasons some server lines still keep a serial port around.

You can also check the manual to see what is available for the IME subsystem (these usually need to be configured) and the BMC (more likely to auto-configure itself via DHCP), and whether you can get console access through these.

At the end of the day, I would be stunned if Intel didn't offer several ways for you to get into the thing.

 

[Lcs_26]

Ok, I know nothing about this but I think I get the idea. Basically I connect with a usb to rs232 adapter with another PC, I boot the server and I try to access bios using the secondary PC's keyboard and a terminal software. Is that correct? What terminal software could I use? I have never used one. I heard about putty in the past but I don't know if it's what you are talking about. Thx btw

 

[jgreco]

Some of us learned UNIX on serial terminals. And if it helps, you can bear in mind that the UNIX CLI is at its heart a serial terminal session, usually these days just emulated, whether on a virtual terminal or a SSH connection or whatever.

PuTTY is usable, it's not great but it isn't a catastrophe. It's really an SSH client, and the serial is an add-on afterthought.

The biggest shortcoming is that it doesn't show you the list of available COM ports, so you need to go into Device Manager, expand COM & LPT Ports, and make sure you give PuTTY the correct device name. When you open PuTTY configuration, select "Connection type: Serial" and use that COM port. I believe it defaults to no hardware flow control, so that probably helps.

 

[ChrisRJ]

I have used Tera Term as terminal software in the best (i.e. 20+ years ago) and at least then was quite happy with it.

 

[Arwen]

Reading the system board's manual, it indicates the BIOS initializes the USB buses. So, having USB keyboards disabled by default sounds wrong. In fact, a quick glance at the manual makes no indications that USB is disabled by default. Quite the opposite, it references places where the USB ports available for keyboards, mice and block storage.

Of course, it can be hard to enter the BIOS if you either don't know the correct key to use. Or, you have a limited time to enter the key.

This system board uses the following:

9.1 HotKeys Supported During POST

Certain “HotKeys” are recognized during POST. A HotKey is a key or a key combination that is recognized as an unprompted command input, that is, the operator is not prompted to press the HotKey and typically the HotKey will be recognized even while other processing is in progress.

The Intel®Server Board S1200V3RP Family BIOS recognizes a number of HotKeys during POST. After the OS is booted, HotKeys are the responsibility of the OS and the OS defines its own set of recognized HotKeys.

Following are the POST HotKeys, with their functions:

Table 54. POST HotKeys Recognized​

HotKey Combination	Function
<F2>	Enter Setup
<F6>	Pop up BIOS Boot Menu
<F12>	Network boot
<Esc>	Switch from Logo Screen to Diagnostic
<Pause>	Stop POST temporarily