Opened 15 years ago
Last modified 15 years ago
#3872 closed defect
vb-2.2.2: vm aborts on boot on Fedora 11 x86_64 — at Version 2
Reported by: | Sean Darcy | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.2.2 |
Keywords: | boot abort | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description (last modified by )
I have vbox on Fedora 11 x86_64 with 2 vm's, windows 7 and xp.
I set them up and ran them under 2.2.0. rpm -Uvh --nodeps.
Installed 2.2.2, no problem. One vm - xp - was saved. Started it up, worked fine. Shut it down to change settings to allow VRDP.
But now when I start either vm, I get the bios screen, a message that the vm couldn't find any audio, then it aborts.
I went back and turned off VRDP. Same result.
Attached is the log.
I tried to get a core dump:
As root:
[root@intel64-office ~]# ulimit -c unlimited [root@intel64-office ~]# echo -n 1 > /proc/sys/fs/suid_dumpable [root@intel64-office ~]# /usr/lib/virtualbox/VirtualBox -startvm Windows-XP
The VM boot window showed up, same dialogs, then aborts. But no core dump:
[root@intel64-office ~]# ls anaconda-ks.cfg Music <unknown>-bugreport.txt Desktop Pictures Videos Documents Public Windows-XP-2009-04-28-21-51-54.log Download Templates
sean
Change History (4)
by , 15 years ago
Attachment: | Windows-XP-2009-04-28-21-55-27.log added |
---|
comment:1 by , 15 years ago
by , 15 years ago
comment:2 by , 15 years ago
Description: | modified (diff) |
---|
Cannot reproduce any crash on F11/x86_64. Please could you check this page on how to create a core dump? Please contact me by private E-mail if you have something (frank _dot_ mehnert _at_ sun _dot_ com).
I have the exact same problem.
I upgraded to F11 and subsequently upgraded VirtualBox to the F11 version.
I successfully started VirtualBox after the upgrade and managed to start my virtual machine (Windows XP Professional) once. I then restarted it and got an abort. I've not been able to restart the machine despite several attempts at changing settings in the VM.
Rebooting the VirtualMachine puts it in a bad state such that it's impossible to restart again.
Unlike the guy above I did not change any settings, I simply restarted the virtual machine and it corrupted.
I don't get any error messages, it's nothing to do with the audio or the VRDP setting.