Custom Query (16363 matches)
Results (235 - 237 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #20914 | fixed | Issues related to Linux kernel 5.18 | ||
| Description |
The problem applies to both VB 6.1.32 and 6.1.34. My sources have been patched using [94502], [94501], and [94500] as well as the -ffreestanding changes to the link statements. I have not been able to determine a pattern for the crashes. Sometimes they happen during boot, and other times after the VM is running. Sometimes it fails with a Bugcheck 3b as in the attached log file. Other time it is a Bugcheck 1e. |
|||
| #20913 | duplicate | With kernel 5.18.0-rx3, starting a VM fails because imported symbols from the kernel cannot be found | ||
| Description |
Under kernel 5.18.0-rc3, starting a VM results in the following error: Failed to open a session for the virtual machine Windows 10.
Failed to load R0 module /usr/lib/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0' (VERR_SYMBOL_NOT_FOUND).
Failed to load ring-0 module 'VBoxDDR0.r0' for device 'pci' (VERR_SYMBOL_NOT_FOUND).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
This example was for Windows 10, but all VMs fail the same. |
|||
| #20912 | duplicate | Virtual box unable to start VM failing with error (rc=-5640) | ||
| Description |
(rc=-5640) Please try reinstalling VirtualBox. where: supR3HardenedWinReSpawn what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread. |
|||

