VirtualBox

Opened 12 years ago

Closed 12 years ago

#10479 closed defect (worksforme)

VirtualBox 4.1.12 crashes after upgrading.

Reported by: aratta Owned by:
Component: other Version: VirtualBox 4.1.12
Keywords: Cc:
Guest type: Windows Host type: Linux

Description (last modified by Frank Mehnert)

I upgraded VirtualBox from previous version and now it crashes after it starts and then ask for a recovery that never gives results.

I didn't found similar post on the forum. Here is my VBox.log and a core dump of the machine. Mi host is Linux with ArchLinux with kernel 3.3.3-1 on a x86_64 Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz GenuineIntel machine.

Attachments (2)

VBox.log (50.4 KB ) - added by aratta 12 years ago.
crash.png (158.6 KB ) - added by aratta 12 years ago.

Download all attachments as: .zip

Change History (9)

by aratta, 12 years ago

Attachment: VBox.log added

comment:1 by aratta, 12 years ago

i forgot to tell that cc is (GCC) 4.7.0 20120414 (prerelease)

comment:2 by Frank Mehnert, 12 years ago

Description: modified (diff)
Guest type: LinuxWindows
Host type: WindowsLinux

I've received your core dump. Actually the 2nd core dump you sent says that the application was terminated by signal 4 (illegal instruction). Did VirtualBox really crash?

Also, you mixed up guest and host, I fixed that in the description.

comment:3 by aratta, 12 years ago

There is a problem with coredump. I follow exactly the instructions from the howto, but cannot create a coredump, don't know why. Moreover after the crash windows restarts asking me to check the sistem and repair. This change also the pid of the process. That's why I forced a coredump with kill -4 after the crash.

Sorry for mixing up the guest and host.

Last edited 12 years ago by aratta (previous) (diff)

comment:4 by Frank Mehnert, 12 years ago

Please describe exactly what happens. If your VM crashes then that means that the VM process terminates immediately. In that case, a core dump will be generated.

From your last description it sounds more like you see a BSOD in the Windows guest and your guest reboots immediately, is that true?

by aratta, 12 years ago

Attachment: crash.png added

comment:5 by aratta, 12 years ago

You are right. Windows starts and immediatly stops with a BSOD. I registered with recordmydesktop and this is the screen message that appears at the crash. Here is the attach file

Thank you

Last edited 12 years ago by aratta (previous) (diff)

comment:6 by aratta, 12 years ago

Solved!!

Hi,

I beg your pardon but i don't know why when i added the vdi image from the gui it was added the sata controller and not to the ide controller. After i removed it and manually added the vdi disk to the ide controller all went ok.

Soprry for bothering you with this stupid question

comment:7 by Frank Mehnert, 12 years ago

Resolution: worksforme
Status: newclosed

Ok, thanks for the clarification! In that case the BSOD makes sense because this is typical Windows behavior. If the controller the system hard disk is attached at changes, then Windows complains very loud. And that's not a VirtualBox bug.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use