NS8 on Rocky on VirtualBox virtualization error

[michelandre (Michel-André)]

Hi @mrmarkuz

With VirtualBox, I found the major error:

  Exécution du scriptlet: sssd-client-2.8.2-2.el9.x86_64                              270/974 
Fatal glibc error: CPU does not support x86-64-v2
attention : %post(sssd-client-2.8.2-2.el9.x86_64) scriptlet échoué, état de sortie 127

Error in POSTIN scriptlet in rpm package sssd-client
  Mise à jour de        : sudo-1.9.5p2-9.el9.x86_64                                   271/974 
  Exécution du scriptlet: sudo-1.9.5p2-9.el9.x86_64                                   271/974 
Fatal glibc error: CPU does not support x86-64-v2
attention : %post(sudo-1.9.5p2-9.el9.x86_64) scriptlet échoué, état de sortie 127

Fatal glibc error: CPU does not support x86-64-v2

What can I do with Virtualbox except switching to Proxmox???

Michel-André

[mrmarkuz (Markus Neuberger)]

You could try enabling “nested paging” in “System - Acceleration”, see also virtualbox.org • View topic - AVX and VirtualBox v6.1.18 r142142

[michelandre (Michel-André)]

Hi @mrmarkuz

@mrmarkuz

“nested paging” in “System - Acceleration”

It is already enabled.

Maybe as with Proxmox:

Michel-André

[michelandre (Michel-André)]

Hi @mrmarkuz

I just tried “None” and doesn’t work.

Michel-André

[mrmarkuz (Markus Neuberger)]

@michelandre I moved it to a new thread.

I have a much more options available, I’m using phpVirtualBox 6.1-0:

Does your virtualbox host support virtualization and is it enabled in BIOS? Check out https://www.cyberciti.biz/faq/linux-xen-vmware-kvm-intel-vt-amd-v-support/

[michelandre (Michel-André)]

Hi @mrmarkuz

VirtualBox Version 6.1.38_Ubuntu r153438

$ grep --color vmx /proc/cpuinfo
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm pti tpr_shadow dtherm
vmx flags       : tsc_offset vtpr
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm pti tpr_shadow dtherm
vmx flags       : tsc_offset vtpr
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm pti tpr_shadow dtherm
vmx flags       : tsc_offset vtpr
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm pti tpr_shadow dtherm
vmx flags       : tsc_offset vtpr
$

I also have VirtualBox 7.0.8

On both Ubuntu and on Win-8.1, I have only one option to enable.

Michel-André

[mrmarkuz (Markus Neuberger)]

Which host processor is used?

Is virtualbox installed bare-metal or in a VM?

Did you install from ISO or image?

@michelandre

VirtualBox Version 6.1.38_Ubuntu r153438

I use Virtual Box 6.1.36 (152435) on xigmanas (FreeBSD) and Virtual Box 7.0.6_SUSE r155176 (both bare-metal) and got Alma (should be no big difference to Rocky) working but I’m going to test Rocky…

EDIT:

In Virtual Box 7.0.6_SUSE r155176 I also have just one option.

Processor tab:

[michelandre (Michel-André)]

Hi @mrmarkuz

Not on bare metal, installed VirtualBox on Ubuntu-22.04 LTS

PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"

# uname -a
Linux fred-kubuntu01-HP-xw6400-Workstation 5.15.0-72-generic #79-Ubuntu SMP Wed Apr 19 08:22:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
#

# /lib64/ld-linux-x86-64.so.2 --help
...
Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3
  x86-64-v2
...

I installed from ISO minimum and DVD

@mrmarkuz

In Virtual Box 7.0.6_SUSE r155176 I also have just one option

Options ar the same as mine.

Michel-André

EDIT: You might need minimum 2 processors. On some forum, some have error with just one CPU.

[mrmarkuz (Markus Neuberger)]

@michelandre

You might need minimum 2 processors. On some forum, some have error with just one CPU.

Good catch, did you try it?

Maybe try to import the vdi (in case there’s an issue regarding ISO/DVD installs):

NS8B1 first test

There were similar issues with the Debian image in VMWare, please try a vmdk from here. EDIT: I tested converting the qcow image to vdi and it worked. I used a bridged virtual network adapter and could reach the cluster-admin page. If needed you can download the working vdi.

[michelandre (Michel-André)]

Hi @mrmarkuz

I tried with 1, 2, and 4.
On installation of Rocky-9.2, all same error: kernel panic.

I copied a working installation of Rocky-9.2 from Win-8.1 to Ubuntu 22.04 LTS and it gave also “kernel panic”

Michel-André

[mrmarkuz (Markus Neuberger)]

@michelandre

I copied a working installation of Rocky-9.2 from Win-8.1 on Ubuntu 22.04 LTS and it gave also “kernel panic”

OK, so it works in virtualbox on Windows but doesn’t work in virtualbox in Ubuntu? So it’s an Ubuntu issue? Sorry for dumb questions, just to clarify…

[michelandre (Michel-André)]

