According to the 'Guru Meditation' screen, I need to post the vbox.log and vbox.png files to report a critical error.
Is this the right place?
Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
Yes. Please ZIP the log file first.
If the screen is something that can be described in words (blank, Windows startup, etc), don't bother. it saves a (virtual) tree or two...
If the screen is something that can be described in words (blank, Windows startup, etc), don't bother. it saves a (virtual) tree or two...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
The last screen visible is the blue 'please wait' one just before the accounts screen.
- Attachments
-
- VBox.zip
- vbox.log zipped
- (69.78 KiB) Downloaded 10 times
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
Your Intel Core i5-4200M CPU supports VT-x, but it's not available in your system, most probably because something is using it. See I have a 64bit host, but can't install 64bit guests for some ideas.00:00:02.877414 HM: HMR3Init: Falling back to raw-mode: VT-x is not available
That error seems to support my previous assessment. See also if enabling PAE/NX in the VM settings might help.00:00:51.695003 !! VCPU0: Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
No. No difference.
The VM is actually a 32 bit Windows 7. I've been using it fine for a couple of years now, so its only the newest version of VB that's getting upset by it.
I've attached the latest log and screen
The VM is actually a 32 bit Windows 7. I've been using it fine for a couple of years now, so its only the newest version of VB that's getting upset by it.
I've attached the latest log and screen
- Attachments
-
- VBox.zip
- Latest log
- (70.14 KiB) Downloaded 4 times
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
What are you responding to? "No difference" is not a valid response to the faq. Go through it point by point and give details of your answers.
The problem will come down to the fact that VT-x is selected for the VM, but is not available. One solution might be to turn VT-x off in the VM settings. Past versions of VirtualBox have sometimes silently ignored this error and ran without VT-x, but that isn't really a viable long term strategy since VirtualBox is inexorably moving towards a situation where VT-x is assumed to be present for all VMs, so you really need to get this fixed.
The problem will come down to the fact that VT-x is selected for the VM, but is not available. One solution might be to turn VT-x off in the VM settings. Past versions of VirtualBox have sometimes silently ignored this error and ran without VT-x, but that isn't really a viable long term strategy since VirtualBox is inexorably moving towards a situation where VT-x is assumed to be present for all VMs, so you really need to get this fixed.
Re: Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
No difference refers to the fact that I changed the VT-x value (enabled), restarted VB then tried to start the VM. The result was the same.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 8.1 VBox 5.1.22 - ctritical error on startup of Windows 7 VM
Well that is not what your updated log shows. It still shows VT-x as enabled.