#4806 closed defect (worksforme)
WindowsXP guest OS crashes after migration host to AMD64 CPU platform
| Reported by: | Owned by: | ||
|---|---|---|---|
| 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 (3)
Change History (15)
by , 15 years ago
comment:2 by , 15 years ago
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?
follow-up: 4 comment:3 by , 15 years ago
Try turning on VT-x in your host BIOS (it's disabled now) and turn it on for the VM.
comment:4 by , 15 years ago
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:6 by , 15 years ago
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 by , 15 years ago
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?
by , 15 years ago
| Attachment: | VBoxLogs3.zip added |
|---|
VBox logs with VT-x enabled both in BIOS and in the VM settings
comment:8 by , 15 years ago
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 by , 15 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
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 by , 15 years ago
I turn it on. Can you , please, tel me if you know how can I check is VT-x functioning ?
comment:11 by , 15 years ago
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 by , 15 years ago
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.
Vbox logs