Opened 10 years ago
Last modified 9 years ago
#14597 new defect
5.0.4 - Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR
| Reported by: | talr | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.4 |
| Keywords: | Guru Meditation | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
I've been using VirtualBox for a while 4.3.18 - 4.3.30 where i have a VM with a live snapshot. after upgrading to 5.0.4 i've got a problem on my 4.3.30 created VM: "Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR" reverting back 4.3.30 runs the VM fine but not with 5.0.4
Host: Windows 7 x64 guest: Linux based OS
see also: https://forums.virtualbox.org/viewtopic.php?f=6&t=70070
Attachments (1)
Change History (4)
by , 10 years ago
| Attachment: | Virtual_5.0.4_logs_Guru Meditation_VERR_REM_VIRTUAL_CPU_ERROR.zip added |
|---|
follow-up: 2 comment:1 by , 10 years ago
| priority: | blocker → major |
|---|
This is definitely not a blocker. Enable VT-x for this VM and your VM will most likely work. The so-called "raw mode" has lower priority.
comment:2 by , 9 years ago
Replying to frank:
This is definitely not a blocker. Enable VT-x for this VM and your VM will most likely work. The so-called "raw mode" has lower priority.
Enabled VT-x. The previous live snapshots still don't work. Can you offer a real solution?
comment:3 by , 9 years ago
Restoring the snapshot will also restore the VM settings at this time. If the snapshot does not boot then I fear you can only restore to that snapshot and then discard the VM state. This is like powering off the VM without saving data. If the VM starts after restoring the snapshot without discarding the state then shut down the guest cleanly, change the VM settings (enable VT-x) and start the guest again.
Logs