virtualbox.org

System setup: Host OS- Ubuntu 16.04LTS, Guest OS-Win 7 32bit, 4GB memory, virtualbox 5.1.34 121010.

Problem occurred after running updates on Ubuntu. VM per usual didn't work so reinstalled virtualbox-dkms and the ext-pack.
Started getting the Guru Meditation error. I've tried all the things that the different posts suggested like reinstalled virtualbox, the extension pack (even updated vb & ext pack), uninstalled,purged and reinstalled.
I've checked the bios there is no VT-x, checked for hyper-v, changed the amount of mem being allocated.
I've even tried installing an older version of virtualbox and extension pack, same problem. I've also tried starting Win7 in safe mode & safe mode networking - same issue.

Attached is a zipped log file.

I do notice that as windows is starting something flashes real quick on the screen I'm unable to see what it is which is no help.
There is no joy in my VM land the past couple of days. So I've attached my log and am hoping someone has an ideo of what is going on. Thanks ~ Ducky

What produced that log? It is not a VirtualBox VM log.

"Fatal error in recompiler cpu" means that VT-x is not available: either not enabled in the host BIOS or something else is using it. If I had the complete log then I'd know which.

Please post a VM log file. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (no other file) to a zip, and attach the zip here.

My apologies, attached is a zipped log file. Thanks

There are a couple of problems with this VM :-

I see that VT-x is enabled in the VM on a host which doesn't support VT-x (you seem to be using an old Asus Celeron 450 laptop - be warned this is not very good for running VMs). You need to disable it using the command line: "VBoxManage modifyvm "Windows 7 32bit" --hwvirtex off".

However I'm not convinced that will fix the problem, since the problem is basically a bug in guest code: something in the guest is trying to execute code from data memory. Where did this Win7 VM come from? Usually this would only happen on a VM that originated outside VirtualBox, and it is trying to execute non VirtualBox VM drivers.

A final and probably the most important problem: you are not running VirtualBox and therefore are not entitled to support on these forums. The app you are running is "VirtualBox 5.1.34_Ubuntu", which is a fork of VirtualBox created by the Ubuntu people. If you want to run Ubuntu code then that's fine, and you should go to the Ubuntu forums for support. If you want support here then you need to be running actual VirtualBox, downloaded and installed from here. I have addressed your problem as a favor, but you'll need to fix this if you want to continue this discussion.

mpack,

Thank you for taking a look at the log file. You are right VT-x shouldn't be enabled because it is not in the Bios which is one of the things I had checked for.
Quite frankly at this point I can't say where the files came from that are showing in the log, I thought they came from the site you listed, but I've installed/uninstalled too much I guess.

So my next step(s) will be to remove, purge and reinstall - start from a clean slate.

I'm new to this and working my way through it with help from those such as yourself. I appreciate you taking the time again thanks.

~Ducky

Ducky wrote:VT-x shouldn't be enabled because it is not in the Bios

It's not a matter of being in the BIOS or not, some manufacturers hide that regardless. It's a matter of your Intel Celeron 450 not supporting VT-x. And 99.999% you need VT-x for this. So, you can't run this VM as is. Your best bet would be to try something from the 4.3.x series, the 5.0.x series or the 5.1.x series.

The higher the VirtualBox version, the more dependent it is on the existence of VT-x, as the "raw mode" will be getting phased out over time.

Wanted to give a quick update. Removed and purged all virtualbox files, extension packs and guest additions. Reinstalled all files from link provided by mpack. Everything is working fine now. Thanks for the help.

Ducky

That's interesting...
First of all, thanks for the update. Can you please upload a ZIPPED VBox.log file from a complete run (start from cold boot / login / shutdown the VM from within the VM)?

I won't have access to the computer again until later this week, but I will get the information for you then.

~Ducky

Ducky wrote:but I will get the information for you then

Thanks! I appreciate it...