[Bug 524893] Re: Can't boot initramfses
** Changed in: linux (Ubuntu Lucid) Milestone: ubuntu-10.04-beta-1 = ubuntu-10.04-beta-2 ** Summary changed: - Can't boot initramfses + versatile: Can't boot initramfses ** Changed in: linux (Ubuntu Lucid) Status: New = Triaged -- versatile: Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
Reopening the bug since: - the patch was just a workaround to support the RAMDISK method, but doesn't fix initramfs support - it actually doesn't work even with the patch :-( qemu-system-arm -m 256 -drive file=lucid.img,media=disk -M versatilepb -cpu cortex-a8 -kernel linux-image-2.6.32-16-versatile_2.6.32-16.24/boot/vmlinuz-2.6.32-16-versatile -initrd initrd.gz -append 'rootdelay=20 root=/dev/ram0 console=ttyAMA0,115200' -nographic [...] [1.752156] type=2000 audit(0.495:1): initialized [1.817340] Trying to unpack rootfs image as initramfs... [1.824094] rootfs image is not initramfs (junk in compressed archive); looks like an initrd [1.876329] Freeing initrd memory: 3640K [...] [ 25.265275] md: ... autorun DONE. [ 25.270878] RAMDISK: Couldn't find valid RAM disk image starting at 0. [ 25.291694] List of all partitions: [ 25.292090] 0b00 1048575 sr0 driver: sr [ 25.292315] 0800 1331200 sda driver: sd [ 25.292514] No filesystem could mount root, tried: ext3 ext2 ext4 cramfs fuseblk [ 25.292991] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) [...] It might be that our vmlinuz is so big that it clobbers the initramfs space on unpack; I can't load vmlinux though (bug #534324) so can't easily confirm. ** Changed in: linux (Ubuntu Lucid) Status: Fix Released = New -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
@Dustin: I'd love if you could assist on this bug; to reproduce, boot: http://ports.ubuntu.com/ubuntu-ports/dists/lucid/main/installer-armel/current/images/versatile/netboot/ with qemu-system-arm -M versatilepb -cpu cortex-a8 -m 256 -kernel vmlinuz -initrd initrd.gz what you will probably see is: [1.866499] Trying to unpack rootfs image as initramfs... [1.875076] rootfs image is not initramfs (junk in compressed archive); looks like an initrd [...] [5.347930] RAMDISK: Couldn't find valid RAM disk image starting at 0. which means that the initramfs support doesn't work. (I also tried with a gunzipped initrd to no luck) We want initramfs support as on the other plaforms, but that doesn't work for an unknown reason; apparently this work on real hardware, so likely specific to the qemu ARM loader. NB: the latest linux upload has CONFIG_CRAMFS=y on armel, so the RAMDISK is likely to become mountable as an initrd; that's not what we want, but it's a good workaround for now... -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
** Changed in: qemu-kvm (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: qemu-kvm (Ubuntu Lucid) Status: New = In Progress -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
Loic- I'm a bit unclear on how to reproduce this bug. If you're looking for me to assist with it, please provide a bit more information on how I might reproduce it. If, instead, this is your own stream of conscious notes and you're working on it, then that's fine too (I often use LP in that way ;-). -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
** Changed in: linux (Ubuntu Lucid) Milestone: lucid-alpha-3 = ubuntu-10.04-beta-1 -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
Since this works on other platforms such as imx51, I suspect it's a qemu bug; I've sent a patch to the ubuntu kernel-team list to set CONFIG_CRAMFS=y and bump the default ramdisk size to 64 MB as on the other platforms as a workaround for now. ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: New = In Progress ** Changed in: linux (Ubuntu) Milestone: None = lucid-alpha-3 ** Changed in: linux (Ubuntu) Assignee: Bryan Wu (cooloney) = Loïc Minier (lool) -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
@Bryan: I hope you can help me debug the qemu loader issue; I'm not familiar with the contents of initrd versus initramfs, so I don't understand the failure. ** Changed in: qemu-kvm (Ubuntu) Assignee: (unassigned) = Bryan Wu (cooloney) ** Also affects: linux (Ubuntu Lucid) Importance: Low Assignee: Loïc Minier (lool) Status: In Progress ** Also affects: qemu-kvm (Ubuntu Lucid) Importance: Undecided Assignee: Bryan Wu (cooloney) Status: New -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
The initramfs image is an optionally gzipped cpio archive (which must have been built with cpio --format=newc in order for the kernel to recognise it --- note this is not the default behaviour for cpio). The filesystem is unpacked into a ramfs or similar, so there is no special size restriction. The first user process to run in the initramfs is usally /init I believe. [ 1.846490] rootfs image is not initramfs (junk in compressed archive); looks like an initrd The kernel always falls back to assuming initrd if the ramdisk image doesn't look like a cpio archive (which is just a whole filesystem image which is dumped into a ramdisk block device, which must be big enough, and mounted). If the initramfs image was built by hand, it might have been built wrongly; otherwise I guess there may be a kernel or qemu problem, or the image is truncated etc. -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524893] Re: Can't boot initramfses
@Dave: Ack, I understand the same as you do so far. The initramfs is the output of building the debian-installer packages, and it allows setting in which format you want that file; I've put initramfs explicitly and checked the code which does call cpio -H newc back then, so I confirm that it's created correctly. I've submitted a patch to add CONFIG_CRAMFS=y to make use of the fallback you mention (initrd in ramdisk block device) while we figure out what's wrong with initramfs. I agree with you it's either a kernel or qemu bug, but given that I saw initramfs unpacking work on real imx51 boards' dmesgs (in other bug reports), I tend to believe it's a qemu issue, but I don't know enought of the format to look into it. Thanks, -- Can't boot initramfses https://bugs.launchpad.net/bugs/524893 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
