If you’re using VirtualBox to host a development environment for Visual Studio 2010, this info may be helpful to you. During debug sessions, you may receive the following exception:
I resolved this problem by disabling VBox’s Nested Paging option for memory. You’ll need to shut-down the guest OS, open its settings in VBox, and turn off the Nested Paging option.
For reference, my configuration is:
Base OS: Windows 7 x64
Virtualization Host: VirtualBox 3.2.8
Guest OS: Windows Server 2008 R2, Standard
Visual Studio 2010 10.0.30319.1 RTMRel
The issue will be fixed in the next VirtualBox major release 4.3, see https://www.virtualbox.org/ticket/9659#comment:30
To me it was solved by installing the Visual Studio 10 SP1
Muchas gracias, funciono de maravilla… Host OSX Lion, Guest Win 7 Pro
SP1 for VS 2010 helps to resolve finally that problem.
turning off Nested Pagings helps, but the problem still remains. You will still receive the same error while running your code
I also had to disable “Enable VT-x/AMD-V.” I installed my system with all of this disabled and enabled it later so I wonder if that is causing problems. Thanks for the tip.
Thanks for posting this. After making the change this error is no longer popping up.
Those of you tracking this topic may also be interested in “Why SQLCraftsman gave VirtualBox the boot” http://AltaModaTech.com/blogs/?p=390
This resolved my problem, thank you!
Actually, not so fast, I’m still experiencing this problem. 🙁
THANK YOU, THANK YOU, THANK YOU!!! This issue has been plaguing me for a very long time.
I resolve this issue turning off the VT-x/AMD-V feature and the issue stop, hope this info help.
Disabling VBox’s Nested Paging option for me didn`t change anything – I`m still getting this exception.
Considering now switching back to vmware.
Thank you, I’ve been battling with this for days. I’ve looked around Google for a bit and finally today got the right search to find this page!
Jon, I’m glad the info was helpful! I still have sudden hardware reset issues, but much less frequently since turning off Nested Paging. I tried VMWare Workstation for about 2 weeks and had hardware resets, so I now believe there’s a problem w/physical NIC driver (I don’t think virtual NIC driver could easily reset hardware). If you have any more resets, pay attention to what network activity was occurring at the time. My recent resets have always been associated with heavy network activity.