How to avoid CRITICAL_STRUCTURE_CORRUPTION errors with VirtualBox inside VMWare

Question

I have the same setup as described here:

Now I'm frequently getting BSOD with a CRITICAL_STRUCTURE_CORRUPTION error and I'm wondering if I can get rid of those. I read opinions that I must expect an unstable system in this setup of nested virtualization, on the other hand it does work and people seem to be using it.

After searching for this error on the web, I already upgraded to the latest versions of VMWare Player (6.0.3 on Windows 8.1) and Virtualbox (4.3.14 on Ubuntu 14.04.1 inside VMWare) and I reduced the number of CPUs in the Vagrant Virtualbox Machine to 1, but the error still occurs, sometimes after an hour or so, and only when running the Vagrant Virtualbox inside the VMWare Player.

Anything that I could try to make it run smoothly?

This site is for programming questions. We are not general software tech support. — Marc B, Jul 30 '14 at 14:55
Ok, moved it to superuser: http://superuser.com/questions/790216/how-to-avoid-critical-structure-corruption-errors-with-virtualbox-inside-vmware — Jörg Brenninkmeyer, Jul 30 '14 at 15:02

score 0 · Answer 1 · answered Oct 27 '16 at 12:23

0

Make sure Hyper-V windows resource is inactive. This works for me

Ty

answered Oct 27 '16 at 12:23

Sergio Peluzzi

31
2

How to avoid CRITICAL_STRUCTURE_CORRUPTION errors with VirtualBox inside VMWare

1 Answers1