[gentoo-user] QEMU guest fs is coming up read-only

2013-08-06 Thread Walter Dnes
  I've got a 32-bit QEMU Gentoo guest on my machine.  For some reason,
it comes up readonly, and other partitions aren't being mounted.
Unfortunately, the initial messages flash by so quickly I can't read
them to get an idea of what's going wrong.  Since /usr isn't mounted,
less isn't available.  I fired up busybox, and ran dmesg | less.
There was no hint in the output about what went wrong.

  If nothing else, is there a way to greatly slow down the QEMU boot
process so I can at least read the error messages, and have something to
work with?

-- 
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I run useful applications



Re: [gentoo-user] QEMU guest fs is coming up read-only

2013-08-06 Thread Kfir Lavi
On Tue, Aug 6, 2013 at 10:41 AM, Walter Dnes waltd...@waltdnes.org wrote:

   I've got a 32-bit QEMU Gentoo guest on my machine.  For some reason,
 it comes up readonly, and other partitions aren't being mounted.
 Unfortunately, the initial messages flash by so quickly I can't read
 them to get an idea of what's going wrong.  Since /usr isn't mounted,
 less isn't available.  I fired up busybox, and ran dmesg | less.
 There was no hint in the output about what went wrong.

   If nothing else, is there a way to greatly slow down the QEMU boot
 process so I can at least read the error messages, and have something to
 work with?

 --
 Walter Dnes waltd...@waltdnes.org
 I don't run desktop environments; I run useful applications

 Run qemu under screen with the flag -curses. Then scroll the screen up
like so:
# screen
# qemu -curses myimage.qcow2
Then use Ctrl-a ESC to enter scroll mode. PageUP will take you to the
kernel log when vm starts.

Regards,
Kfir