> Yes I discovered this. If I set EROS_FD to /dev/fd0, I can "make
> ztstflop" without any problems and I can then boot another machine
> with the disk, however the boot up process stops after the following
> Your cpu type is 5 (GenuineIntel)
> Could not reserve log space for node
> current thread 0x01092ee0 (Running) ctxt 0x01061590 (user)
> uobj 0x00000018 cnt=0 0x0000000000001605
> Stopped at 0x00105b14 0x105b14: movl %ebp,%esp
Which directory are you doing "make ztstflop" in? I suspect that what is going on is that the image in question is simply too small to run.
> If I type continue at the debugger prompt, it will run until it
> stops at a checkpoint and typing continue a second time appears
> to put it into an infinite loop. Is this behaviour correct? What
> does the message about not being able to reserve log space mean?
Well, I won't say it's correct but it's about what I'ld expect. What's going on is that you have a system image that is too small for the computation to make any progress. I build such images occasionally for the purpose of testing the checkpointer.
Sorry about botching your name, by the way. I'ld just been responding to someone named Andrew, and experienced a "stuck at" condition.
Thanks for the help, Anthony.