Differences

This shows you the differences between two versions of the page.

--- rocky_linux_9_migration_notes [2025/06/10 09:28] – juckins
+++ rocky_linux_9_migration_notes [2025/08/11 11:45] (current) – juckins
@@ Line 1: / Line 1: @@
 ==== Rocky Linux 9 Migration Notes ====
-__2024-11-21__
+__2025-06-25__
-Upgrade to Rocky Linux 9.6:
+Upgrade to Rocky Linux 9.6 initially failed on test VM with package errors.
-  dnf remove vlc totem
+  Trying these steps on a test VM:
+  dnf remove vlc totem gstreamer1-plugins-bad-free gstreamer1-plugins-ugly-free
   dnf update
   dnf install vlc totem
+Then reinstall VBox Guest Additions.
+Got message ''/var/log/vboxadd-setup.log to find out what went wrong'' (Building the modules for [current] kernel failed).
+Rebooted and then tried installing kernel-debug-devel but same problem.
+Upgraded host computer's VirtualBox to version 7.1-7.1.10 (was running 7.1.4)
+Now can upgrade from 9.5 to 9.6 on VirtualBox VMs but Xfce logs in for 1 second, a black screens appears, and then the sytem logs out.
+<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 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 {{ :0:virtualbox-vmx-problem.pdf|see PDF}}:
+  # 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__
@@ Line 228: / Line 279: @@
     * Right-click top panel > Add New Items
     * Add CPU Graph, Weather Info
+  * Adjust keyboard repeat delay and repeat speed (Applications > Settings > Keyboard)
+    * Repeat delay: 500
+    * Repeat speed: 65
   * Adjust top and bottom panels
     * Reverse positions
@@ Line 240: / Line 294: @@
 __Post Installation__
+  * Possibly want to adjust the grub timeout from the default of 5 seconds to something like 10 or 12 seconds to be sure the menu appears when the machine boots up.
+    * As root, modify ''/etc/default/grub'' by setting GRUB_TIMEOUT to the desired value.
+    * As root, run ''grub2-mkconfig -o /boot/grub2/grub.cfg''
+    * Reboot to test.
   * In /root/bin on old/new machines, see final_sync_for_new_server.txt
   * As root, use ''alpine'' to check email from crons that indicate any errors or failures