Opened 13 years ago
Closed 13 years ago
#8552 closed defect (fixed)
Export from 3.2 does not work in 4.0
| Reported by: | Ed | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.4 |
| Keywords: | import | Cc: | |
| Guest type: | other | Host type: | other |
Description
I exported a Windows 7 VM from Virtualbox 3.2.12 on my desktop computer. I then imported the VM in Virtualbox 4.0.4 on my laptop. After importing, Virtualbox says the saved state is unusable, and I discard it. I then try to start Windows. It reaches the "Starting Windows" screen, where normally there is a Windows logo that moves. However, the Windows logo never appears, and boot never finishes.
If I import the VM using Virtualbox 3.2.12 while keeping everything else the same, the VM works fine.
It seems like the VirtualBox kernel module is crashing. I do not get a core file produced, but I am attaching a log from dmesg. If there is a way to get the kernel-level equivalent of a core file, let me know how and I'll do it.
Attachments (2)
Change History (5)
by , 13 years ago
| Attachment: | Windows 7-2011-03-12-19-54-09.log added |
|---|
comment:3 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
vbox.log