Virtualbox aborting on resume

[gkamathh]

Windows 10 2004 19041.388 Virtualbox 6.1.12

This happens in three ways 1) save-state -> resume vm 2) running -> pause -> resume vm 3) start as hidden -> show -> close-window and continue running in the background

a popup box appears VBoxHeadless.exe - Application Error The instruction at 0x... referenced memory at 0x0000..000C. The memory could no be read Click OK to terminate the program

00:00:25.871086 VMMDev: Guest Additions capability report: (0x0 -> 0x4) seamless: no, hostWindowMapping: no, graphics: yes 00:00:26.335303 VMMDev: Guest Log: 22:32:02.516677 main VBoxService 6.1.10_Fedora r138449 (verbosity: 0) linux.amd64 (Jun 8 2020 00:00:00) release log 00:00:26.335670 VMMDev: Guest Log: 22:32:22:32:02.517571 main OS Product: Linux 00:00:26.337367 VMMDev: Guest Log: 22:32:02.519165 main OS Release: 5.7.8-200.fc32.x86_64 00:00:26.338250 VMMDev: Guest Log: 22:32:02.519954 main OS Version: #1 SMP Thu Jul 9 14:34:51 UTC 2020 00:00:26.339013 VMMDev: Guest Log: 22:32:02.520828 main Executable: /usr/sbin/VBoxService 00:00:26.339255 VMMDev: Guest Log: 22:32:02.520828 main Process ID: 421 00:00:26.342033 VMMDev: Guest Log: 22:32:02.520829 main Pa22:32:02.523773 main 6.1.10_Fedora r138449 started. Verbose level = 0 00:00:26.344597 VMMDev: Guest Log: 22:32:02.526267 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1) 00:00:26.345107 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000 00:00:37.138464 IEM: rdmsr(0x122) -> #GP(0) 00:49:57.970214 Changing the VM state from 'RUNNING' to 'SUSPENDING' 00:49:57.970344 PDMR3Suspend: after 0 ms, 1 loops: 1 async tasks - virtio-scsi/0 00:49:59.069354 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0781) created successfully 00:49:59.426309 AIOMgr: Async flushes not supported 00:49:59.505913 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0781) created successfully 00:49:59.541990 PDMR3Suspend: 1 571 708 931 ns run time 00:49:59.542009 Changing the VM state from 'SUSPENDING' to 'SUSPENDED' 00:49:59.542021 Console: Machine state changed to 'Paused' 00:50:04.490337 Changing the VM state from 'SUSPENDED' to 'RESUMING' 00:50:04.490657 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0723) created successfully 00:50:04.495647 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0723) created successfully 00:50:04.500963 Changing the VM state from 'RESUMING' to 'RUNNING' 00:50:04.500977 Console: Machine state changed to 'Running' 00:50:04.501069 00:50:04.501070 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002f58!!! 00:50:04.501075 00:50:04.501075 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023 00:50:04.501079 ExceptionInformation[0]=0000000000000000 00:50:04.501082 ExceptionInformation[1]=000000000000000c 00:50:04.501085 00:50:04.501085 cs:rip=0033:00007ffa18bb0023 00:50:04.501089 ss:rsp=002b:0000000008f4d7f0 rbp=0000000008f4d8f0 00:50:04.501093 rax=00000000000022e0 rcx=00000000064b0000 rdx=00000000064b3340 rbx=00000000064b0000 00:50:04.501096 rsi=00000000064b3340 rdi=0000000000000000 rsp=0000000008f4d7f0 rbp=0000000008f4d8f0 00:50:04.501102 r8 =00000000064b0140 r9 =0000000000000004 r10=0000000008f4fb10 r11=0000000008f4fb10 00:50:04.501107 r12=00000000064b3340 r13=0000000000000000 r14=0000000000000020 r15=0000000000000060 00:50:04.501110 ds=002b es=002b fs=0053 gs=002b eflags=00010287 00:50:04.501113 p1home=0000000000000000 p2home=0000000000000000 pe3home=00000000064b0000 00:50:04.501117 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000 00:50:04.501126 00:50:04.501126 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000456c!!! 00:50:04.501137 LastBranchToRip=0000000000000000 LastBranchFromRip=0000000000000000 00:50:04.501147 00:50:04.501148 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023 00:50:04.501176 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000 00:50:04.501190 ExceptionInformation[0]=0000000000000000 00:50:04.501202 00:50:04.501203 Stack 0000000008f4c740, dumping 0x38c0 bytes (low=0000000008e50000, high=0000000008f50000) 00:50:04.501215 ExceptionInformation[1]=000000000000000c

Though VMSVGA display adapter is configured, it does not matter which display-adapter is configured, same effect for each. No sound device is enabled. I have ensured that hyper-V hypervisor is not enabled

There is a intel haxm type-2 hypervisor, which occasionally is run with android-emulator/qemu. My understanding is that it should not interfere. The joint installtion has worked before. Plus no qemu-VM is running.

Save/Resume/Show/Hide has worked before.

[gkamathh]

Sorry about garbled input, didn't realize this bug-tool, in the first bug description, neither keeps preformatted text, nor allows edits.

There is no Hyper-V or any uusuall antivirus like software. Not using sandbox/containers/WSL. Uninstalled haxm and confirmed that it has nothing to do with it.

To reproduce:

• Windows-10 2004 19041.388
• Virtualbox 6.1.12
• Configure Fedora-family, 2 processors, 6Gb VMSVGA, no-3D acceleration, IDE-controller for ISO, VIRTIO_SCSI controller, VMDK DISKS, no audio, NATNetwork
• Install fedora from downloaded installer ISO
• Attempt start in background -> show -> close and run in background

[gkamathh]

I think I determined the reason for the crash

The storage controller "VIRTIO", which I had used to attach some VMDK disks, was responsible. The idea behind using them was that complete hardware emulation of a SATA-AHCI interface was not required, and that cutting out the unnecessary emulation would allow for more efficiency via the virtualization aware block level VIRTIO drivers in the guest operating system.

Troubleshooting: I added a SATA-AHCI controller, moved the virtual disks over and deleted the VIRTIO Storage controller. The I attempted the hide-in-background/show exercise and confirmed that virtualbox did not crash. This confirmed that that the component causing the crash was the VIRTIO storage controller.

Hence, the "Workaround" to avoid this bug, is, to avoid using VIRTIO Storage controller

So, the bug is that the "VirtIO Storage controller is not suspend/resume tolerant". That may be a more apt title for this bug report.