ISOs not booting to CLI in VBox

[wilsonephillips]

OpenMandriva version:ABF #4704 and #4705

Describe the bug: GRUB2 > Advanced Options > Console Mode takes you to SDDM and not CLI

Steps to reproduce:

Observed behavior: Boots to SDDM

Expected behavior: Boot to CLI

Additional comment: Happens in VBox. Works fine booting USB.

Logs and screenshots if relevant

[wilsonephillips]

Not booting to Recovery Mode in VBox
Not booting to Failsafe Mode in VBox

Seems be one issue causing all of these problems. UEFI/BIOS related.

[rudiservo]

My guess is the CLI boot on vbox is mostly due to graphics driver issue, adding failsafe will boot
From what I read this is a know issue in other distros maybe after kernel 6.5.

The VM crashed or failed to boot even with failsafe in normal mode and all modes in troubleshooting with VboxVGA and VboxSVGA.

This is the start of crash log of Vbox on CLI without failsafe

00:00:14.866204 !!R0-Assertion Failed!!
00:00:14.866205 Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf && hNativeSelf != (~(RTNATIVETHREAD)0)
00:00:14.866205 Location  : /build/virtualbox/src/VirtualBox-7.2.16/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(827) int PDMCritSectLeave(PVMCC, PPDMCRITSECT)
00:00:14.866220 ffffd10221c32040 <R3_STRING>: ffffffffffffffff != 00007f55bc5ff6c0; cLockers=-1 cNestings=1
00:00:14.866229 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:14.866235 Console: Machine state changed to 'Stuck'
00:00:14.866423 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:14.866423 !!
00:00:14.866423 !!         VCPU1: Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)
00:00:14.866426 !!
00:00:14.866428 !!R0-Assertion Failed!!
00:00:14.866428 Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf && hNativeSelf != (~(RTNATIVETHREAD)0)
00:00:14.866428 Location  : /build/virtualbox/src/VirtualBox-7.2.16/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(827) int PDMCritSectLeave(PVMCC, PPDMCRITSECT)
00:00:14.866429 ffffd10221c32040 <R3_STRING>: ffffffffffffffff != 00007f55bc5ff6c0; cLockers=-1 cNestings=1
00:00:14.866429 !!
00:00:14.866429 !! AssertJmpBuf:
00:00:14.866430 !!
00:00:14.866430 UnwindSp=ffffd1020c1f36e0 UnwindRetSp=ffffd1020c1f3708 UnwindBp=ffffd1020c1f3710 UnwindPc=ffffd1020f593d29
00:00:14.866432 UnwindRetPcValue=ffffffffc05a1c77 UnwindRetPcLocation=ffffd1020c1f3d68
00:00:14.866433 uOperation=0000000000000000
00:00:14.866434 rax=volatile         rbx=ffffd10221c32040 rcx=volatile         rdx=volatile
00:00:14.866434 rsi=volatile         rdi=volatile          r8=volatile          r9=volatile
00:00:14.866434 r10=volatile         r11=volatile         r12=ffffd10221b19001 r13=00007f55bc5ff6c0
00:00:14.866435 r14=ffff8a508dc08000 r15=ffffd10221c64d68 rfl=00000286
00:00:14.866435 rip=ffffd1020f3b223e rsp=ffffd1020c1f3708 rbp=ffffd1020c1f3730
00:00:14.868571 !!
00:00:14.868571 !! Call Stack:
00:00:14.868571 !!
00:00:14.868572 RBP              Ret RBP          Ret RIP          RIP              Symbol [line]
00:00:14.868573 ffffd1020c1f3710 ffffd1020c1f3730 ffffd1020f3b223e ffffd1020f593d29 vmmr0.r0!VMGetHardResetCount+339
00:00:14.868574 ffffd1020c1f3730 ffffd1020c1f37a0 ffffd1020f559d23 ffffd1020f3b223e vmmr0.r0!RTAssertShouldPanic+6e
00:00:14.868576      rbp=ffffd1020c1f37a0
00:00:14.868577 ffffd1020c1f37a0 ffffd1020c1f37c0 ffffd1020f579d0b ffffd1020f559d23 vmmr0.r0!PDMCritSectLeave+253
00:00:14.868578      rbx=ffffd10221b19000
00:00:14.868578      rbp=ffffd1020c1f37c0
00:00:14.868579      r12=0000000000000000
00:00:14.868579      r13=ffffd10221b19000
00:00:14.868579 ffffd1020c1f37c0 ffffd1020c1f3810 ffffd1020f582852 ffffd1020f579d0b vmmr0.r0!pgmR0BthAMD64AMD64MapCR3+2cb
00:00:14.868580      rbx=0000000000000000
00:00:14.868581      rbp=ffffd1020c1f3810
00:00:14.868581      r12=ffffd1020c1f3858
00:00:14.868581 ffffd1020c1f3810 ffffd1020c1f3880 ffffd1020f56fba6 ffffd1020f582852 vmmr0.r0!PGMPhysReleasePageMappingLock+1142
00:00:14.868582      rbx=0000000000000021
00:00:14.868582      rbp=ffffd1020c1f3880
00:00:14.868583      r12=ffffd1020c1f3900
00:00:14.868583      r13=ffffd10221ccd000
00:00:14.868583      r14=0000000000000010
00:00:14.868583 ffffd1020c1f3880 ffffd1020c1f3790 ffffd1020f410a2b ffffd1020f56fba6 vmmr0.r0!_Z26pgmR0GstAMD64QueryPageFastP6GVMCPUyjP13PGMPTWALKFAST+2f6
00:00:14.868584      rbp=00007f092e9868a0
00:00:14.868585 ffffd1020c1f3790 ffffd10221b19000 0000000000000286 ffffd1020f410a2b vmmr0.r0!HMCanExecuteGuest+af9b
00:00:14.868586      rbx=ffffd10221b19000
00:00:14.868586      rbp=ffffd10221b19000
00:00:14.868586      r12=0000000000000000
00:00:14.868586      r13=ffffd10221b19000
00:00:14.868587      r14=ffffffffa9504110
00:00:14.868587 ffffd10221b19000 0000000000000000 0000000000000000 0000000000000286
00:00:14.868588 0000000000000000 0000000000000000 0000000000000000 0000000000000000
00:00:14.868588 0000000000000000 0000000000000000 0000000000000000 0000000000000000
00:00:14.868589 !!
00:00:14.868589 !! Addresses on the stack (iAddr=0x0, iEnd=0x123)
00:00:14.868590 !!

[rudiservo]

It boots with failsafe graphics.

I made a PR that adds one more entry.
OpenMandrivaAssociation/omdv-build-iso#98

[benbullard79]

IMO Recovery Mode and Console Mode are not both needed. Console Mode works except in some instances in VBox. Recovery Mode has been broken for a long time, not sure how long. So Recovery Mode should be remove from the grub2 menu.

[rudiservo]

IMO Recovery Mode and Console Mode are not both needed. Console Mode works except in some instances in VBox. Recovery Mode has been broken for a long time, not sure how long. So Recovery Mode should be remove from the grub2 menu.

I can change the PR or try and fix recovery mode but that should probably be another ticket and maybe it's own conversation.

Right now what I need to know is

1. either console is added with failsafe
2. new console mode failsafe (current PR)
3. change nothing at all and add somewhere in documentation.

[rudiservo]

@benbullard79 or @berolinux can I get decision on this one?