Custom Query (16363 matches)
Results (2542 - 2544 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2600 | duplicate | VirtualBox x64 guest crashes periodically, reason unknown, log attached | ||
| Description |
I have an ubuntu server x64 guest machine running with VBoxHeadless in the background (with "/usr/bin/screen"). Sometimes I realize that it does not work anymore, but I can't afford that, cause this is a production server. The only clue I have are the logs, cause VBox does not produce any other messages, just kills the machine or closes the window (if I catch the error while running in the X environment). This is what the log (which I think corresponds to the error) ends with: 00:00:06.643 Guest Log: BIOS: int13_harddisk: function 02, ELDL out of range 8F 00:00:06.755 PIT: mode=2 count=0x2e9c (11932) - 99.99 Hz (ch=0) 00:00:07.565 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0) 00:00:10.128 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x20 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:10.128 PIIX3 ATA: Ctl#0: finished processing RESET 00:00:10.288 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:10.288 PIIX3 ATA: Ctl#1: finished processing RESET 00:00:20.046 PCNet#0: Init: ss32=1 GCRDRA=0x048ad000[32] GCTDRA=0x07870000[16] 10:38:05.818 10:38:05.818 !!Assertion Failed!! 10:38:05.818 Expression: i < 4096 10:38:05.818 Location : /home/vbox/vbox-2.0.4/src/VBox/Runtime/r3/linux/semevent-linux.cpp(188) int RTSemEventSignal(RTSEMEVENTINTERNAL*) 10:38:05.861 iCur=0x1 pThis=0000000001834fe0 I have noticed that the log tail is always the following: 02:44:29.618 !!Assertion Failed!! 02:44:29.618 Expression: i < 4096 02:44:29.618 Location : /home/vbox/vbox-2.0.4/src/VBox/Runtime/r3/linux/semevent-linux.cpp(188) int RTSemEventSignal(RTSEMEVENTINTERNAL*) 02:44:29.665 iCur=0x1 pThis=0000000002693430 |
|||
| #2601 | fixed | After MacOS X suspend/resume, bottom of fullscreen display can't be read | ||
| Description |
Running
when I suspend (sleep) the laptop, and then resume, the bottom of the display seems to extend beyond the actual display, so I can't read the labels in the solaris gnome toolbar at the bottom of the screen. This may also involve unplugging my 2nd display and bringing the mac back up without it, not sure if this is necessary to reproduce it. |
|||
| #2602 | fixed | Immediate Reboots of Vista64 host + XML corruption when loading saved W2K guest by VBox 2.0.4 64bit => Fixed in 3.1.4 | ||
| Description |
Hello, I run guest W2K SP4 professional on Free version of VirtualBox 2.0.4 -64 ( czech localization ) on host Vista64 Home Premium SP1, ( all patches applied ). As other sw running Avast Home AV and Comodo CIS 3.5( firewall + HIPS ) . This issue happened for second time in last few days by exactly the same way: When loading saved state of W2K VM, the screen gets suddenly black and Vista OS reboots immediately without warning. Not sure at 1st time, at 2nd time R/O manually run chkdsk showed no problem at any partitions. When run VBox again, it shows W2K machine is not available with "one-way-road red traffic sign". When 1st time it occured, I was not able to use as emergency solution another freshly created W2K guest, using any of existing W2K disk states. Virtual disk manager showed that all snapshots are unavailable. Counting this time it will be the same. In 1st time W2K was just installed and updated and some system installs, so I wiped it and installed guest from the scratch. But I am definitely not going to perform it every week :-) In details window is written this (btw I could not copy it even if VBox context menu offers it, so retyped ): Could not load the settings file: L:\.VirtualBox\Machines\Win2000SP4\Win2000SP4\W2K.xml Premature end of data in tag VirtualBox line 3. Location: 'L:\.VirtualBox\Machines\Win2000SP4\Win2000SP4\W2K.xml', line 400(3), column 43 Return code: E-FAIL (0x80004005) Component: VirtualBox Interface: IVirtualBox {557a07bc-e6ae-4520-a361-4a8493199137}
|
|||

