If you want us to take a look (regarding VirtualBox 6.1.36), create your own topic, reproduce and describe your problem and provide a zip file containing the VBoxHardening.log and VBox.log files.Alvaro Palma wrote:Tested using 6.1.36. Still failing if Hyper-V is enabled
Has anyone successfully installed RHEL 9 on Virtualbox?
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Has anyone successfully installed RHEL 9 on Virtualbox?
-
- Posts: 12
- Joined: 20. Mar 2021, 00:26
Re: Has anyone successfully installed RHEL 9 on Virtualbox?
Tested using 6.1.36, this time with Hyper-V disabled, still not working. In the other hand, AlmaLinux 8 works fine in the same machine, regardless if Hyper-V is enabled or disabled.
I'll create the issue as requested.
I'll create the issue as requested.
-
- Posts: 38
- Joined: 12. Feb 2021, 00:02
Re: Has anyone successfully installed RHEL 9 on Virtualbox?
Even after turning off the hyper-v in the Windows 11, the RHEL 9 still will panic in the VirtualBox.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Has anyone successfully installed RHEL 9 on Virtualbox?
There's many folks who don't actually successfully do this after they think they've done it. If the green turtle is still in the VM's Status Bar, then underlying Hyper-V is still enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).Fujitsu_user wrote:Even after turning off the hyper-v in the Windows 11
Fujitsu_user, please start a new topic if you want to pursue this further.
Re: Has anyone successfully installed RHEL 9 on Virtualbox?
I installed successfully on 6.1.34 (Windows 10, no HyperV) and am able to boot the VM on an Ubuntu 20.04 host running 6.1.36.
Creating a clone fails with the LVM unable to find the volumes on the /dev/sda2 partition.
Apparently cloning the diskchanges an LVM ID somewhere. I had to use this URL to get the VM "back":
https://portal.nutanix.com/page/documen ... 000LaGrSAK
Creating a clone fails with the LVM unable to find the volumes on the /dev/sda2 partition.
Apparently cloning the diskchanges an LVM ID somewhere. I had to use this URL to get the VM "back":
https://portal.nutanix.com/page/documen ... 000LaGrSAK