GNOME Bugzilla – Bug 611871
Qemu image doesn't boot
Last modified: 2013-11-14 18:12:20 UTC
The Qemu image (gnome-2.29.20100222-x86.hdd) fails to boot, showing the following: ............................. Loading /boot/initrd-2.6.30.10-4-fl.smp.gcc4.1.x86.i686.img.................... .................ready. Loading /lib/kbd/keymaps/i386/qwerty/us.map Unable to access resume device (/var/swap) exec of init (/sbin/init) failed!!!: Accessing a corrupted shared library ERROR: failed in exec of /bin/echo: Exec format error ERROR: failed in exec of /bin/sleep: Exec format error ERROR: failed in exec of /bin/sleep: Exec format error Kernel panic - not syncing: Attempted to kill init! I tried mounting the disk, chrooting into it and running mkinitrd, but I get the same error even with the new initrd.
Hi, not sure what these error means, but did you examine the checksum of the image? Run 'sha1sum gnome-2.29.20100222-x86.hdd' and compare it to the download page. If it's right, could you go into the chroot, and run 'sudo conary verify coreutils'?
I already checked the checksum, it is OK. Running 'conary verify coreutils' returns nothing.
According to another of our devs, it "either busted image or rBuilderOnline issue". I will generate a new image and test it.
Hi, Could you try the new image http://www.rpath.org/web/project/gnome/build?id=25456 from release 2.29.20100308? It runs well here.
This one doesn't boot either. I get: INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: cannot execute "/bin/sh" INIT: Id "x" respawning too fast: disabled for 5 minutes. Then it keeps repeating every 5 minutes.
Ohh... So this is another problem. I saw another user encounter it too (http://www.ogmaciel.com/?p=816&cpage=1#comment-6075). Khaled, could you paste the command with which you launched the image? My machine doesn't support virtualization so I ran 'qemu-kvm -no-kvm'. Could that make a difference? We will look into it soon, thanks for the report!
I use a plain "kvm gnome-2.29.20100308-x86.hdd" with no extra options (I edit the boot parameters in the bootloader menu removing vga= and splash to see the error messages). With "kvm -no-kvm", I still get the 'INIT: cannot execute "/bin/sh"' albeit much more slowly.
I'm the user mentioned in comment 6. I wanted to emphasize that I tried *the same image* with qemu-kvm (INIT: cannot execute "/bin/sh") and with VirtualBox (after converting the raw disk image into virtualbox format; it booted fine there). It could be a bug in qemu, maybe. I tried with qemu-kvm version 0.11.0-0ubuntu6.3 from Ubuntu Karmic.
Hello, I suppose it's more a KVM but than a GDK bug because I'm running the same image on my Fedora 11 server without any problems and I've also managed to run 'conary updateall' into it to update to the latest group build. So we should try to reproduce this bug on another physical machine to see where the bug come from ? To help us to do that, Khaled could you precise us like Marius what version of Linux distribution you are using and what version of KVM so I can test on the same versions than you. Thanks in advance for your precise reporting, Bertrand alias bertux on freenode.
(In reply to comment #9) > Marius what version of Linux distribution you are using and what version of KVM > so I can test on the same versions than you. As I said before: qemu-kvm version 0.11.0-0ubuntu6.3 from Ubuntu Karmic.
I'm running(In reply to comment #10) > (In reply to comment #9) > > Marius what version of Linux distribution you are using and what version of KVM > > so I can test on the same versions than you. > > As I said before: > qemu-kvm version 0.11.0-0ubuntu6.3 from Ubuntu Karmic. Exactly the same here.