[LINUX] HOW-TO create a XBMC server for diskless PXE network booting clients - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Announcements, Info, and General Discussion (/forumdisplay.php?fid=85)
+--- Forum: Tips, tricks, and step by step guides (/forumdisplay.php?fid=110)
+--- Thread: [LINUX] HOW-TO create a XBMC server for diskless PXE network booting clients (/showthread.php?tid=83840)
- opdenkamp - 2010-12-14 18:32
the provisioning process does the following things on the client:
- if a file /home/xbmc/.provisioned exists, bail out
- look for a file named default.tar.bz2 on the nfs share (on your server, it'll be /var/lib/xbmc-diskless/overlay/provision/default.tar.bz2). if it exists, extract it's contents in /home/xbmc
- look for a file named XX.tar.bz2 (where XX is the nic's mac address without colons) and extract it
- create the file /home/xbmc/.provisioned
I want to distribute some advancedsettings.xml to each client. On my server, I created a dir /var/lib/xbmc-diskless/provision/default/.xbmc/userdata and I put the advancedsettings.xml in there.
On one client, I got an old irman infrared receiver, which needs a specific lirc config.
The lirc config is placed in /var/lib/xbmc-diskless/provision/[mac of client]/config/lirc/hardware.conf. The xbmc config for the receiver went to /var/lib/xbmc-diskless/provision/[mac of client]/.xbmc/userdata/Lircmap.xml.
Now I run xbmc-diskless.sh and choose "provision" which creates the archives. The files will then be distributed to each new client. The "default" file is distributed to all clients and in the next step the client specific ones are copied. The latter can overwrite the first.
It's a bit complicated at the moment, but I got some plans for it for the next version that will make it easier.
About the pvr addons: please provide a full debug log via pastebin.
- ErAzOr2k - 2010-12-22 19:30
does diskless server also include tvheadend? or am i able to include this?
- opdenkamp - 2010-12-22 20:54
it's not included by default, but you can just "sudo apt-get install hts-tvheadend" to install it on your server.
- ErAzOr2k - 2010-12-28 01:58
today i tried to setip diskless xbmc.
i used the dchpproxy method to boot xbmc via lan.
but now i have the problem, that xbmc just loads and loads and loads on the booting screen.
which logs should i check to see what's wrong?
other question: is it normal, that the xbmc logo on booting screen is in black&white?
hope you understand my problem ;D
- ErAzOr2k - 2010-12-28 20:34
with sudo xbmc-diskless.sh check i get the following output:
Loading the default configuration
Checking your configuration:
image present: yes
inetd running: yes
tftpd running: yes
tftpd (69) listening: yes
nfsd running: NO - clients will not be able to persist data
mountd running: NO - clients will not be able to persist data
statd running: yes
portmap running: yes
/etc/exports has overlay: yes
portmap (111) listening: yes
nfs (2049) listening: NO - clients will not be able to persist data
- opdenkamp - 2010-12-28 23:35
the boot logo should be black&white indeed.
clearly nfs is not running for some reason.
if it still doesn't work, do you see any error in /var/log/daemon.log?
- ErAzOr2k - 2010-12-28 23:42
i figured it out.
problem was in /etc/exports.
it was like:
and i changed it now to:
now erverything is on yes in the check.
but my client still hangs on xbmc booting screen
- mason - 2010-12-29 08:48
try and remove the quiet and splash command from the following line in var/lib/tftpboot/pxelinux.0
Quote:DEFAULT vmlinuz ro initrd=initrd.img nbdroot=192.168.64.1 nbdport=2000 xbmcdir=nfs=192.168.64.1:/var/lib/xbmc-diskless/overlay xbmc=autostart probe_mask=4 vga=0x361 quiet splash
then you should see whats going on!
- ErAzOr2k - 2010-12-29 18:41
in this file are only cryptical characters :/
- ErAzOr2k - 2010-12-29 18:49
ok i found the line.
correct file was
my clients hangs on:
mounting the NBD root...
Connection: connection timed out
few lines above my client seems to lease ip 192.168.1.31 without errors. but the ip is already used by a other client. i think that's the problem :/