Opened 5 years ago
Last modified 5 years ago
#19007 new defect
VERR_PGM_HANDLER_NOT_FOUND
| Reported by: | YoungJules | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.0.12 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description
Running 4 VirtualBox (Version 6.0.12 r133076 (Qt5.6.1)) instances on Fedora host with 40Gb RAM. 2 Windows Server 2016 instances were doing updates. Both crashed with VERR_PGM_HANDLER_NOT_FOUND
Attachments (5)
Change History (11)
by , 5 years ago
comment:1 by , 5 years ago
Guest machines were not created on this particular host and also not necessarily use exactly the same version of VirtualBox, although it would have been a VirtualBox 6...
comment:2 by , 5 years ago
Quite similar situation with a Windows 10 guest under Windows 10 host. All X64; VBox 6.0.12; Last version Guest Additions. See https://forums.virtualbox.org/viewtopic.php?f=2&t=95107&p=460050#p460050 for further info.
Every time monthly patches for the OS are applied and reboots, the condition VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) appears if the VM was run from saved state. Not if the VM was freshly booted, then patch applied.
I already checked the use of screen driver as well as having enough memory for screen as well as for the machine.
Glitch happens every time montly patches are applied. Several VMs. Several HW.
comment:3 by , 5 years ago
Thanks Caspertone2003, happy I'm not looking for some worrying memory/disk/way I installed the OS kind of problem. And thanks for the advice to make sure the VMs are started from a fresh boot before doing updates.
Kind regards, YoungJules
comment:4 by , 5 years ago
In the VirtualBox forums there are several cases with the VERR_PGM_HANDLER_NOT_FOUND error using a Windows host (in contrast to this ticket, which is about a Linux host). In one of the forum threads I wrote a summary of my findings (https://forums.virtualbox.org/viewtopic.php?f=6&t=94381&start=30#p461317) regarding log file messages that I think may be key points.
Additionally, there are cases of Windows BSODs in VBoxDDR0.r0, which may also be related.
comment:5 by , 5 years ago
@fth0 My comment relates to a Windows 10 host because I was unable to add that to the OP ticket... But the issue is related to the guest... See https://forums.virtualbox.org/viewtopic.php?f=2&t=95107&p=460050#p460050
comment:6 by , 5 years ago
See also the logs attached in the thread https://forums.virtualbox.org/viewtopic.php?f=6&t=96876.
MachineB png file