virtualbox.org

I updated to the latest version (4.3.4 r91027) and now one of my virtual machines is crashing during start up. It will start in safe mode, but will not start normally. I have attached the vbox log. If anyone can provide some help it would be appreciated. Thanks.

Hmm. This is a new one.

VBox.log wrote: 00:00:30.989534 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:30.989536 !!
00:00:30.989536 !! Guru Meditation -4017 (VERR_VMX_UNEXPECTED_INTERRUPTION_EXIT_TYPE)
00:00:31.002474 !!

I note that the log says you're running a 64bit VM, though you didn't mention that in your post. is this in fact XP-64? You haven't been applying that "longmode" thing have you?

VBox.log wrote: 00:00:00.850568 Guest OS type: 'WindowsXP'
00:00:00.852546 fHMForced=true - SMP
00:00:00.852552 fHMForced=true - 64-bit guest

No, it should not be a 64 bit VM. It is standard XP x86. The host is machine Win 8 x64.

In that case I would try the following:

Try setting long mode off and see if it helps. Note: guest must be shut down and not saved state.

I ran the command but the VM still won't start. I attached a new log file.

Try disabling VT-x in the VM settings.

Do you have any other VM platform running on this host? I.e. disable Hyper-v.

p.s. I know the error dialog tells you to, but there's no need to include blank screenshots in the zip. If the screenshot doesn't contain an error message or some other indication of context then it just wastes space.

I tried disabling VT-x, and the VM just hangs at the "Press Ctrl+Alt+Delete" screen, but doesn't throw the virtual box critical error. I have attached the log from that (minus the screen shot). I have two other XP x86 VMs, a Win 7 x86 VM, and a Win 7 x64 VM. All of those are working fine.

Where did this XP come from? I'm concerned that in this same VM you have chopped and changed paramaters that would typically force XP to select a different HAL during installation, then it would be no surprise that it doesn't boot up. Perhaps you should consider reinstalling it with the basic settings you have now. Or at least repair the installation.

This guru is caused by unhandled interurption-exception type, in this case that'd be privileged software exception (ICEBP most likely). Should be fixed in the upcoming release, I'm curious why/how this happens though... do you have any Anti-Virus or some such software in your VM when it boots up?

I just installed the latest version, and now this virtual starts with no issues. Thanks for the help.