Custom Query (16363 matches)
Results (1102 - 1104 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1901 | fixed | Huge log files fill up the host file system (PATM: ...) => Fixed in 2.0.4 | ||
| Description |
WARNING: DANGER !!! VirtualBox 1.6.4 will crash your Windows computer, and render it unbootable !!! I have been using VirtualBox 1.6.4 for several hours and the log file went up to 6GB (!!!) in size, tooking over my Windows partition, and leaving zero space. Of course, Windows refused to boot after reboot, and crashed with BSOD. Sun: I really recommend building v1.6.4a as soon as possible. -Technologov, 2.8.2008. |
|||
| #1902 | fixed | VBOX_PATH_X11_XORG_1_x / x headers not found | ||
| Description |
I've finally built 2008-Aug-02 svn.. However I couldn't build it without symlinking my git GL X11 and xorg include folders over to usr/include and hardcoding my /opt/xorg/include path in a few makefiles. I don't think the build process can cope with non-standard x11 installs. The configure script uses pkg-config and correctly finds X library and include paths, but whatever flags are set aren't visible throughout the whole build. pkg-config --cflags --libs x11 = -I/opt/xorg/include -L/opt/xorg/lib -lX11 The following places required intervention..
1, HostServices/SharedOpenGL required GL headers ..for example, and I found this strange, my makefile for vboxvideo: vboxvideo_drv_71_INCS = \ $(VBOX_PATH_X11_XORG_7_1) \ $(VBOX_PATH_X11_XORG_7_1)/X11 \ $(VBOX_PATH_X11_XORG_7_1)/xorg vboxvideo_drv_15_INCS = \ $(VBOX_PATH_X11_XORG_1_5) \ $(VBOX_PATH_X11_XORG_1_5)/X11 \ $(VBOX_PATH_X11_XORG_1_5)/xorg \ /opt/xorg/include \ /opt/xorg/include/X11 Both drivers were made.. .the first uses VBOX_PATH_X11_XORG_7_1 to successfully reference the headers that are included in the tarball. ..however, although I see VBOX_PATH_X11_XORG_1_5 is declared in the exact same manner in the Config.kmk file, the later fails.. ..as as you see I needed to append my custom include paths. Asides.. 1, I also had to append these paths in src/VBox/Additions/x11/xmouse/Makefile.kmk vboxmouse_drv_INCS := \ $(KBUILD_PATH)/include/iprt \ $(KBUILD_PATH)/include/VBox 2, I actually resorted to trying the 'stable' 1.6.4 ose but immediately ran into problems There seems to be missing makefiles at src/apps/Makefile.kmk and /src/apps/tunctrl/Makefile.kmk ..and if they're purposely missing ..then stable doesn't build without them!! So i took the svn versions ..but had to change the constants 'SUB_DEPTH' back to 'DEPTH' in each case. The above problems with not finding the xorg include paths is also present in this 1.6.4 release! However this time SharedClipboard/Makefile.kmk wouldn't use my VBoxSharedClipboard_INCS.linux hack.. ..hence I had to give up and re-revert back to the svn build for which I had got further with. Anyway it's built now :) ..I can't insert vboxadd or vboxvfs kernel modules into my 2.6.26 kernel due to..
FATAL: Error inserting vboxadd (/lib/modules/2.6.26/extra/vboxadd.ko): No such device and
FATAL: Error inserting vboxvfs (/lib/modules/2.6.26/extra/vboxvfs.ko): Unknown symbol in module, or unknown parameter (see dmesg) vboxvfs: Unknown symbol vboxadd_cmc_open vboxvfs: Unknown symbol RTLogBackdoorPrintf vboxvfs: Unknown symbol vboxadd_cmc_ctl_guest_filter_mask vboxvfs: Unknown symbol RTErrConvertToErrno vboxvfs: Unknown symbol vboxadd_cmc_call vboxvfs: Unknown symbol RTAssertDoBreakpoint vboxvfs: Unknown symbol vboxadd_cmc_close vboxvfs: Unknown symbol AssertMsg2 vboxvfs: Unknown symbol AssertMsg1 ..but I think i've had all I can take for today. |
|||
| #1905 | fixed | enabling Serial Port throws VERR_PDM_DRIVER_NOT_FOUND | ||
| Description |
If I enable a serial port in the VM settings I get the error below: Unknown error creating VM. VBox status code: -2823 (VERR_PDM_DRIVER_NOT_FOUND). Result Code: 0x80004005 Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} My serial port settings are as follows, although it doesn't seem to matter which port number or path is used: Port Number: COM1 Port Mode: Host Device Port Path: /dev/tty.serial0 Also, selecting Host Pipe throws a different error. |
|||

