thanks for the bug report! On Wed, Mar 11, 2009 at 06:29:32PM -0300, Gustavo Lima wrote: > 1. Xen dom0 running on lenny amd64 with 12 vlan interfaces > 2. domU running lenny amd64 with 12 network interfaces, bridged on those > vlans, running dhcp server on almost all networks > 3. On the same domU where dhcp is running I installed > ltsp-server-standalone
most of my real LTSP installs run from xen domU servers as well... though not with quite so many vlans... > 4. My dhcpd.conf for the network where the ltsp-clients are running is: > > subnet 10.1.20.0 netmask 255.255.255.0 { > authoritative; > range 10.1.20.11 10.1.20.254; > use-host-decl-names on; > option routers 10.1.20.1; > option domain-name-servers 10.1.20.57, 10.1.20.58; > option domain-name "domain.com"; > option netbios-name-servers 10.1.20.47, 10.1.20.24; > next-server 10.1.20.2; > option root-path "10.1.20.2:/opt/ltsp/i386"; > if substring (option vendor-class-identifier, 0, 9) = > "PXEClient" { > filename "/ltsp/i386/pxelinux.0"; > } else { > filename "/ltsp/i386/nbi.img"; > } > > host ws0020 { > hardware ethernet 00:50:04:E3:A9:D5; > fixed-address 10.1.20.6; > filename "ltsp/i386/nbi.img"; > } > > 5. I ran ltsp-build-client with the following sintaxe: > > ltsp-build-client --arch i386 > I followed the steps on http://wiki.debian.org/LTSP/Howto 4. Configure /etc/exports: /opt/ltsp *(ro,no_root_squash,async,no_subtree_check) is that what you have in /etc/exports ? > but didn't found /etc/lts.conf and /etc/default/ltsp-client-setup on the > system nether the docs at /usr/share/doc/ltsp-client*. Am I suposed to > install any other packages like ltsp-client? I don't believe so as the > disclaimer at the package description tells me not to do so. correct, ltsp-client should only be installed in the chroot (/opt/ltsp/i386), not on the server itself. the files you mentioned should be in /opt/ltsp/i386/etc/lts.conf and /opt/ltsp/i386/etc/default/ltsp-client-setup. i updated the wiki page to make this more clear. but your boot hasn't even gotten far enough to read those files yet. > My dhcp is running fine and tftp server either. DHCP, TFTP and NFS server are all on the same machine? they're all reachable as 10.1.20.2? > I boot my client and it gets the IP address, loads de image and right > after that starts a loop message "NFS over TCP not available from > 10.1.20.2" until it stops giving me 3 mount error messages when trying > to mount /dev, /sys, /proc and at last "No init found. Try passing init= > bootarg." what is in the file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default? it should contain a "boot=nfs" parameter. does /opt/ltsp/i386 exist on the NFS server? can you sucessfully: mount 10.1.20.2:/opt/ltsp/i386 /mnt from the server itself? from another machine on the 10.1.20.* network? do you have a firewall running on the server that may be blocking NFS traffic? what's the results of: dpkg -l nfs-kernel-server if it's installed, did you try restarting nfs-kernel-server: invoke-rc.d nfs-kernel-server restart or do you have a different nfs server installed? live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org