From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU with KNOPPIX
Date: Thu, 26 Aug 2004 02:34:00 -0700 [thread overview]
Message-ID: <1093512840.27729.849.camel@aragorn> (raw)
In-Reply-To: <20040826.165738.48522976.k.suzaki@aist.go.jp>
On Thu, 2004-08-26 at 00:57, Kuniyasu Suzaki wrote:
> Yes, root File System of KNOPPIX is stored to a compressed loop-back
> device. It is called "CLOOP". KNOPPIX has boot option to move CLOOP file
> to hard disk or RAM disk. It takes time to boot, but response makes
> better.
>
> But I think the option is not valuable on QEMU. It makes slow boot on QEMU.
> To make short-cut of boot is most important.
>
How long does it take to transfer the CLOOP file to hard disk?
I would think that you could do it just once, say and drop it in My
Documents, or wherever the user wants, with a pointer to the file in the
registry. Don't have the virtual machine do it (that's slow), have the
script that starts QEMU copy the file to the host's hard disk before
running QEMU. Also put a version number there. Then read some version
number off the Knoppix disk... if they match, and the file is already on
the hard drive don't copy it again. So you get a one-time hit, for
hopefully a big performance gain and the user won't see it again until a
new version of knoppix-qemu-win comes out (BTW, what is a good name for
this? kqw? something short... I actually registered a domain when I
thought of this possibility sometime back, "linsitu" if that makes any
sense to anyone...)
Might be a cool, general way to do this transparently in QEMU. What if
there was a option/feature in QEMU, that as it reads from a CD-ROM, it
builds a cache of it on the hard disk. Maybe it saves some unique info
from cd, and the hash for some random blocks. Then when QEMU is started
again with the same disk, it hashes those blocks and decides whether it
already has cached any/all of that cd on hard disk. If it has it reads
from cache of that cd on hard disk. Then you would have something that
could work with any bootable linux cd without any tweaking.
But booting a suspended image will probably save a lot of time so either
one is worth some focus.
I don't think the QEMU engine itself is off the hook either. There are
definitely things that could be squeezed there, the question is, is
there any low-hanging fruit which would provide a measurable performance
gain...
-- John.
next prev parent reply other threads:[~2004-08-26 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 7:09 [Qemu-devel] QEMU with KNOPPIX Kuniyasu Suzaki
2004-08-25 10:02 ` John R. Hogerhuis
2004-08-26 5:19 ` Kuniyasu Suzaki
2004-08-26 6:13 ` John R. Hogerhuis
2004-08-26 7:57 ` Kuniyasu Suzaki
2004-08-26 9:34 ` John R. Hogerhuis [this message]
2004-08-27 5:58 ` Kuniyasu Suzaki
2004-08-26 11:41 ` Johannes Schindelin
2004-08-26 12:56 ` Piotr Krysik
2004-08-26 15:49 ` Johannes Schindelin
2004-08-27 6:06 ` Kuniyasu Suzaki
2004-08-27 8:35 ` Piotr Krysik
2004-08-27 10:08 ` Johannes Schindelin
2004-08-27 17:00 ` Cloop-Driver, was " Johannes Schindelin
2004-08-27 20:40 ` Juergen Lock
2004-08-29 13:52 ` Johannes Schindelin
2004-08-30 4:32 ` coLinux and " Kuniyasu Suzaki
2004-08-27 22:32 ` Fabrice Bellard
2004-08-27 22:40 ` Fabrice Bellard
2004-08-28 3:53 ` Kuniyasu Suzaki
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=1093512840.27729.849.camel@aragorn \
--to=jhoger@pobox.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).