Custom Query (16363 matches)
Results (2296 - 2298 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4201 | fixed | VBox 2.2.4 segfaults after heavy I/O => Fixed in 3.0 | ||
| Description |
Also see this topic: http://forums.virtualbox.org/viewtopic.php?f=7&t=18462 I get regular segfaults when running VirtualBox 2.2.4 or 2.2.2 PUEL on Ubuntu 9.04 amd64, with guest OS FreeBSD 7-STABLE amd64. The dmesg shows: [60327.316891] VirtualBox[21681]: segfault at 20 ip 00007f159fd66c32 sp 00007f1536ba5e10 error 4 in VBoxVMM.so[7f159fcbd000+12a000] [164613.347935] VirtualBox[19352]: segfault at 20 ip 00007f5b68567c32 sp 00007f5afb112e10 error 4 in VBoxVMM.so[7f5b684be000+12a000] The segfaults occur while performing heavy I/O on 8 raw disks attached via AHCI. The heavy I/O originates from a ZFS RAID-Z ("RAID5") configuration on those 8 disks, and performing a scrub on the volume, which is 100% disk bound and takes little over an hour to complete. But often the crash is triggered within the first run, between 30-50 minutes. On the third try, i tried to run a backtrace and dump. Logs attached, but the dump is over 1.7GB. I could try reducing the memory to reduce the dumpsize, but ZFS likes to use lots of memory so this could be problematic. I've already tried 5-passes with Memtest86+ so memory corruption is not an issue here. I think these crashes are a defect of Virtualbox, and would like help to debug this thing. Kind regards, sub |
|||
| #4203 | fixed | Mouse problems with Linux/Slitaz | ||
| Description |
I have just created a new virtual machine running Slitaz 2.0. Everything works fine except for the mouse. A majority of the time the movement of the mouse is restricted to a small part of the screen. If I move the mouse wildly then it is possible to access other parts of the screen until movement is restricted again. I'm running VirtualBox on a Dell Latitude D600. |
|||
| #4206 | fixed | Rapair install not possible in the nromal way | ||
| Description |
After the install of VB 2.2.4, if you go to Control Panel/Add Remove Programs and try to run a "Repair" install of VirtualBox, it will fail with the message similar to "File 'C:\Temp\virtualbox_2.2.4.msi' not found" when it actually tries to run. There is no way to run a repair install without going back to the original installer .exe that was downloaded. I noticed this on an upgrade from 2.2.0 -> 2.2.4. |
|||

