I have just installed Fedora 8 on my Acer Aspire 5000 laptop with 1.5GB RAM. Installed the VirtualBox All Users AMD 64 (1.5.2) version of VirtualBox. My Windows XP guest, with all updates and version 1.5.2 of the VirtualBox guest apps, is crashing intermittently.
I am a fairly experienced Linux user and a semi-experienced user of VirtualBox as I had it running on my Fedora 7 with no problems.
Here is a copy of the log file that was created after the crash.
<<<<< Cut Here >>>>>
Log created: 2007-11-11T18:23:24.916577000Z
Executable: /opt/VirtualBox-1.5.2/VirtualBox
Arg[0]: /opt/VirtualBox-1.5.2/VirtualBox
Arg[1]: -comment
Arg[2]: Windows XP Pro
Arg[3]: -startvm
Arg[4]: 9b4064a4-90ad-40ab-c4bf-97d0d8f62e90
!!Assertion Failed!!
Expression: i < 4096
Location : /home2/vbox/vbox/1.5-lnx64-rel/src/VBox/Runtime/r3/linux/sems-linux.cpp(219) int RTSemEventSignal(RTSEMEVENTINTERNAL*)
iCur=0x1 pIntEventSem=000000000081a7d0
<<<<< Cut Here >>>>>
Should I be looking at another log file for issues?
This might be a bug with the new PulseAudio that Fedora is using, don't know for sure.
Any help would be appreciated.
Fedora 8 VM Crash
-
sjstafford
- Posts: 2
- Joined: 11. Nov 2007, 22:55
Still having problem on 1.5.6
Still having this problem on VirtualBox 1.5.6. This is the only issue keeping me from using VirtualBox full time, it's just a toy until this is fixed. VMWare does not have this problem.
More info. This only happens when I have VB running in a workspace that does not have focus. The guest is running in full screen mode, but I am working in other desktop workspaces, while the guest in "idling" in it's own workspace.
I think this has something to do with a timer or counter in the guest shell that is looking for something or some user interaction with the guest, but running on an unused workspace, no updates or interaction is happening with the guest.
More info. This only happens when I have VB running in a workspace that does not have focus. The guest is running in full screen mode, but I am working in other desktop workspaces, while the guest in "idling" in it's own workspace.
I think this has something to do with a timer or counter in the guest shell that is looking for something or some user interaction with the guest, but running on an unused workspace, no updates or interaction is happening with the guest.
Similar problem with 2.0.2
I have a similar problem with kernel 2.6.27.2 on VirtualBox 2.0.2 Binary (host kernel 2.6.27). The error occurs after a short time if there is high network load.
Logfile:
Logfile:
Code: Select all
Log created: 2008-10-22T21:14:00.739727000Z
Executable: /opt/VirtualBox/VBoxHeadless
Arg[0]: /opt/VirtualBox/VBoxHeadless
Arg[1]: -s
Arg[2]: perimeter
!!Assertion Failed!!
Expression: i < 4096
Location : /home2/vbox/vbox/lnx64-rel/src/VBox/Runtime/r3/linux/semevent-linux.cpp(188) int RTSemEventSignal(RTSEMEVENTINTERNAL*)
iCur=0x1 pThis=00007f7f1c07a770