Custom Query (16363 matches)
Results (379 - 381 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12592 | obsolete | vboxvideo 4.3.6 for Solaris 11 on XStreamDesktop/illumos OpenGL problems | ||
| Description |
We're testing the new 4.3.6 additions that delivers vboxvideo for Solaris with X11 1.13.1 and 1.14.5 on our XStream Desktop based on illumos. It mainly works fine both with X 1.13.1 and X 1.14.5, but it shows problem with cairo-dock in OpenGL mode (-o). Because previously vbox was not delivering any X driver later than 1.12.x on Solaris, we used to provide our own build of additions, modified to work with 1.13.1 and 1.14.5, and worked fine, also in OpenGL mode. The current public beta1 of XStream Desktop features X 1.13.1, and it has the same problem: using 4.3.6. additions breaks cairo-dock. Debugging cairo sources, we've seen it's looking for a stencil buffer + transparency visual, and vboxvideo answer with one that cairo picks up and use, but then all is painted bad (a big black box an all the horizontal area of the dock, glitching, and more bugs). Also, Xorg.0.log shows strange errors during startup. The vboxvideo is correctly loaded, but then later: [ 93.819] drmOpenDevice: node name is /dev/dri/card0 [ 95.810] drmOpenDevice: open result is -1, (No such device or address) [ 95.810] drmOpenDevice: open result is -1, (No such device or address) [ 95.810] drmOpenDevice: Open failed [ 95.810] drmOpenDevice: node name is /dev/dri/card0 [ 95.811] drmOpenDevice: open result is -1, (No such device or address) [ 95.811] drmOpenDevice: open result is -1, (No such device or address) [ 95.811] drmOpenDevice: Open failed [ 95.811] [drm] failed to load kernel module "vboxvideo" [ 95.811] (EE) [drm] drmOpen failed. [ 95.811] (EE) VBoxVideo(0): DRIScreenInit failed, disabling DRI. You can testdrive the system downloading the iso here: http://sourceforge.net/projects/xstreamos In the files section you may also download our own additions to check that they work (built on vbox 4.2.18). Last but not least, no XVideo support, xvinfo shows no screen capable of XVideo. Do vboxvideo supports it? Thanks for any help, Gabriele. |
|||
| #819 | fixed | vboxvfs seems to have problems with mmapped access to files => retry with 6.0.6 | ||
| Description |
I've created a VM with a clone of my webserver's configuration to test my projects under "real" conditions. The Apache webroot is a shared folder mountpoint which is connected to the folder in the host system where I store my sources for the web development. In the guest VM, I have no problems to access the documents with cat, but the Apache doesn't deliver the files if they're larger than 255 bytes. If I reconfigure Apache to use a handler (e.g. mod_php) to process the requested file before delivering, everything works as desired. Up to my knowledge, Apache uses mmap() for fast access to static content. Probably this mechanism needs a special support of the underlying file system which vboxvfs doesn't provide. Host:
Guest:
|
|||
| #4840 | worksforme | vboxvfs module build not suitable for kernels with CONFIG_MODVERSIONS | ||
| Description |
Compilation of the vboxvfs module is incomplete: # cd vboxvfs/ # make [...]
WARNING: "RTSpinlockAcquireNoInts" media/vbox.local/linux/module/vboxvfs/vboxvfs.ko undefined! [...] The problem is because there is no symbol information available in the build directory (which is vboxvfs/ in this case). The necessary information resides in ../vboxadd/ instead. The separation of vboxadd and vboxvfs therefore causes the aforementioned problem with the openSUSE 11.1 2.6.27.x kernel, or generally, as I see it, any kernel with CONFIG_MODVERSIONS=y, CONFIG_MODULE_SRCVERSION_ALL=y. The solution is to combine the build directories, such that the toplevel Makefile invokes Kbuild once, instead of each directory (vboxadd, vboxvfs, etc.) doing it for itself. BTW: The 'clean' target of the vbox additions Makefiles incorrectly clean files They should be running - at least -
and _not_ remove *.o, Modules.symvers modules.order, etc. for themselves. That is, BTW, Modules.symvers is wrong - the file is called Module.symvers. |
|||

