Hi!
Can you attach your installer syslog file?
Having .tmp in the path usually indicates that ltsp-update-image failed
somehow as its last step is to rename amd64.img.tmp to amd64.img.
How much disk space did you give your VM? At build time LTSP can use
around 1GB more than what's needed for a
Public bug reported:
Running lucid-alternate-amd64.iso (10.04.03)
Both the LTSP server and thin client (pxe boot) are able to obtain an IP
address from the internal dhcp server.
The thin client starts to connect and fails with an error unable to
locate the filename
I've tested this on kvm and v