Re: Virtualbox UI and remote X clients
On Oct 26, 2010, at 15:50 , Ade Lovett wrote: > VirtualBox itself doesn't appear to honor -graphicssystem (I tried > --graphicssystem too), and crashes with the exact same Qt error. Found it, after much more digging around: csh% env LIBGL_ALWAYS_INDIRECT=1 VirtualBox works. So it's definitely a bug in OpenGL somewhere. At the very least the environmental variable above should be folded in to a command-line option to VirtualBox itself until the underlying problem is correctly resolved. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Oct 26, 2010, at 14:57 , Juergen Lock wrote: > I just talked with Michael from the vbox team about this a bit and > he came up with another thing to try: running VBboxManage etc with: > > -graphicssystem raster VirtualBox itself doesn't appear to honor -graphicssystem (I tried --graphicssystem too), and crashes with the exact same Qt error. VBoxManage doesn't seem to have an equivalent to clicking on the Settings box from within VirtualBox itself, rather it relies on a whole bunch of command-line options after 'modifyvm ' to achieve the same result. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
In article <081b8654-fd34-4062-bbe7-4171cbd57...@freebsd.org> you write: > >On Oct 25, 2010, at 03:35 , Bernhard Froehlich wrote: >> I think i've found the reason why it did not work. Please add >> --disable-opengl and also add the attached patch. >> >> http://home.bluelife.at/patches/vbox-2dacc-opengl.diff > >Unfortunately, this breaks at the install phase: > >[] >cd: can't cd to >/usr/obj/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE/out/freebsd.amd64/release/obj/VirtualBox/qtnls >*** Error code 2 > >Looks like more digging is required. Hi! I just talked with Michael from the vbox team about this a bit and he came up with another thing to try: running VBboxManage etc with: -graphicssystem raster It didn't work for me (lots of `Qt WARNING: X Error: BadShmSeg (invalid shared segment parameter)' and pretty much empty windows), but he thought it might still be worth a try for you... Good luck, :) Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Oct 25, 2010, at 03:35 , Bernhard Froehlich wrote: > I think i've found the reason why it did not work. Please add > --disable-opengl and also add the attached patch. > > http://home.bluelife.at/patches/vbox-2dacc-opengl.diff Unfortunately, this breaks at the install phase: [] cd: can't cd to /usr/obj/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE/out/freebsd.amd64/release/obj/VirtualBox/qtnls *** Error code 2 Looks like more digging is required. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Sat, 23 Oct 2010 17:29:15 -0500, Ade Lovett wrote: > On Oct 23, 2010, at 03:28 , Bernhard Froehlich wrote: >> I think it makes sense to add an OpenGL option that disables it all >> together. Can you try if it works for you when you reenable VIDEOHWACCEL >> in the Makefile and add CONFIGURE_ARGS+=--disable-opengl somewhere? > > I forcibly added --disable-opengl and recompiled. Same error. Looks > like it's going to be a bit more tricky than that. I think i've found the reason why it did not work. Please add --disable-opengl and also add the attached patch. http://home.bluelife.at/patches/vbox-2dacc-opengl.diff -- Bernhard Fröhlich http://www.bluelife.at/ vbox-2dacc-opengl.diff Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Oct 23, 2010, at 03:28 , Bernhard Froehlich wrote: > I think it makes sense to add an OpenGL option that disables it all > together. Can you try if it works for you when you reenable VIDEOHWACCEL > in the Makefile and add CONFIGURE_ARGS+=--disable-opengl somewhere? I forcibly added --disable-opengl and recompiled. Same error. Looks like it's going to be a bit more tricky than that. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Fri, 22 Oct 2010 17:04:35 -0500, Ade Lovett wrote: > On Oct 22, 2010, at 16:21 , Bernhard Froehlich wrote: >> Could you please post that errors? > > freebsd% setenv DISPLAY remote:0 > freebsd% VirtualBox > > Wait for UI to pop up, click on 'Settings' for any virtual host, > VirtualBox crashes with: > > Qt WARNING: QGLContext::makeCurrent(): Cannot make invalid context current. > Segmentation fault > > > (remote) in this case has been (so far): > > MacOSX 10.6 with Apple's X11.app > MacOSX 10.6 with XQuartz.app > Windows XP with cygwin/X > Windows 7 with cygwin/X > Xvnc on the FreeBSD box, then using either the Mac or Windows box to > fire up a vnc client to get to the Xvnc. That makes more sense now. Looks like the 2D acceleration unconditionally requires OpenGL. You will find a lot of MythTV users with exactly that problem and they usually switch to Qt rendering. Don't know if vbox has such a possibility. I think it makes sense to add an OpenGL option that disables it all together. Can you try if it works for you when you reenable VIDEOHWACCEL in the Makefile and add CONFIGURE_ARGS+=--disable-opengl somewhere? >> It sounds like an upstream bug so it >> would be good to collect a few details like why it happens on your >> system bug I cannot reproduce it here with Intel graphics. > > Please re-read what I said. The host machine (running the > virtualboxes) has NO graphics of any kind. It's FreeBSD > 8.1-STABLE/amd64 hooked up to a VT320 terminal as a serial console. > It has X11 libraries and the various toolkits (QT etc) installed, but > no Xorg server (other than Xvnc), no X11 drivers > (graphics/keyboard/mouse). > > 3.2.8 was fine > 3.2.8_1 broke things > 3.2.10 (unsurprisingly) hasn't changed -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Fri, Oct 22, 2010 at 5:04 PM, Ade Lovett wrote: > > On Oct 22, 2010, at 16:21 , Bernhard Froehlich wrote: > > Could you please post that errors? > > freebsd% setenv DISPLAY remote:0 > freebsd% VirtualBox > > Wait for UI to pop up, click on 'Settings' for any virtual host, VirtualBox > crashes with: > > Qt WARNING: QGLContext::makeCurrent(): Cannot make invalid context current. > Segmentation fault > > > (remote) in this case has been (so far): > > MacOSX 10.6 with Apple's X11.app > MacOSX 10.6 with XQuartz.app > Windows XP with cygwin/X > Windows 7 with cygwin/X > Xvnc on the FreeBSD box, then using either the Mac or Windows box to fire > up a vnc client to get to the Xvnc. > > > > It sounds like an upstream bug so it > > would be good to collect a few details like why it happens on your > > system bug I cannot reproduce it here with Intel graphics. > > Please re-read what I said. The host machine (running the virtualboxes) > has NO graphics of any kind. It's FreeBSD 8.1-STABLE/amd64 hooked up to a > VT320 terminal as a serial console. It has X11 libraries and the various > toolkits (QT etc) installed, but no Xorg server (other than Xvnc), no X11 > drivers (graphics/keyboard/mouse). > > 3.2.8 was fine > 3.2.8_1 broke things > 3.2.10 (unsurprisingly) hasn't changed > I can confirm this issue, I reported it on the emulation mailing list a few days ago. Thanks for finding the exact breakage point. -- Adam Vande More ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Oct 22, 2010, at 16:21 , Bernhard Froehlich wrote: > Could you please post that errors? freebsd% setenv DISPLAY remote:0 freebsd% VirtualBox Wait for UI to pop up, click on 'Settings' for any virtual host, VirtualBox crashes with: Qt WARNING: QGLContext::makeCurrent(): Cannot make invalid context current. Segmentation fault (remote) in this case has been (so far): MacOSX 10.6 with Apple's X11.app MacOSX 10.6 with XQuartz.app Windows XP with cygwin/X Windows 7 with cygwin/X Xvnc on the FreeBSD box, then using either the Mac or Windows box to fire up a vnc client to get to the Xvnc. > It sounds like an upstream bug so it > would be good to collect a few details like why it happens on your > system bug I cannot reproduce it here with Intel graphics. Please re-read what I said. The host machine (running the virtualboxes) has NO graphics of any kind. It's FreeBSD 8.1-STABLE/amd64 hooked up to a VT320 terminal as a serial console. It has X11 libraries and the various toolkits (QT etc) installed, but no Xorg server (other than Xvnc), no X11 drivers (graphics/keyboard/mouse). 3.2.8 was fine 3.2.8_1 broke things 3.2.10 (unsurprisingly) hasn't changed -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox UI and remote X clients
On Fri, 22 Oct 2010 15:02:20 -0500, Ade Lovett wrote: > Folks, > > It would appear that ever since 3.2.8_1 of virtualbox-ose, a number > of additions were made to unconditionally enable some kind of hardware > acceleration in the UI. > > This completely breaks the UI with a variety of QT errors, when > running on a remote X11 displays, so far I've tested X11.app and > XQuartz.app on OSX, cygwin/X on Windows 7/XP, and even an Xvnc server > running on a FreeBSD/amd64 box. Could you please post that errors? It sounds like an upstream bug so it would be good to collect a few details like why it happens on your system bug I cannot reproduce it here with Intel graphics. Do you probably have nvidia graphics or anything special? Maybe the bug you are hitting was already fixed upstream so could you test the virtualbox-ose-devel port [1] and see if the problem persists? Sure we could make an option for that patch or revert it but that won't fix the underlying problem that it uncovered. So I would really like to get it at least analyzed first and if it cannot get fixed we can always disable it. [1] http://svn.bluelife.at/nightlies/virtualbox-port.tar.gz -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Virtualbox UI and remote X clients
Folks, It would appear that ever since 3.2.8_1 of virtualbox-ose, a number of additions were made to unconditionally enable some kind of hardware acceleration in the UI. This completely breaks the UI with a variety of QT errors, when running on a remote X11 displays, so far I've tested X11.app and XQuartz.app on OSX, cygwin/X on Windows 7/XP, and even an Xvnc server running on a FreeBSD/amd64 box. It looks like it was this commit: revision 1.27 date: 2010/09/30 12:51:00; author: decke; state: Exp; lines: +2 -0 - Add 2D acceleration support for Windows Guests - Bump PORTREVISION This needs to be made into an OPTION (default on or off, I don't care), but as it stands, the UI is unusable on apparently anything but a local X11 display -- which most machines, holding a number of vbox images, are unlikely to have. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
