Opened 11 years ago
Closed 9 years ago
#12254 closed defect (fixed)
Guru Meditation (VERR_TRPM_DONT_PANIC) VBox 4.3 fails to load the VM
| Reported by: | spyrus | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.3.0 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Attachments (2)
Change History (12)
by , 11 years ago
by , 11 years ago
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Hardware Virtualization in VirtualBox is disabled but that setting was there from the beginning when i have created the machine (back in 4.0.x release or earlier) Last update to 4.3 has the problem on the same machine with untouched settings
comment:4 by , 10 years ago
Sorry for the stupid question, I missed your last comment before. That is indeed a bug but enabling VT-x is still preferred.
comment:5 by , 10 years ago
Ok it worked by enabling VT-X and paging (i have Core i7). The machine though cannot be shutdown still, but that is an old bug. If interested check that link https://forums.virtualbox.org/viewtopic.php?f=6&t=31658
comment:6 by , 10 years ago
| Summary: | VBox 4.3 fails to load the VM → Guru Meditation (VERR_TRPM_DONT_PANIC) VBox 4.3 fails to load the VM |
|---|
comment:7 by , 10 years ago
I've seen this reported a few times recently. Here is a recent example involving 4.3.18. Same error and same scenario in that VT-x is enabled in the VM (probably for legacy reasons) but disabled in the BIOS.
comment:8 by , 10 years ago
Here's another one from today. Exact same scenario, except this user suggests that preventing his guests drive from sleeping bypasses the issue. https://forums.virtualbox.org/viewtopic.php?f=6&t=64220
comment:9 by , 10 years ago
Hi mpack, all VBox.log files which involve 'acpiPMTmrRead' are a duplicate of #13521. This problem is a 4.3.18 regression and happens only with VT-x/AMD-V disabled/not available.
Other tickets (like this one, see the original VBox.log file) have PDMQueueInsert in the lines right below the Guru meditation description. These reports don't describe a regression but actually a problem with the LsiLogic emulation. Also does only happen if VT-x/AMD-V is not available.
Did you disable VT-x for this VM or is VT-x just disabled in the BIOS?