Can the CPU instruction RDTSCP be available in iohyve for Debian?

[karlinhigh]

Here's what I have:
Lenovo ThinkServer TS140, Intel Core i3-4130, 16 GB RAM.
FreeNAS 9.10.2-U4
iohyve 0.7.7
Debian 8.8 32-bit

...and a piece of software that says the RDTSCP cpu instruction is not supported by my hardware and repeatedly crashes. I tried to check why this is happening, and logged into FreeNAS via SSH.

Code:

freenas~# cpuid | grep -i rdtscp
RDTSCP	RDTSCP and IA32_TSC_AUX are available

Then I logged in to the Debian iohyve:

Code:

debian-bhyve:~$ cpuid | grep -i rdtscp
RDTSCP = false
RDTSCP = false
RDTSCP = false
RDTSCP = false

Also under Debian iohyve, if I run
cat /proc/cpuinfo
...I get a long list of cpu features, including lots of flags values. One of those is "tsc."

Any ideas? Would further information be helpful?

 

[dlavigne]

Also under Debian iohyve, if I run
cat /proc/cpuinfo
...I get a long list of cpu features, including lots of flags values. One of those is "tsc."

Just to clarify, that command works on Debian when it is installed to hardware but not when it is installed to iohyve?

 

[karlinhigh]

On the same machine, I have a standard jail running VirtualBox. I had been using the plugin-jail for VirtualBox, but it got broken in upgrades, and at that point I set it up VirtualBox in a standard jail. A Debian VM there says the CPU instruction is available.

Code:

debian-vbox:~$ cpuid | grep -i rdtscp
RDTSCP = true

I still haven't found anything in research. It does look like VirtualBox and iohyve might not play nice together, and I should use one or the other. If I can get iohyve to do everything VirtualBox can, I'd rather use that now.

 

[dlavigne]

Interesting. It might be worthwhile creating a bug report at bugs.freenas.org. If you do, post the issue number here.