Can't install Rocky Linux 8.6

[DRIESMUL]

I am trying to install Rocky Linux 8.6 on my new laptop.

I tried to run the Automatic installation, but that failed because of a unsupported version 8 (RL is recognized as a RedHat clone)
After manual installation, I tried to boot the Linux guest, but got stuck after a while on attached screen.
[img]D:\AM\Downloads\VBOX_Rocky86_Problem.JPG[/img]

Host: Windows Home 11
VBox: VBox version: 7.0.12-15984
Guest: Rocky Linux 8.6
Laptop Asus Zen Book Core i9 processor, 32 GB Ram, 22 processors
Guest Installed RockyLinux 8.6, with 8 GB of memory and using 14 processors.

After the picture as shown the program is stuck on where it was.

Andries Mulder

OK. As I don not think the picture gets diplayed, I type hereafter the top message:

Warning: Unmaintained hardware is detected e1000:100E:8086 @ 0000:00:00:03.0

[scottgus1]

The forum won't be able to access your computer's D drive. That would be rather a massive security hole if it could.

And IMG tags only work for pictures already uploaded to the forum using the Attachments tab.

Please use the Attachments tab to upload the picture.

[scottgus1]

FWIW the "e1000" is the network card in the VM. The message appears to mean that the OS doesn't have drivers for the network card.

Did you change the default network card picked by Virtualbox's template?

[DRIESMUL]

Thanks for very quick answer:

As a network connection from my guest program is not required, can I install with a disabled network and would that resolve the problem ?

[scottgus1]

OK, thanks. This screenshot seems to indicate that the error happens early. It may be that at that moment the OS's booting environment doesn't have drivers for the network card. It will probably have them when the OS fully boots. I'd ignore the error for now.

If this is all the further the VM boots, it may be a problem that is dealt with here by forum guru fth0:
viewtopic.php?p=545849#p545849

Please try ftho0's posts there.

[DRIESMUL]

>>> If this is all the further the VM boots, it may be a problem that is dealt with here by forum guru fth0:
>>> viewtopic.php?p=545849#p545849

I tried that one without result. The Rocky Linux installation gets stuck at some random point while installing.

My next attempt will be installing VBOX and Rocky Linux on another laptop.

[fth0]

FWIW, the warning related to the e1000 network card driver is an ubiquitous warning that you can ignore.

I'd suggest to try the current VirtualBox 7.0.14. If you then still have the same issue, please provide a (zipped) VBox.log file.

[DRIESMUL]

Dear fth0,
I tried to install VBOX 7.0.14 now and that fails at an earlier stage.

I removed the current VBox (7.0.12) and tried to cleaned up all old leftovers from 7.0.12.
This didn't completely go well, because after I installed 7.0.14, it showed an aborted VM Rocky86.
I removed that one with the regular VBox function to remove that VM.

Installed VBox 7.0.14 without Networking and Without Python
Name: Rocky86
Folder: D:\VBOXDISK
Iso D:\..... Roclky_Linux8.6....Win.exe
Type Linux
Version RedHat 64 bits
Memory 8192 MB
CPU's 14
Disk Size 71,56 GB

Then I started the Virtual Box and it got stuck on the first installation screen. See attached IMG_7215.JPG file.
Whatever I tried, it hung on that screen.

As you asked for, I attach the Vbox.log as a .ZIP file.
When requested, I also have the VBox Hardening log file.

Hope you can tell me what goes wrong.

[fth0]

In the VBox.log file, I haven't seen any clear sign of the error, but I noticed two general things to try:

On a CPU with 14 cores (6P + 8E), providing 14 vCPUs to the VM doesn't leave much processing power for the host OS, Hyper-V and VirtualBox itself. I'd suggest to start with 2 vCPUs.

In the VM configuration, set Display > Screen > Video Memory to 128 MB.

[DRIESMUL]

Dear fth0,
Your advice did it.

Although the machine itself really has 28 cores, and it allowed me to assign the 28 cores completely to the Linux guest,
I have set the number of CPU's now to 4.

The maximum that I could set for Video Display was 128 MB, so I decided to take half, so set it to 64 MB.

Works like a charm.

Only problem left, is that I can change the Shared Folder to be set to the "normal" user and it is now root : vboxsf
But using su, I can access all files in SHARED, so I will fix that later.

[fth0]

Although the machine itself really has 28 cores

Well, Intel clearly disagrees with you on that (see Intel® Core™ i9-13900H Processor), and so do I.

Regarding the Shared Folder, did you add your user to the vboxsf group as the VirtualBox User Manual instructs you to do?