Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

[kenny]

• Host: Windows 7 64-bit
• Guest: Ubuntu 32-bit
• VirtualBox: 4.3.20

We took an initial snapshot, had multiple successful restarts. Then at the end of the day, tried to restart the image, and got a Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT).

I'm attaching the logs and any insight, anomalies, hints/tips, would be much appreciated.

[kenny]

Logs

[kenny]

I have seen in another ticket that this still may be an issue. Ticket 13125.

[Frank Mehnert]

The guest state looks invalid:

CPUM: 0060:e183b28a 00 00                   add byte [eax], al

so I would say the guest is really screwed up and therefore a triple fault is triggered.This is the same what would happen on real hardware. Please double-check your guest for any sign of binary corruption. If you cannot boot your Ubuntu guest, use a live CD and mount the image. To check for binary corruption, debsums is a good helper (but the guest must be bootable to use this tool).

[kenny]

Frank, thanks for the reply.

Would it matter that we made the image on Mac with 4.3.20 r96996 and its running on windows with r96997?

[Frank Mehnert]

Should not matter. It's the same image. But as you are using snapshots it's really important that you use the very same image chain on both hosts. Actually it would be better to not move a VM with snapshots to another host. The preferred way to move a VM from one host to another is to delete all snapshots (that is, merge the later changes in the base disk image) and then either use OVA export + import or create a new VM on the target host with very similar settings (!), copy the VM image and then attach the image on the target host.

If you make any mistake while moving a VM with snapshots between hosts, then you will definitely experience binary corruption.

[kenny]

@Frank, we root caused the issue. Between the multiple successful starts, and the end of day failed start with the Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) error, the user enabled VT-x.

We had to restart the image, and create a new snapshot with the changed VT-x configuration.

Thanks for your help.

[Frank Mehnert]

I still don't know how this worked at all but let's close this ticket.