virtualbox.org

I started w U22.04 on VB v6.1.36 .. with Hang/freeze issues, so went through a LONG process debugging and re-installing w various versions/settings.. double checking BIOS, etc.

NOTE: Windows OS must have Hyper-V services turned off, as well as Windows Linux System. Screen will show the V-chip icon in grey if issues there.

Also, I had downgraded to 6.1.34 same prob, but didn't realize the Extension pack was NOT down-graded. Before I downgraded, I first tried with a fresh VM install using 20.04 64 bit, same thing Freeze/hangs, then as I downgraded to 6.1.34, I got Application memory access errors WIN32... that are posted everywhere on here.

Even though NO Hyper-V was running, NOR WLS, I disabled anyway.. same errors.

Lastly, I downgraded BOTH virtualbox and extension pack to 6.1.30, still using 20.04 and problems seemed to go away, TBD, works but will test out more.. since I wasted a day of time !?!?
.. not sure if the issue was a 6.1.36 bug or 22.04 interaction ?? for the hang/freeze?? .. and the error was just a mis-match of extension pack ??

Why can't virtualbox have BETTER up-front ERROR and config checking to tell you : A> your extension pack doesn't match the version of VB A?? .. and/or B> Tell you that Hyper-V services or Windows System for Linux is running ??? C'mon Oracle, get your crap together !

I ran into the SAME problem after many others (20.04/22.04 hangs/freezes in the middle of installation), the Application errors cant read memory, etc. , then after a CLEAN install and DOWNGRADING BOTH VB AND the Extension Pack (don't MIX versions since 6.1.36 Ext pack stays when you downgrade to 6.1.30 !!!), and after fresh install and DGd to 6.1.30 w 22.04 running fine.. THEN run into this issue hangs starting to create process that happened after I had a working VM, suspended it, then deleted it's state to: increase cores to 2, increase memory to 4GB, AND..this could be it.. increased the display resolution to 16:9.

ironically, I get past this if I just KILL the VM process from task manager, in windows 10, virtualbox continues and works fine !?? Guessing something to do with the memory or display changes??

Since that, I did an Ubuntu 20.04 OS update and ironically saw my 16:9 video VM format.. downgrade the VM window in the middle. I could not change the video display settings from within VM, so shutdown VM and went into VM manager and looked at the Diplay settings of the VM and found Video memory was only 16MB!.. updated that to 32MB, restarted, and back to High Res w no issues !!
.. so thinking there is a video driver/memory conflict that started the issue above ?? Who knows but would have been nice if the code detects these issues/settings and reports with errors or pointers to "try/check..".

Would be nice if Oracle had half-way decent config checking up-front or Error reporting/diagnostics AUTOMATICALLY (is hyper-v configured/running, is WSL installed, are there driver/memory conflicts.. or maybe just TELL us what the stack trace/error is without doing a science debug project !?).

I merged your somewhat wandering resurrections of peacefully sleeping old topics. And let's cut this kind of talk:

TechThinker wrote:C'mon Oracle, get your crap together !

right here and now. Be peaceful with others and they'll be glad to help. Come at 'em guns blazing, well, you wont get far...

As for the long term science project, well, you could have come for help earlier, that's what we're here for.

Many of the items you discovered we've known about for some time. Virtualbox does not now require Hyper-V to be turned off on a Windows host in many cases. Some bugs do creep in at times, especially when the Windows host OS or 3rd-party AV changes stuff, but the devs are on it.

You are correct that the Oracle Extension Pack could have a bit of better error checking over version differences. That one bites a lot of folks.

With no log posted there's not much we can do to help now. But if you post a log and succinctly state whatever errors you have, we may be able to offer some suggestions.

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log and the hardening log next to it, zip them, and post the zip file, using the forum's Upload Attachment tab.