enable the direct hardware access to the container [message #35847] |
Tue, 28 April 2009 00:46 |
Balbuzard
Messages: 26 Registered: March 2009 Location: Australia
|
Junior Member |
|
|
Hi,
I have read in the wiki-pages that the direct access to hardware is not available by default.
So is there a way to provides the direct access to the hardware nevertheless into the containers?
Thanks for your attention and your answers!
|
|
|
|
|
Re: enable the direct hardware access to the container [message #36544 is a reply to message #36523] |
Tue, 30 June 2009 05:39 |
Balbuzard
Messages: 26 Registered: March 2009 Location: Australia
|
Junior Member |
|
|
I have installed a heavy graphic application in the HN, and some non-graphic applications in VPS. But I would prefer the Graphic application to be installed in VPS instead of HN. In fact, I do not care if the graphic server or my graphic application crashes, as long as nothing else crashes with it. I need only the command line in the HN.
So, in a VPS, I have tried to install a graphic server, and a complete desktop, kde. This error has occured during the installation:No userspace software suspend support in the kernel
The current kernel doesn't support userspace software suspend> Please recompile the kernel with the 'CONFIG_SOFTWARE_SUSPEND' option.
Once the installation finished, I have tried to stop the graphic server of the HN, then start it from inside this VE, but it does not recognize the hardware support.
I think I have to provide the direct access to the hardware, to the PCI-bus to reach the graphic card.
But I have read nothing to help me with that. I have read these discussions: http://forum.openvz.org/index.php?t=tree&th=7070&mid =34390&&rev=&reveal= and http://forum.openvz.org/index.php?t=rview&goto=35314#msg _35314
Thanks a lot for your help, any kind of trick/howto will be very welcomed!
|
|
|
Re: enable the direct hardware access to the container [message #36564 is a reply to message #36544] |
Wed, 01 July 2009 05:26 |
Balbuzard
Messages: 26 Registered: March 2009 Location: Australia
|
Junior Member |
|
|
Hey,
I am still on this problem, here are some things I have tried:
I have tried to provide the VPS with the whole content of the /proc directory:umount -l /vz/root/$VEiD/proc
mount -t proc proc /vz/root/$VEID/proc
and stopped the graphic server from the HN. Then, I entered this VPS and tried to start the graphic server by the startx command. The output returns:Fatal server error:
xf860OpenConsole: Cannot open /dev/tty0 (no such file or directory) giving up.
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno3): Server error.
So I have tried to provide the /dev/tty0 device with the commandvzctl set 301 --devnodes tty0:rw --save but still the same error occurs, even after a restart of the VPS
I have no more ideas :-S
Thank you for your help!
[Updated on: Wed, 01 July 2009 05:28] Report message to a moderator
|
|
|
|
Re: enable the direct hardware access to the container [message #36577 is a reply to message #36565] |
Thu, 02 July 2009 00:42 |
Balbuzard
Messages: 26 Registered: March 2009 Location: Australia
|
Junior Member |
|
|
Hi, thanks for your answer;
I have removed /dev/tty and /dev/tty0 in my VPS; and then added them again using the commandsvzctl set $CTID --devnodes tty:rw --save
vzctl set $CTID --devnodes tty0:rw --save The shel returnssetting devices
saved parameters for CT$CTID
Then, I have shut down the graphic server, and tried to start it up again from inside the VPS, the same error message is returned.
I have noticed that the rights of /dev/tty and /dev/tty0 are not the same in the HN and in the VPS, so I have set the rights in these devices of the VPS the same way they are in the HN, but still the same error message.
Does this configuration depend on the hardware on whom the openvz kernel is installed?
Thanks!
EDIT:
I have tried to move the devices tty0 and tty in the HN. Then, when I am trying to enter the VPS, vzctl returns;Incorrect device name /dev/tty0: no such file or directory
Invalid value for DEVNODES=/tty0:rw, skipped But the devices in VPS still appear! (And the same error again while trying to execute the command startx) Maybe it can help :-S
[Updated on: Thu, 02 July 2009 01:13] Report message to a moderator
|
|
|
|
|
|
|
|