From: "André Braga" <meianoite@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] big hidden file
Date: Fri, 25 Feb 2005 03:42:37 -0300 [thread overview]
Message-ID: <2ad73a05022422423a539def@mail.gmail.com> (raw)
In-Reply-To: <200502242216.48534.os2@videotron.ca>
export QEMU_TMPDIR=/dev/shm
qemu [any useful custom flags here] -m 192
[or something closer to the 256MB you have available on /dev/shm; I
just like standard RAM sizes better...]
--
"I invented the term Object-Oriented, and I can tell you I did not
have C++ in mind"-Alan Kay
On Thu, 24 Feb 2005 22:16:48 -0500, Marc Collin <os2@videotron.ca> wrote:
> hi
>
> i use suse 9.2, qemu 0.62 and kqemu.
>
> in the documentation of kqemu we can read
>
> "When using KQEMU, QEMU will create a big hidden file containing the RAM of
> the virtual machine. For best performance, it is important that this file is
> kept in RAM and not on the hard disk. QEMU uses the `/dev/shm' directory to
> create this file because tmpfs is usually mounted on it (check with the shell
> command df). Otherwise `/tmp' is used as fallback. You can use the
> QEMU_TMPDIR shell variable to set a new directory for the QEMU RAM file."
>
> linux:/home/collinm/Documents/qemu/qemu # df
> Sys. de fich. 1K-blocs Occupé Disponible Capacité Monté sur
> /dev/sda5 12586488 141504 12444984 2% /
> tmpfs 253944 6484 247460 3% /dev/shm
> /dev/sda1 31077 5854 23619 20% /boot
> /dev/sdc5 35542652 4087660 31454992 12% /home
> /dev/sdb6 8393656 452956 7940700 6% /opt
> /dev/sda7 2007996 33468 1974528 2% /tmp
> /dev/sdb5 26217176 1985736 24231440 8% /usr
> /dev/sda6 3148568 472076 2676492 15% /var
>
> how to keep this file in ram?
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
prev parent reply other threads:[~2005-02-25 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 3:16 [Qemu-devel] big hidden file Marc Collin
2005-02-25 6:42 ` André Braga [this message]
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=2ad73a05022422423a539def@mail.gmail.com \
--to=meianoite@gmail.com \
--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).