From: Robin Pfeifer <robinpfeifer@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu problem (you might be my last resort)
Date: Wed, 09 Mar 2005 21:06:22 +0100 [thread overview]
Message-ID: <422F573E.9010107@web.de> (raw)
Hello all,
I'm writing to this list because I haven't been able to locate help with
my qemu problem anywhere else (forums, google).
When I start qemu with the following command:
qemu -cdrom /dev/cdrom -boot d -snapshot -m 256
with any bootable CD in the drive, I only get a qemu window with the
tile 'qemu stopped'. I cannot get into the monitor by pressing ctrl +
alt + 2 or do anything else except ctrl + c in the terminal where I
started qemu to cancel it.
The command used to work perfectly with various versions of qemu, but
now doesn't anymore. I've tried CVS versions after 0.6.1 stopped
working, but to no avail.
the problem started when I tried to change the -m value to 350.
Apparently this is not a legal value to use (maybe only realistic RAM
levels are allowed?) - I've got 768 megs RAM, so it's not too much. The
trouble is that nothing makes the error go away - not a reboot, not
completely removing /tmp and /var and all their content, and I can't
find anything else anywhere which might cause the problem. I even
deleted all files which seemed to have anything to do with qemu
(everything with qemu in its name) and installed a fresh version, but no
luck. Just in case there was some remnant of a file somewhere blocking
things (and because I had two other defunct files I couldn't get rid of
any other way) I used reiserfsck --rebuild-tree, but still no show for
qemu. At least the two files got corrected.
At first only my user ID had the problem, and root worked - but then I
tried the -m 350 parameter with root, too, (not thinking, at the time,
that it could be the cause of the problem) and since then, root hasn't
been able to use qemu anymore either.
If I start qemu with the additional parameter -S I can still get into
the monitor, but nothing I do there has any effect - the program still
crashes as soon as I press c or enter cont.
Does anyone on this list have any suggestion what I can do?
Robin
next reply other threads:[~2005-03-09 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 20:06 Robin Pfeifer [this message]
2005-03-11 17:20 ` [Qemu-devel] qemu problem (you might be my last resort) Jim C. Brown
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 9:10 Robin Pfeifer
2005-03-18 15:45 ` Jim C. Brown
2005-03-18 16:44 ` Stefan Kisdaroczi
2005-03-20 7:01 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
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=422F573E.9010107@web.de \
--to=robinpfeifer@web.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).