Re: UML startup problems
On Mon, 2003-07-28 at 19:20, Millis Miller wrote:
> (as the uml is in testing, this seemed a good list)
>
> I am running the testing distribution, and have been having problems
> trying to get UML working.
> When I run the images on a RH machine as host, they work fine. On
> Debian, I get the following problems:
>
> - Debian image, always says that the flesystem has problems and needs
> fixing (even when copied from a vigin, working image).
>
> - RH image, complains about INIT respawning too fast and locks up. A
> subsequent kill/restart results in irrecoverably corrupted image.
>
> All this is using a stock host 2.4.18-bf24 kernel, and the latest
> testing UML packages.
>
> Error messages follow:
>
> --- Debian UML -----------
>
> jaques:/opt/uml# ./uml.sh
[...]
> Kernel command line: mem=48M ubd0=root.COW,/opt/uml/Debian-3.0r0.ext2
> eth0=tuntap,,,192.168.0.254 con=pty con0=fd:0,fd:1 root=/dev/ubd0
[...]
> 00VFS: Mounted root (ext2 filesystem) readonly.
[...]
> Checking root file system...
> fsck 1.27 (8-Mar-2002)
> fsck.ext2: No such file or directory while trying to open /dev/ubd/0
you've given root=/dev/ubd0, and VFS mounted it fine .. then fsck can't
find /dev/ubd/0 ? It'd appear your image is configured to use devfs -
mount your image with mount -o loop then edit /etc/fstab to use
/dev/ubd0 instead of /dev/ubd/0
> --------- Red Hat UML ----------------
> millis@jaques:/opt/uml$ ./uml-rh.sh
[...]
> Kernel command line: mem=48M
> ubd0=root-rh.COW,/opt/uml/root_fs.rh-7.2-server.pristine.20020312
> eth0=tuntap,,,192.168.0.254 con=pty con0=fd:0,fd:1 root=/dev/ubd0
[...]
> INIT: Id "0" respawning too fast: disabled for 5 minutes
> INIT: Id "1" respawning too fast: disabled for 5 minutes
> INIT: Id "2" respawning too fast: disabled for 5 minutes
> INIT: Id "c" respawning too fast: disabled for 5 minutes
> INIT: no more processes left in this runlevel
my only guess is that whatever it's spawning doesn't like there not
being a terminal available?
My best suggestions would be to try using "con=xterm" rather than
"con=pty con0=fd:0,fd:1" atleast for long enough to let it you login and
see what it's spawning, why it's failing, and what you can do about it.
HTH,
Shaun
Reply to: