[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: qemu bugs with initramfs (thinks initramfs is an initrd)
From:       "Matthew Franz" <mdfranz () gmail ! com>
Date:       2007-04-28 21:54:15
Message-ID: 33acb3db0704281454q56e18369k193a6c082293e8c () mail ! gmail ! com
[Download RAW message or body]

Thanks. It must be a bug the -initrd option (or initrd processing,
more likely) for Qemu because I created an .iso and boot with -cdrom
(using isolinux) and the exact same initrd/kernel combo works just
fine.

- mdf

On 4/28/07, Denis Vlasenko <vda.linux@googlemail.com> wrote:
> On Monday 23 April 2007 03:15, Matthew Franz wrote:
> > I know this is isn't a busybox issue but I imagine some folks on the
> > list are using qemu for testing/debugging.
> >
> > Anyone else seen this before with qemu
> >
> > checking if image is initramfs...it isn't (bad gzip magic numbers);
> > looks like an initrd
> >
> > and then boot hangs...
> >
> > The exact same initramfs and kernel on real hardware (booted with
> > pxelinux) works just fine...
>
> I have an image which hangs on qemu but boots just fine in virtualbox
> (www.virtualbox.org). It said to be qemu derived and GPLed.
> Give it ia try. If it works, then it's probably qemu problem/bug.
>
> (You will need a small program to convert raw disk image
> into vbox's one. Google for it).
> --
> vda
>


-- 
Matthew Franz
http://www.threatmind.net/
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]