qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] big hidden file


From: André Braga
Subject: Re: [Qemu-devel] big hidden file
Date: Fri, 25 Feb 2005 03:42:37 -0300

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 <address@hidden> 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
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]