From: Tyler Spivey <tspivey@pcdesk.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu --curses uses large amount of memory
Date: Fri, 11 Sep 2009 07:50:48 -0700 [thread overview]
Message-ID: <20090911145048.GA16489@linux1.lan> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm using qemu 0.10.6 on linux 2.6.30. When I run:
qemu -fda floppy.img -curses
Qemu has a rss of 800mb or so. Compare this
to -nographic, which has an rss of 10 mb or so. (The
floppy I'm booting is just a bunch of zeroes, the same thing
happens if I boot a real os such as a bsd install cd).
- --
Tyler Spivey - PGP Key ID: 048C58A4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkqqY8gACgkQTsjaYASMWKRLCQCgqAqhYhyVuC36z/jmR/Uz7e1C
HAoAniRjBWCStQhfP5IoIarYl8pz31UH
=OmlE
-----END PGP SIGNATURE-----
next reply other threads:[~2009-09-11 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 14:50 Tyler Spivey [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-11 15:19 [Qemu-devel] qemu --curses uses large amount of memory Tyler Spivey
2009-09-14 22:23 ` Aurelien Jarno
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=20090911145048.GA16489@linux1.lan \
--to=tspivey@pcdesk.net \
--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).