[WBEL-users] installing WBEL on a UML guest

[A Streetcar Named]

I'm trying to install WBEL by following the steps listed at
http://marc.theaimsgroup.com/?l=user-mode-linux-user&m=108372798531039&w=2
but the actual package installation doesn't seem to be taking place -
instead, it just eats all CPU on my host machine.  Any ideas?

The only real deviation from the listed steps are:
* I'm doing an ftp install from my local mirror
* I'm providing networking on the guest machine using tuntap and
iptables masuerading.
Networking seems to work fine, and it is able to download the catalogs
etc. correctly from my mirror, so I don't suspect any problems on this
front.

After running "linux mem=128M fakehd fake_ide ubd0=rootfs
con0=fd:0,fd:1 root=620 ubd=3 ramdisk_size=16384 con1=pts con2=pts
con3=pts con4=pts con5=pts eth0=tuntap,tap0 initrd=wbel.bootdisk", I
ran through network configuration, disk partitioning (auto
partitioning), misc configuration (selected server, lilo on MBR,
firewall, standard US english, singapore time zone) and package
selection (text based internet, administration tools, ) as discussed
in Peter's steps.  After formatting my file systems, it just froze and
ate all my cpu cycles without doing anything.

On one console, it had this:
<7>eth0: no IPv6 routers present
<4>Unable to identify CD-ROM format.
<4>Unable to identify CD-ROM format.
<4>VFS: Can't find ext2 filesystem on dev loop(7,0).
<6>Serial line 1 assigned device '/dev/ptyp0'
<6>Serial line 2 assigned device '/dev/ptyp1'
<6>Serial line 3 assigned device '/dev/ptyp2'
<6>Virtual console 5 assigned device '/dev/pts/16'
<6>Adding Swap: 262136k swap-space (priority -1)
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3 FS 2.4-0.9.19, 19 August 2002 on fake(3,2), internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3 FS 2.4-0.9.19, 19 August 2002 on fake(3,1), internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>Virtual console 1 assigned device '/dev/pts/17'

On another console, it had this:
...
* using esound-1:0.2.28-5.1.i386 to satisfy libesd.so.0
* using libxslt-0:1.0.33-1.i386 to satisfy libxslt-1.0.19
* using gnome-mime-data-0:2.2.0-1.i386 to satisfy gnome-mime-data-2.0.0-11
* using fam-0:2.6.8-9.i386 to satisfy libfam.so.0
* using libIDL-0:0.8.0-9.i386 to satisfy libIDL-0.7.1
* FIXME: had dependency problems.  resolved them without informing the user
* moving (1) to step confirminstall
* moving (1) to step install
* moving (1) to step enablefilesystems
* mounting filesystems
* going to mount /tmp/hda2 on /mnt/sysimage
* going to mount /tmp/hda1 on /mnt/sysimage/boot
* going to mount none on /mnt/sysimage/dev/pts
* going to mount none on /mnt/sysimage/proc
* moving (1) to step migratefilesystems
* moving (1) to step setuptime
* moving (1) to step preinstallconfig

Other consoles were empty, and there were no apparent consoles that
would give me a shell.  What step normally happens after this on a
regular WBEL install?  In general, how do I find out where it is being
stuck?  Peter also hinted at problems once "the installer got to the
meaty bits of acutally installing rpms", and he believes the rpms
won't install unless lilo is selected - is the install process known
to be fussy?

This happens on two kernels I tried - 2.4.24-1um (direct from debian
testing's current user-mode-linux package) as well as a vanilla 2.4.26
kernel I compiled with the uml-patch-2.4.26-1.bz2 patch (kernel config
available if you think it would help).

Much obliged if Peter or someone else can throw me a bone :)