Custom Query (45 matches)
Results (16 - 18 of 45)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8 | fixed | Import 5.x source | ||
| Description |
Import latest VBox source code. Rename current trunk to a branche for historical reason. The old vendor part could be deleted and redone from scratch. |
|||
| #61 | fixed | Improper (garbled) mouse pointer graphic on Linux guests | ||
| Description |
This same problem is now fixed for Windows hosts (XP & Windows 7). Is there a similar fix for Linux Hosts like SuSE? |
|||
| #37 | fixed | Kernel logging implementation | ||
| Description |
Implement kernel logging. We need a logging function for all ring0 components. 1) Probably, we'll need a ring buffer like in DaniS506 (we could look in DaniS sources to use Daniela's implementation). Then we can copy it to a file with copy vboxdrv$ vbox.log 2) OS/4 kernel has KernPrintf? KEE call, so we can use it too, as an option. Then use: copy kernlog$ kernlog.txt Note that it should not be limited in vboxdrv.sys, but use the single API for all Ring0 components, like *.r0, *.rc, VboxGuest?.sys from guest OS's, TAP driver etc. |
|||
