So i finally had some time to make the OS upgrade. Running OS 7.6 for quite some time and had no need to upgrade. Virtual Box 6.1 is running on a windows 10 pro with ) i5-4570T CPU @ 2.90GHz.
The upgrade started , but after booting and option ‘B’ was passed , the machine started spitting a lot of page faults at me and just stopped.
Rechecking the VM settings did not bring me AHA moment yet, so coming here for some advice where to start tinkering.
Who has thoughts ?
HAd some time to research on the issue a bit. intel_pstate is a driver that’s trying to load some hardware speed steppings. Seems there are several CPU/OS combinations that had this before and causing kernel panic.
there are options to disable hwp on the dirver, but dont seem to have a way to do that now.
tried even brand new vdi image and vm, still no change in behavior, which is not weir if considered that the driver issue is same on either image (upgraded os or clean drive)
on this topic, as the upgrade added a boot option and there are 2 now, it cycles to the other option with each boot. So one boot at option A , next boot option B. As option B doesnt work, i have to reset the machine to boot optio A again.
tried Grub2 command lines, but coudl not find the way to remove the option B from the boot options. Anyone can help me removing option B which is not working anyway? I would love my HA instance be rebootable from HA cli, which is not the case currently. (i always have to do a reset machine from virtualbox to make it boot option A)
Any updates on this? I’ve been stuck with the exact same problem for quite a while now, the OS from 7.6 to 8 failed some time ago (can’t recall when I originally tried). I get the same error messages and now am struck in the same boot cycle where I need to do a reset to get to boot option A.
Would appreciate any tips if you were able to upgrade or at least set to always boot option A.
Well, you’ll have to get to command line when system is booted and get some grub tools installed to modify the boot config.
I gave up on that and moved my VM to Synology. No issues at all anymore, stable as an elephant and have additional snapshots to secure the installation.
Don’t know what hardware you have, but you could consider a hardware upgrade so the processor will support it and you are done with the issue too.
I decided to update VirtualBox today to try and address some USB issues I’ve been having, and the update happened to resolve this unsupported CPU issue for me. Went from Virtual Box 6.16 to 6.48.
