Guru Meditation 1155 (3x Fault) Importing Large File into DB

[Alpha47]

Hi,

I'm working on building a planet map tile server on a VirtualBox VM. As my VM was nearing the end of importing the planet file (it had been importing for about 86 hours) VirtualBox notified me that it was entering "Guru Meditation" mode and that I should seek help. Log excerpt:

Code: Select all

86:20:54.471338 !!                 Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

86:20:54.472553 !!

86:20:54.473706 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT

Details on the construction of the map tile server I'm working on can be found here: http://switch2osm.org/serving-tiles/man ... ver-12-04/. The final step (importing the planet.pbf file into a GIS database and uncompressing it) generally takes several days. Because of the uncompressed planet file's large size my database is housed on an external drive (see below).

From looking around the user forums (search.php?keywords=guru+meditation) it seems like Guru Meditations have been an unfortunately common problem that occurs shortly after the VM has been started and that is associated with machines using AMD processors and VirtualBox 4.3.4. I think this case is different because of the size of the planet file as it is imported and uncompressed (20GB uncompressed into 400GB), the fact that my machine has an Intel processor and the time it took for this error to occur (86 hours).

• Machine
o Windows 7
o 32 GB RAM
o Intel i7-3740QM 2.70 GHZ processor
o 64-bit
• VirtualBox
o Version 4.3.4
o Linux 2.6 (64-bit) running Ubuntu 12.04
o PostgreSQL 9.1
o 24 GB RAM
o 620 GB of disk space (external drive) - 1TB Seagate GoFlex USB with exFAT file system

Log attached

Any advice on what this error means in VirtualBox given this setup? Is this a similar error to what has previously been reported?

Thanks!

[michaln]

Any advice on what this error means in VirtualBox given this setup?

It means the guest system crashed hard. It might be caused by a virtualization bug, or it might be caused by a bug in the software running in the VM (which would hang/reboot a physical host system).

Is this a similar error to what has previously been reported?

Impossible to tell.

[Alpha47]

So nothing good then. Thank you for the general guidance!