On Friday 30 January 2009 07:42:22 ltsp-discuss-requ...@lists.sourceforge.net
wrote:
> posted this question on the Ubuntu forum earlier, no reply.
>
> How would I configure/build LTSP client if the boot server is not the
> same as LTSP server?
>
> Given a 64-bit computer (host) which runs several 32-bit VMs (with
> kvmadm); Ubuntu (8.04 fresh internet install with mini.iso) ltsp
> server is on one of these VMs. The host computer provides bridging, so
> all VMs are on the same subnet. The host computer also runs TFTP and
> DHCP servers. Diskless client is of course a separate PC, plugs into
> host's ethernet card which is on the same bridge with VMs.
>
> In the boot server's dhcpd.conf there is the following:
>
> host <thin client host name> {
> hardware ethernet <thin client MAC>;
> fixed-address <thin client host name with domain>;
> option root-path "<IP of Ubuntu VM>:/opt/ltsp/i386";
> }
>
> The Ubuntu VM exports /opt/ltsp/i386 via nfs. DHCP server is disabled
> on Ubuntu VM. I wouldn't really want to use the Ubuntu VM as DHCP
> server.
>
> I copied ltsp client's Linux kernel and initrd from Ubuntu VM
> (/opt/ltsp/i386/boot, vmlinuz-2.6.24-16-generic and
> initrd.img-2.6.24-16-generic)to the tftpboot directory of the host
> computer as vmlinuz-ltsp and initrd-ltsp resp. I added these lines to
> the host computer's pxelinux.cfg/default (similarly to those in the
> ltsp's pxelinux.cfg/default):
>
> label Ubuntu LTSP
> kernel vmlinuz-ltsp
> append initrd=initrd-ltsp ro quiet splash
>
> If I select this item in the client's PXE boot menu, the image starts
> booting, I see Ubuntu splash screen, but it cannot mount root because
> it tries to do that with the boot server (connection refused, as the
> host does not provide anything for this). I tried to append the "ip"
> parameter with IP if the Ubuntu VM as the second field: no effect.
> Same with "nfsroot" parameter.
>
> ifconfig shows correct IP address on client's eth0.
>
> When booting the client, I get to the shell prompt with messages that
> it cannot mount root. IP configuration shows that root server IP is
> host's IP (instead of desired Ubuntu VM's IP), and root path is as in
> dhcpd.conf, but still root cannot be mounted. I can manually mount the
> Ubuntu VM's NFS share from client's shell prompt, so there is
> connectivity.
>
> Basically all I need is to tell the client that root server is Ubuntu
> VM rather than the host. Is this DHCP deficiency, or just not assumed
> in LTSP design?
Problem 1: What are you trying to achieve
Problem 2: Why
>From My DHCP server which is not the LTSP server
It also is a tftp server, but that is of no interest or concern
host ws121 {
hardware ethernet 00:40:63:DA:67:8D;
fixed-address ws121;
filename "/ltsp/i386/pxelinux.0";
next-server 192.168.5.120;
option log-servers 192.168.5.120;
}
Now weather next-server is a VM or another box or even the same box (and yes
they ARE) nobody cares and nothing is amiss
James
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
