Hi, i followed your documentation and i created some VM and i installed LTSP.
But now i don't understand how function the system:
- client boot on network
- ltsp login with ldm
- automatically run the vm script gui?

Thank you

Ghido

The clients boot thanks to the LTSP architecture.
It's about a network boot actually. LTSP maybe rather demanding to setup, so you first have to look at the LTSP documentation.

Once a thin client has finished to boot, you will see your *dm (e.g. kdm) login manager.

The vm script gui will be managed directly once the WM has been started.

Ok, i finish the boot and i see ldm (my login manager).
Now i login on ltsp server and then?
i have 4 vm already running.

i'm sorry, but i don't understand the process:
1 network boot (dhcp - tftp ltsp)
2 start all vm
3 ldm login
4 start vmlanch for choose vm and desktop
5 use the vm with ssh

it's correct?

Thank you

Ghido

ghido wrote:
Ok, i finish the boot and i see ldm (my login manager).
Now i login on ltsp server and then?
i have 4 vm already running.
Once your thin client has booted you can use LTSP of course, and you should be able to use VMs too. But that's a XEN issue on the server side. See our documentation for further details.

ghido wrote:

i'm sorry, but i don't understand the process:
1 network boot (dhcp - tftp ltsp)
2 start all vm
LTSP and XEN are both on the server side isn't it? So they are managed both by the server, at the same "level". You have LTSP and XEN for the virtual machines. At this point you have to use LTSP to spread virtual machines graphical sessions. This is described too in our documentation. The concept is that you start your VM and then project the Windows Manager on a thin client either using Xorg or using VNC protocol.

ghido wrote:

3 ldm login
4 start vmlanch for choose vm and desktop
5 use the vm with sshThe VM should be used via ssh only by administrators. As I told you before, users have to use VMs on thin clients in a transparent way.

ghido wrote:

it's correct?

Thank you

Ghido
That's it! Apart of the corrections I've made on your procedure.

flavio wrote:
Once your thin client has booted you can use LTSP of course, and you should be able to use VMs too. But that's a XEN issue on the server side. See our documentation for further details.
Ok when the finish boot process i see ldm login manager.
when i log in i have e xterm console.

flavio wrote:

LTSP and XEN are both on the server side isn't it? So they are managed both by the server, at the same "level". You have LTSP and XEN for the virtual machines. At this point you have to use LTSP to spread virtual machines graphical sessions. This is described too in our documentation. The concept is that you start your VM and then project the Windows Manager on a thin client either using Xorg or using VNC protocol.

LTSP and XEN are on the same server.
But i don't understand how run automatically the VM after the login manager
launching ./lanchVM in /home/user ??

i'm sorry for my insistence but i'm very interested to vdd project for sobstitute my ltsp server.

Ghido

Just to be more precise, after you login from your thin client on ldm, you should have a fully operating windows manager, like if you was on the LTSP server, and not only a xterm console. You are doing a remote login into the central ltsp server actually.

The virtual machines are already up and running when you launch the script, but about this script and its utilisation I'll ask to my colleague in order to be more precise and I will let you know. I look forward that he will participate in this thread.

ghido wrote:

i'm sorry for my insistence but i'm very interested to vdd project for sobstitute my ltsp server.
No problem, but note that vdd doesn't substitute LTSP!!! Both LTSP and XEN (more generally the virtualization itself) are fundamental for VDD to be operating. So, it's a nonsense to say i'm very interested to vdd project for substitute my ltsp server. I hope I clarified your misunderstanding.