Hi Jean-Vincent, Thank you for the help but this approach doesn't seem to solve the problem. Here are some more details:
1. First I ran "echo $DISPLAY" on server (IP is set to 168.18.104.142) console (which I normally cannot access since LSTP server is headless, i.e. virtualized with VMware ESXi) and I got ":0.0" which is not "localhost:7.0" as in your reply. 2. I ran the same command, i.e. "echo $DISPLAY" on thin client (IP is set to 168.18.104.251) which returned "168.18.104.251:7" so I concluded that thin client utilizes 7th display port of X11 server running on LTSP server... BTW is this correct assumption? 3. I listed magic cookies by running "xauth list". On both (LSTP server and thin client) result is the same. It lists for example: -----------------8<---------- 168.18.104.251:7 MIT-MAGIC-COOKIE-1 7a70850220f80c6ee6b3419c9f8c852c LTSP2/unix:0 MIT-MAGIC-COOKIE-1 d8cbbc217e8ba13aa429855c55928a1a -----------------8<---------- among other similar records 4. I started Marionnet and created a project with one VM. Then I started the project and waited for VM to boot up. Then I logged in and ran the following commands: -----------------8<---------- m1:~# echo $DISPLAY 172.23.0.254:0 m1:~# xauth list xauth: creating new authority file /root/.Xauthority m1:~# xauth add $DISPLAY . d8cbbc217e8ba13aa429855c55928a1a xauth: creating new authority file /root/.Xauthority m1:~# xauth list 172.23.0.254:0 MIT-MAGIC-COOKIE-1 d8cbbc217e8ba13aa429855c55928a1a m1:~# xeyes (window is shown on the virtual console of headless LSTP server, but not on the screen attached to thin client) -----------------8<---------- 5. I created, started and logged in another VM, i.e. "m2" and ran the same scenario while changing value of the $DISPLAY variable to 168.18.104.251:7and using corresponding cookie: -----------------8<---------- m2:~# echo $DISPLAY 172.23.0.254:0 m2:~# xauth list xauth: creating new authority file /root/.Xauthority m2:~# export DISPLAY=172.23.0.254:7 m2:~# xauth add $DISPLAY . 7a70850220f80c6ee6b3419c9f8c852c xauth: creating new authority file /root/.Xauthority m2:~# xauth list 172.23.0.254:7 MIT-MAGIC-COOKIE-1 7a70850220f80c6ee6b3419c9f8c852c m2:~# xeyes Error: Can't open display: 172.23.0.254:7 -----------------8<---------- 6. Finally I attempted to replicate Step 5 while creating VM named "m3" but this time I used cookie from LTSP server: -----------------8<---------- m3:~# echo $DISPLAY 172.23.0.254:0 m3:~# xauth list xauth: creating new authority file /root/.Xauthority m3:~# export DISPLAY=172.23.0.254:7 m3:~# xauth add $DISPLAY . d8cbbc217e8ba13aa429855c55928a1a xauth: creating new authority file /root/.Xauthority m3:~# xauth list 172.23.0.254:7 MIT-MAGIC-COOKIE-1 d8cbbc217e8ba13aa429855c55928a1a m3:~# xeyes Error: Can't open display: 172.23.0.254:7 -----------------8<---------- So it seems that exporting magic cookie doesn't solve the problem... Am I missing something? PS: I also tried to modify Step 4 while using cookie of thin client, but it also failed with messages: -----------------8<---------- Xlib: connection to "172.23.0.254:0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key Error: Can't open display: 172.23.0.254:0 -----------------8<---------- Looking forward to reed your response. Thank you. -- Simon On Wed, Apr 3, 2013 at 7:59 AM, <jean-vincent.lo...@lipn.univ-paris13.fr>wrote: > Hi Simon, > > It's a pleasure to answer to a well detailed question, even if the > solution is not simple. > > > 7. I assumed that having DISPLAY set to <IP of thin-terminal>:7 on >> hosting site may require setting DISPLAY from within Marionnet's host >> to 172.23.0.254:7 but it doesn't fix the problem. Actually it fixes >> (removes) the first part of the error message related to refused >> connection, so the new error message looks like: >> -----------8<---------- >> (wireshark:5076) Gtk-WARNING **:cannot open display: 172.23.0.254:7 >> > > This is reasonable, but it doesn't work. (I think that if it had been > enough, we would have introduced it in Marionnet). Actually, I think that > you have to transmit the server's X11 cookie to all virtual machines... > Suppose that you start an ssh connection from the (thin) client to the > server. In this connection, your $DISPLAY doesn't correspond to a real X11 > server (it's the ssh -X tunneling): > > server# echo $DISPLAY > localhost:7.0 > > However, this information is useful to get the related cookie: > > server# xauth list :7 > server/unix:7 MIT-MAGIC-COOKIE-1 34409ca90323311c437495112c060b**da > > Now you have to send this cookie to the virtual machine (for instance > "m1", with IP 172.23.0.1): > > m1# echo $DISPLAY > 172.23.0.254:0 > > server# ssh root@172.23.0.1 xauth add 172.23.0.254:0 . > 34409ca90323311c437495112c060b**da > root@172.23.0.1's password: > > or directly in your virtual machine: > > m1# xauth add $DISPLAY . 34409ca90323311c437495112c060b**da > xauth: creating new authority file /root/.Xauthority > > m1# xeyes # should appear on your thin client > > Best regards, > Jean-Vincent > > > On Tue, 2 Apr 2013 11:55:28 -0400, Simon Baev wrote: > >> Hello All, >> >> Background: >> -- >> I'm trying to run Marionnet in LTSP environment (ltsp.org [1]) >> >> installed >> on top of Lubuntu 12.10 (Ubuntu + LXDE) with several thin-terminals >> >> (http://www.**disklessworkstations.com/1700-**series-thin-clients.html<http://www.disklessworkstations.com/1700-series-thin-clients.html> >> [2]). >> >> This LTSP server is virtualized in VMware ESXi but it should play any >> difference. >> >> Setup: >> -- >> 1. The LTSP server has IP 168.18.104.142 and latest version of >> Marionnet installed using the script. >> 2. A thin-terminal utilizes PXE boot, gets IP address from the same >> LAN, i.e. 168.18.104..128/25 [3] and starts LDM session to LTSP >> >> server >> 3. As soon as LDM session gets authenticated on LSP server it >> (thin-terminal) starts X session so I can run Marionnet on it. In >> console of the thin-terminal I can see the value of DISPLAY which is >> set to :7 >> >> 4. When I create new project in Marionnet with at least one host and >> start up the project, it adds a NIC (one per each Marionnet's host) >> with IP address set to 172.23.0.254/255.255.255.255 [4] so I assume >> >> it is >> sort of P2P tunnel between hosting machine and a host within >> Marionnet >> environment. >> 5. Once Marionnet's host started I can check the value of its DISPLAY >> which is set to 172.23.0.254:0 [5] >> >> 6. When I try to start wireshark in Marionnet's host I'm getting >> error: >> -----------8 >> >> Links: >> ------ >> [1] http://ltsp..org >> [2] >> http://www.**disklessworkstations.com/1700-**series-thin-clients.html<http://www.disklessworkstations.com/1700-series-thin-clients.html> >> [3] http://168.18.104.128/25 >> [4] >> http://172.23.0.254/255.255.**255.255<http://172.23.0.254/255.255.255.255> >> [5] http://172.23.0.254:0 >> [6] http://172.23.0.254:0 >> [7] http://172.23.0.254:7 >> [8] http://172.23.0.254:7 >> >
_______________________________________________ Mailing list: https://launchpad.net/~marionnet-dev Post to : marionnet-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~marionnet-dev More help : https://help.launchpad.net/ListHelp
