qemu boot failure

[0xefbeefbe]

Hi all,

I've been trying to boot a xubuntu-12.04.2 i386 vm with i386-s2e-softmmu/qemu-system-i386, but the VM fails to boot and instead I end up at the BusyBox 1.18.5 built-in shell prompt at (initramfs). The weird thing is that if I boot the image with i386-softmmu/qemu-system-i386 it boots just fine. 

I'm kinda at a loss as there doesn't seem to be a decent logging info that can help me discover what's going on. The VM doesn't boot up far enough to get dmesg info. Even with -s2e-verbose on I'm not seeing any errors. In my s2e-last folder I'm not seeing anything that would indicate an error either.

Any thoughts on how I can get some indication as to what's going on?

Regards,

Shawn

[Vitaly Chipounov]

On 08.10.2013 16:50, 0xefbeefbe wrote:

Hi all,

I've been trying to boot a xubuntu-12.04.2 i386 vm with i386-s2e-softmmu/qemu-system-i386, but the VM fails to boot and instead I end up at the BusyBox 1.18.5 built-in shell prompt at (initramfs). The weird thing is that if I boot the image with i386-softmmu/qemu-system-i386 it boots just fine.

Looks like it couldn't mount the root partition and dropped into busybox instead. What does dmesg say?

Vitaly

Regards,

Shawn

--
--
You received this message because you are a member of the S2E Developer Forum.
To post to this group, send email to s2e...@googlegroups.com
To unsubscribe from this group, send email to s2e-dev+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/s2e-dev
 
---
You received this message because you are subscribed to the Google Groups "S2E Developer Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to s2e-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[0xefbeefbe]

dmesg doesn't seem to have anything outside of the boot messages when I've booted with i386-softmmu.

[0xefbeefbe]

I was able to redirect the kernel console to a file with qemu option "-serial file=./console.txt". In the console messages I see the following:

Gave up waiting for root device. Common problems:

-Boot args (cat /proc/cmdline)

     - Check rootdelay= (did the system wait long enough?)

     - Check root= (did the system wait for the right device?)

-Missing modules (cat /proc/modules; ls /dev)

ALERT! /dev/disk/by-uuid/<big long uuid> does not exist.

Dropping to a shell!

The <big long uuid> is the actual uuid of my root partition. Inside of byusybox I ran 'exec blkid' to see which devices are available and my drive is indeed listed with the uuid matching in <big long uuid>.

After digging around on the ubuntu forums I noticed that people had to add the kernel parameter rootdelay=90 to get passed a similar issue on certain motherboards. I just tried waiting for several minutes before typing exit at the busybox prompt and the vm eventually booted. Apparently this delay allows for the hard disc to be recognized by the kernel.

I hope this helps anyone else that might come across this issue.

Regards,

Shawn

On Tuesday, October 8, 2013 1:08:02 PM UTC-4, 0xefbeefbe wrote:

dmesg doesn't seem to have anything outside of the boot messages when I've booted with i386-softmmu.

On Oct 8, 2013, at 11:46 AM, Vitaly Chipounov <vitaly.c...@epfl.ch> wrote:

On 08.10.2013 16:50, 0xefbeefbe wrote:

Hi all,

I've been trying to boot a xubuntu-12.04.2 i386 vm with i386-s2e-softmmu/qemu-system-i386, but the VM fails to boot and instead I end up at the BusyBox 1.18.5 built-in shell prompt at (initramfs). The weird thing is that if I boot the image with i386-softmmu/qemu-system-i386 it boots just fine.

Looks like it couldn't mount the root partition and dropped into busybox instead. What does dmesg say?

Vitaly

Regards,

Shawn

--
--
You received this message because you are a member of the S2E Developer Forum.
To post to this group, send email to s2e...@googlegroups.com

To unsubscribe from this group, send email to s2e-dev+unsubscribe@googlegroups.com

For more options, visit this group at http://groups.google.com/group/s2e-dev
 
---
You received this message because you are subscribed to the Google Groups "S2E Developer Forum" group.

To unsubscribe from this group and stop receiving emails from it, send an email to s2e-dev+unsubscribe@googlegroups.com.