OpenVZ Forum: Support » HowTo DRI/GLX in a ubuntu EV

Home » General » Support » HowTo DRI/GLX in a ubuntu EV

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

HowTo DRI/GLX in a ubuntu EV [message #34604]

Tue, 20 January 2009 09:36

anto_gc
Messages: 2
Registered: January 2009

Junior Member

Hello all,

I have a openvz kernel 2.6.24, OS gentoo, ev ubuntu. I have installed Xserver1.5 (passthrough DRI/GLX for Xephyr). If I try a "glxinfo" command or a "glxgears" command at my ubuntu ev the result is that I dont have DRI/GLX. What is the problem??

is possible to have DRI/GLX in the ubuntu ev?

Thanks!

P.D: another question, for when the kernel 2.6.28 (GEM for GPUs) for the openvz-kernel?

thanks

Report message to a moderator

Re: HowTo DRI/GLX in a ubuntu EV [message #34622 is a reply to message #34604]

Wed, 21 January 2009 18:44

n00b_admin
Messages: 77
Registered: July 2006
Location: Romania

Member

Please note that the OpenVZ project is targeted at server deployments.

The latest kernel are hardly deemed as stable for server environments, maybe if you detail why do you require GLX inside a VE someone, more qualified then me, could respond to your question.

On the other hand, the direct hardware interfacing required for 3D acceleration may not be possible in an OpenVZ container.

Report message to a moderator

Re: HowTo DRI/GLX in a ubuntu EV [message #41346 is a reply to message #34604]

Tue, 04 January 2011 19:47

petteriaimonen
Messages: 1
Registered: January 2011

Junior Member

Replying to this old message thread to share my findings.

I had the same need, because I want to run a HTPC setup on the same computer as I use to experiment with virtual machines.

My plan was to export /dev/dri/card0 and /dev/dri/controlD64 to the VE, and then convince DRI to use it.

First trouble was this error message from glxinfo:

X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  136 (DRI2)
  Minor opcode of failed request:  1 ()
  Serial number of failed request:  16
  Current serial number in output stream:  16

I traced it to this check in xorg/hw/xfree86/dri2/dri2ext.c:

    if (!LocalClient(client))
        return BadRequest;

Bypassing this got me a little further, but only to discover that the /dev/dri/card0 does not work in VE, even though I've set the permissions using vzctl. The other device works, though:

jpa-adm@clefairy:~$ cat /dev/dri/card0
cat: /dev/dri/card0: No such device
jpa-adm@clefairy:~$ cat /dev/dri/controlD64 
^C

I guess there is some limitation in either the DRI driver or OpenVZ that stops me from sharing the device. But even if I could, I fear that some shared memory issues might make DRI from VE impossible.

In conclusion, I think it is better to run the desktop system in a chroot on the HN, even if it is not as secure.

--
jpa

Report message to a moderator

Previous Topic:	Virtual ethernet device wiki
Next Topic:	Drive Partitioning [OT]

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Jun 22 11:07:27 GMT 2025

Total time taken to generate the page: 0.06832 seconds