qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Robin Pfeifer <robinpfeifer@web.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu problem (you might be my last resort)
Date: Fri, 18 Mar 2005 10:10:16 +0100	[thread overview]
Message-ID: <423A9AF8.2010304@web.de> (raw)


Sorry for replying so late, but apparently the answer did not pass some 
spam removal utility on the part of my e-mail provider. Not all messages 
from this list are making it through. Guess I'll have to monitor the 
archives more closely.


Jim C. Brown wrote:

 > On Wed, Mar 09, 2005 at 09:06:22PM +0100, Robin Pfeifer wrote:
 >> 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.

 > "-monitor stdio" will make the monitor show up in the terminal. If the
 > monitor loads from there, try using 'info' command to see what qemu 
is > doing.

The monitor loads, but after displaying the 'type help' message doesn't 
react to input anymore, stopping / crashing along with qemu.

 >>
 >> 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.
 >>

 >You did build from source yourself, correct?

At first I used the binary package, then the official sources, then a 
daily snapshot from dad-answers.com, all with the same result. In 
between I deleted all files which I could locate with 'qemu' in them in 
the hopes of gettind rid of the error, too.

 >>
 >> 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 u add a new user, can that user use qemu (provided you don't try 
"-m 350") ?

No, I tried that yesterday, but a new user gets the same error. Root 
used not to get it when the user already did, but after using -m 350 
with root, it no longer worked for root 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.

Robin

             reply	other threads:[~2005-03-18  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  9:10 Robin Pfeifer [this message]
2005-03-18 15:45 ` [Qemu-devel] qemu problem (you might be my last resort) Jim C. Brown
2005-03-18 16:44   ` Stefan Kisdaroczi
  -- strict thread matches above, loose matches on Subject: below --
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
2005-03-09 20:06 Robin Pfeifer
2005-03-11 17:20 ` Jim C. Brown

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=423A9AF8.2010304@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).