VirtualBox

Ticket #4806 (closed defect: worksforme)

Opened 5 years ago

Last modified 5 years ago

WindowsXP guest OS crashes after migration host to AMD64 CPU platform

Reported by: riprop@… Owned by:
Priority: major Component: other
Version: VirtualBox 3.0.4 Keywords: start
Cc: Guest type: Windows
Host type: Linux

Description

After starting VM, VirtualBox shows critical error window. The VirtualBox process works fine, so the core dump file is not generated

Attachments

VBox.zip Download (54.6 KB) - added by riprop@… 5 years ago.
Vbox logs
VBoxLogs2.zip Download (27.2 KB) - added by riprop@… 5 years ago.
Vbox logs with VT enabled
VBoxLogs3.zip Download (27.1 KB) - added by riprop@… 5 years ago.
VBox logs with VT-x enabled both in BIOS and in the VM settings

Change History

Changed 5 years ago by riprop@…

Vbox logs

comment:1 follow-up: ↓ 2 Changed 5 years ago by frank

Which host do you used before, did the CPU type change?

comment:2 in reply to: ↑ 1 Changed 5 years ago by riprop@…

Yes, it was Intel celeron , now is Intel Core 2 duo. The OS is also changed to 64 -bit version , from "xubuntu 8.04 i386" to "xubuntu 8.04 AMD64"

Replying to frank:

Which host do you used before, did the CPU type change?

comment:3 follow-up: ↓ 4 Changed 5 years ago by sandervl73

Try turning on VT-x in your host BIOS (it's disabled now) and turn it on for the VM.

comment:4 in reply to: ↑ 3 Changed 5 years ago by riprop@…

Thank you I didn't know it must be turned on. I've turned on, but guest OS crashes on the same way.

Replying to sandervl73:

Try turning on VT-x in your host BIOS (it's disabled now) and turn it on for the VM.

comment:5 Changed 5 years ago by sandervl73

Please attach a log of the VT-x session.

Changed 5 years ago by riprop@…

Vbox logs with VT enabled

comment:6 Changed 5 years ago by riprop@…

For test purpose I've copied VM to some other host (Intel P4 centrino, Windows XP) and started VM without problem, so the configuration and migration process is not to blame.

comment:7 Changed 5 years ago by sandervl73

Did you turn it on in your BIOS? (of your computer, not the VM) It's still disabled, but then again you didn't enable it for the VM either. Wrong log?

Changed 5 years ago by riprop@…

VBox logs with VT-x enabled both in BIOS and in the VM settings

comment:8 Changed 5 years ago by riprop@…

I've reinstalled guest OS (WinXP), so , for me, there is no need to search for error any more.

Thank you for support. Regards

comment:9 Changed 5 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to worksforme

Ok, I'll close it then. Your last log shows that VT-x wasn't enabled by your BIOS. If you did turn it on there, then your BIOS is broken.

comment:10 Changed 5 years ago by riprop@…

I turn it on. Can you , please, tel me if you know how can I check is VT-x functioning ?

comment:11 Changed 5 years ago by sandervl73

You can hover the mouse over the 'V' icon in the status bar of the VM window or open the session information window. VBox.log shows that VT-x is disabled and locked. You can try to find an update for your BIOS.

comment:12 Changed 5 years ago by riprop@…

Icon shows in both (old-nonworkink and new working) VM: VT-x/AMD64: Enabled Nested paging: Disabled

Can't find any info in log about it.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use