Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision |
rocky_linux_9_migration_notes [2025/06/25 18:35] – juckins | rocky_linux_9_migration_notes [2025/06/25 18:54] (current) – juckins |
---|
<color #ed1c24>The fix is to choose a different window manager on the main login screen (upper right, choose "GNOME Classic on Wayland"). After logging in successfully, log out and then go back to the main screen and choose the "Xfce Session".</color> | <color #ed1c24>The fix is to choose a different window manager on the main login screen (upper right, choose "GNOME Classic on Wayland"). After logging in successfully, log out and then go back to the main screen and choose the "Xfce Session".</color> |
| |
For my non-virtual, primary Rocky Linux 9 machine the upgrade from 9.5 to 9.6 worked without issue. | For my non-virtual, primary Rocky Linux 9 machine the upgrade from 9.5 to 9.6 worked without issue but upon reboot, I got the following error: |
| |
| ''VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE).'' |
| |
| Using a [[https://www.google.com/search?q=VirtualBox+can%27t+operate+in+VMX+root+mode.+Please+disable+the+KVM+kernel+extension%2C+recompile+your+kernel+and+reboot+(VERR_VMX_IN_VMX_ROOT_MODE).&oq=VirtualBox+can%27t+operate+in+VMX+root+mode.+Please+disable+the+KVM+kernel+extension%2C+recompile+your+kernel+and+reboot+(VERR_VMX_IN_VMX_ROOT_MODE).&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIHCAEQIRiPAjIHCAIQIRiPAtIBCTYzNTVqMGoxNagCCLACAfEFCfv4GIhBFt3xBQn7-BiIQRbd&sourceid=chrome&ie=UTF-8|Google Search]], the temporary fix was to do the following: |
| |
| # lsmod | grep kvm |
| |
| Verified the following output: |
| |
| kvm_intel 446464 0 |
| kvm 1404928 1 kvm_intel |
| |
| Disabled the KVM temporarily: |
| |
| # modprobe -r kvm_intel |
| |
| Verified nothing was returned with the following command: |
| |
| # lsmod | grep kvm |
| |
| Was then able to start up the VMs using the VirtualBox GUI successfully. |
| |
| Need to reboot machine and see if fix stays. Otherwise, the permanent fix is the following: |
| |
| Create a file named kvm-blacklist.conf in /etc/modprobe.d/ |
| |
| Add the blacklist entry: Add the appropriate line to the file: |
| |
| blacklist kvm_intel |
| |
| -or- |
| |
| blacklist kvm_amd |
| |
| Reboot to apply the changes. |
| |
__2024-11-25__ | __2024-11-25__ |