Hi @mrmarkuz

I think it is not just on Ubuntu, I check many forum on different OS and many complained about “kernel panic” with VB or x86-64-v2.
Even with Proxmox, you have to set a parameter to “NONE”, as you wrote somewhere, to have Rocky-9.2 to work.

I installed Rocky-8.8 on both Ubuntu and it works.

I found a link to upgrade Rocky-8.8 to 9.2 and after reboot => kernal panic.
While upgrading:
Fatal glibc error: CPU does not support x86-64-v2

As I wrote before with:

# /lib64/ld-linux-x86-64.so.2 --help
...
Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3
  x86-64-v2
...

Then, I think the CPU should support x86-64-v2.

Michel-André

[mrmarkuz (Markus Neuberger)]

I found a lot of forum threads but no solution, maybe this works?

I assume you chose Red Hat 9 (64-Bit) in the General/Basic settings:

[michelandre (Michel-André)]

Hi @mrmarkuz

I tried quite a few of them: Linux 2.4, Linux 2.6/3.x/4.x, Red Hat, and Other.

@mrmarkuz

I found a lot of forum threads but no solution, maybe this works?

SSE4 was announced on September 27, 2006 => Then, I have some doubts. But I have to try…

Michel-André

[mrmarkuz (Markus Neuberger)]

@michelandre

Then, I have some doubts. But I have to try…

I’m having doubts too but it was the only “solution” I found…

[michelandre (Michel-André)]

Use SSE4 to have other instructions like CPUID =>

This instruction was introduced by Intel in 1993 with the launch of the Pentium and SL-enhanced 486 processors.[1]

This reinforces my doubts !

Michel-André

[mrmarkuz (Markus Neuberger)]

You’re right, as said I have doubts too.
But the solution could be in changing the CPU to host-passthrough or something else like in Proxmox but I don’t know how

I’m going to test Rocky in vbox tomorrow…

[michelandre (Michel-André)]

Hi @mrmarkuz

After reading this link:

RHEL9 Raises Base Target For x86_64 CPUs Plus Possible Optimized Libraries...

Now, I am a bit confused. Might be an interesting test to add SSE4 but where is the file to modify ?

Thank you so much for your help,

Michel-André

EDIT:
I found the command to do both 4.1.0 & 4.2.0:

How to change the CPU instruction set which VirtualBox emulated for guest OS, like disabling SSE4.2 instruction set?

VBoxManage setextradata VM-name VBoxInternal/CPUM/IsaExts/SSE4.1 0

VBoxManage setextradata VM-name VBoxInternal/CPUM/IsaExts/SSE4.2 0

I can not find the VM-name with the command:

VBoxManage list vms

The output is blank…

Michel-André

[michelandre (Michel-André)]

Hi @mrmarkuz

I managed to install both 4.1.0 & 4.2.0

# cd /media/fred-kubuntu01/VIRTUALBOX/Rocky92/

# pwd
/media/fred-kubuntu01/VIRTUALBOX/Rocky92

# ls -als
total 104
 4 drwx------  3 fred-kubuntu01 fred-kubuntu01    4096 mai   26 18:48 .
 4 drwxrwxrwx 11 root           root              4096 mai   26 18:23 ..
 4 drwx------  2 fred-kubuntu01 fred-kubuntu01    4096 mai   26 18:47 Logs
 4 -rw-------  1 fred-kubuntu01 fred-kubuntu01    4003 mai   26 18:48 Rocky92.vbox
 4 -rw-------  1 fred-kubuntu01 fred-kubuntu01    4003 mai   26 18:48 Rocky92.vbox-prev
84 -rw-------  1 fred-kubuntu01 fred-kubuntu01 2097152 mai   26 18:48 Rocky92.vdi

# VBoxManage registervm /media/fred-kubuntu01/VIRTUALBOX/Rocky92/Rocky92.vbox

#  VBoxManage list vms
"Rocky92" {4f573c5e-0269-45c7-b551-f80111329e5a}

# VBoxManage setextradata Rocky92 VBoxInternal/CPUM/IsaExts/SSE4.1 0

# VBoxManage setextradata Rocky92 VBoxInternal/CPUM/IsaExts/SSE4.2 0

Still kernel panic.

I have no more ideas…

Michel-André

EDIT:
Setting those to 0 disables the parameters.
I tried 1 and still “kernel panic”

Michel-André

[mrmarkuz (Markus Neuberger)]

@mrmarkuz

I’m going to test Rocky in vbox tomorrow…

I couldn’t reproduce it.

Rocky 9.2 is working here with Virtualbox on:

• xigmanas/FreeBSD 12, Intel Celeron G1610T
• OpenSUSE 15.4 Leap, Intel Core i3-8100
• Ubuntu 22.04.2, Intel Core i7-8750H

I just created a new virtual machine, respected the minimum requirements, set network to bridged, kept the hard disk on the SATA (IDE should work too) controller and installed from IDE ISO, setup network, installed NS8 and created the cluster.