Critial Error booting Win XP

[phild]

Not exactly sure when this started as not always using the VM but when attempting to boot my Win XP VM today, I received a critical error. Interestingly, I can boot the VM okay in safe mood but when I attempt a regular boot, the critical error message is received. Oh, VB is v5.1.2

Attempted to re-install VB but the error persists.

Attempted to post VBox.log but it makes the message too large so let me know if I need to send it somwhere.

Not sure how to paste the requested VBox.png but when I open it, it is the standard boot screen for Win XP.

[socratis]

If you compress the VBox.log, it will be small enough to upload. If the PNG shows nothing that can help troubleshoot this, don't bother. If on the other hand it shows the exact error, then either type it here (preferable) or post the screenshot if you have to.

[phild]

VBLog.zip

Log for VB critical error when booting Win XP

(51.29 KiB) Downloaded 7 times

Thanks - hopefully have done this correctly - if so a file VBLog.zip should be attached. As for the .png file, there was no error message just the standard Windows XP boot splash screen.

[socratis]

A couple of things:

• You have a Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR). If the two following steps don't help, go to the bugtracker and either search for an appropriate bug where you'll attach your logs and other vital information, or open a new bug report.
• Make sure that VT-x is enabled in the BIOS and nothing is using it.
• Read this reply from michaln. viewtopic.php?f=6&t=63586#p298699. It contains some information about a rare message in your guest:

  • WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.

Plus you have an old version of the guest additions installed, but that is a really minor thing compared to what you're having.


PS. Is your actual username 'socrates'? I almost got confused when comparing your log with mine

[phild]

Thanks for the suggestions - I was actually having the problem on two different machines. Enabling the virtualization in the BIOS fixed the problem on one of the machines. Still having a problem on the second machine - have yet to try the second suggestion in your note. Once my partner is off the machine, I'll do some more testing on it.

Re "socrates" - my partner uses that handle as he studied him and the hostname for his machine is "socrates".

[socratis]

One fixed, one more to go! If you can't solve the other one, be sure to post the VBox.log.zip from the "problematic" computer.


PS. Thanks for the handle info. It just seemed funny... For sometime, long ago, my e-mail signature was "Ἓν οἶδα ὅτι οὐδὲν οἶδα". Google translate wasn't available then (heck, Google wasn't available then) so I dropped it. But your partner will know the translation...

[phild]

VBLog2.zip

After setting virtualization in the BIOS

(51.46 KiB) Downloaded 7 times

Seems that neither suggestion has resolved the problem. Attached is the latest log (zipped).

[socratis]

The 2nd log look exactly the same as the 1st log. I thought you fixed it and it was another computer that was having a problem, no?

[phild]

hmmm - this is the machine that I continue to have the problems with - let me check that I zipped the right file!!

[phild]

Checked the zip - and it does contain the current log - and then checked the log for the string "WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization." that was in the original and it was not found. Is it possible the zips got confused, the lastest is VBLog2.zip.

Something I did notice when going throught the log however was a reference to "linux.amd64" - the machine that this is occuring on is a Intel cpu based machine. That said, the original VM was built on an AMD platform but has worked fine on the Intel machine that replaced the old amd one prior to recent updates.

[socratis]

Yes, by "look exactly" I didn't mean they are the same. I should have been clearer. They look like they are from the same computer.

So, I think that you posted the log from computer A, I gave you some ideas, you applied said ideas to computer B, B got fixed and then you posted the 2nd log from computer A. Is that correct?

As for the amd64, that's what 64-bit chips/programs are called since AMD was the first one to introduce them. https://en.wikipedia.org/wiki/AMD64

[phild]

That is correct. I was more concerned with computer A at the time and took the initial log from that machine for the first upload. When you made the suggestions, since I was having a "critical" error on machine B too, I thought I would try your suggestion on that machine as well. Machine B VM booted fine so went back to Machine A - applied the suggestions you had made but still continued to have the problem on Machine A - and thus uploaded the second log from Machine A as well.

No logs ever came from Machine B - just coincidence that the suggested change for Machine A happened to address the problem on Machine B - but alas, Machine A still has the problem.