From: Robin Pfeifer <bitpicker@compuserve.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu crashes at boot start
Date: Fri, 25 Mar 2005 22:38:59 +0100 [thread overview]
Message-ID: <424484F3.8070708@compuserve.de> (raw)
In-Reply-To: <20050321200112.GA32293@jbrown.mylinuxbox.org>
This has been discussed as 'qemu problem (you might be my last resort)',
but the new topic line is probably a little more informative. I'd like
to subsume the error once more, maybe someone has an idea who ignored
the less-informative previous title.
I am trying to boot live CDs or the freedos.img as available on the qemu
homepage. It used to work perfectly a couple of months ago, and back
then I aliassed the command
livecd='qemu -cdrom /dev/cdrom -boot d -snapshot'
When I added more RAM about a month ago, I added '-m 350' to this
command. After that, qemu wouldn't work anymore, not even when I left
out the -m parameter. Instead, qemu now immediately stops (the window
displaying 'qemu stopped' in its title) and cannot be closed with
anything other than ctrl+c in the console from which it was started. Not
even the BIOS messages turn up. Using the parameter -S I can stop the
emulation before the crash and get into the monitor, but as soon as I
enter c in order to continue the window freezes. Meanwhile I have also
tried gdb as described in the documentation, but as soon as I enter c
there, same thing: qemu window freezes.
If I use a wrong parameter so that booting fails, the BIOS messages do
appear up to the obvious point where booting cannot commence. So:
qemu -cdrom /path/to/freedos.img
boots until ' FATAL: Could not read the boot disk'
Same goes for any attempts to boot a live CD with -hda /dev/cdrom
But if I use -cdrom for /dev/cdrom or -hda for the freedos.img, I get
the freeze. Apparently qemu crashes on my system as soon as it finds
something it should be able to boot.
I have tried various dad-answers snapshots and now I have 0.6.1 again. I
have deleted all files with qemu int heir names between installations. I
have deleted the content of /tmp and even temporarily moved both /tmp
and /var somewhere else in order to check whether there might be a
temporary file blocking the process, but nothing changed anything. Qemu
is no longer working for me.
I'm grateful for any suggestions you might have.
Robin
next prev parent reply other threads:[~2005-03-25 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 7:01 [Qemu-devel] qemu problem (you might be my last resort) Robin Pfeifer
2005-03-20 16:06 ` Jim C. Brown
2005-03-20 20:49 ` Robin Pfeifer
2005-03-21 0:57 ` Jim C. Brown
2005-03-21 17:37 ` Robin Pfeifer
2005-03-21 20:01 ` Jim C. Brown
2005-03-21 21:02 ` Robin Pfeifer
2005-03-25 21:38 ` Robin Pfeifer [this message]
2005-03-25 22:04 ` [Qemu-devel] qemu crashes at boot start Antony T Curtis
2005-03-25 22:30 ` Robin Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=424484F3.8070708@compuserve.de \
--to=bitpicker@compuserve.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).