severity 365395 important
thank
On Sat, Apr 29, 2006 at 11:48:16AM -0700, Todd A. Jacobs wrote:
> Package: user-mode-linux
> Version: 2.6.16-1um-1
> Severity: grave
> Justification: renders package unusable
it's not really unusable, severity is inappropriate IMO.
> I reported on the UML mailing list that I was unable to boot from an ISO
> image, even after various gyrations. Jeff Dike suggested that the binary
> was probably compiled without proper block support (specifically
> CONFIG_BLK_DEV_UBD, although there may be issues with ISO9660 support as
> well).
>
> Here is the actual error and command-line:
>
> $ linux mem=64M umid=debian ubd0r=debian-testing-i386-netinst.iso
You're mixing things up. You can't boot from the install image, you need
to extract the initrd from the iso [1] and boot from the initrd
[2]. Then you can proceed and install the system (you'll also have to
manually tell the installer where the cdrom is -you'll be asked during
installation, in my example you can use /dev/ubdb).
[1]: mount -o loop debian-testing-i386-netinst.iso /mnt
cp /mnt/install/2.6/initrd.gz /anywhere
[2]: linux ramdisk_size=12000 mem=128M umid=debian initrd=initrd.gz
root=/dev/ram0 ubd0=rootfs ubd1=debian-testing-i386-netinst.iso
eth0=tuntap,,,172.20.0.1
As said in the uml-devel ML I have the new package ready here, I'll
upload it tomorrow.
[...]
> Console initialized on /dev/tty0
> Initializing software serial port version 1
> ubda: unknown partition table
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(98,0)
In fact you get this same error running:
linux mem=64M umid=debian ubd0r=/dev/zero
The problem here is that netinst.iso doesn't contain a regular
filesystem to boot with. This works with regular PCs because the
bootloader helps this process (loading and running the initrd).
Thanks
--
mattia
:wq!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
