Closed GoogleCodeExporter closed 9 years ago
mkdir /dev/shm/network is not occuring at bootup, even on the old images that
used to
work, and this prevents the instances from DHCPing. /dev/shm is mounted, so
it's not
an issue when tmpfs missing. A quick login on the terminal confirms that tests
still
pass if the network is brought up manually and sshd is restarted.
It's possible this only worked for me because I had cached images with slightly
different startup conditions, where networking worked on boot.
Original comment by drake.di...@gmail.com
on 16 Jan 2008 at 1:12
This looks like it never worked for anyone but me, and still has issues with the
template image creation. It's still broken for 0.5, and too much would need to
change and risk fixing there. Working on cbtb/uml for 0.6 only.
Original comment by drake.di...@gmail.com
on 16 Jan 2008 at 1:57
It looks like the debian archive itself changed while I was offline developing
this
installer, and that I and I alone had an image built from an older 4.0r0 CD.
Enough
has changed in the installer and related boot environment to cause the failures
I'm
seeing after debootstrap. Point releases are not supposed to be noticable like
this.
Sigh.
Dec. 26:
http://release.debian.org/stable/4.0/4.0r2/
Original comment by drake.di...@gmail.com
on 17 Jan 2008 at 12:07
When stdin to the UML binary is redirected from /dev/null and the console is
connected to fd:0, the instance boots to single-user mode, not starting
networking or
daemons. When stdin is not redirected and the exact same UML launch is used
from the
commandline, the instance will boot to full network/multi-user init state.
Removing
con=null was done as part of debugging, to see what the consoles were doing
while
booting, and turned out being the most significant cause of failure.
con=null being returned after about a week of debugging.
Original comment by drake.di...@gmail.com
on 17 Jan 2008 at 8:45
Fixed. smoketests take 4-10 minutes depending on system and whether ccache is
installed again. dnsmasq.sh may need to be set up again and tunbr reinstalled
depending on when the last install happened.
Original comment by drake.di...@gmail.com
on 17 Jan 2008 at 10:44
Original issue reported on code.google.com by
drake.di...@gmail.com
on 15 Jan 2008 at 7:54