From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC for new features
Date: Fri, 9 Jul 2004 11:34:58 +0100 [thread overview]
Message-ID: <200407091134.58693.jseward@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0407091151150.8873@wgmdd8.biozentrum.uni-wuerzburg.de>
On Friday 09 July 2004 11:02, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 8 Jul 2004, Thomas Munn wrote:
> > 1. Definately a DISK manager/compressor ala vmware disk images (so I
> > don't have to waste 4+gb if I don't have a full fileysystem!)
>
> Fabrice already mentioned that, right? I would favor using cloop devices,
> i.e. using the toolset from cloop to create compressed "devices". Knoppix
> uses this system to pack much more than 700MB on a CD.
>
> The advantage of cloop as compared to gzip'ed filesystem: Everytime you
> seek in the file, with gzip you have to either have stored a certain zlib
> state or decompress the whole file up to that point. With cloop this
> problem is solved.
I don't think it's a good idea to compress the real data in the filesystem
it reduces performance and adds complexity. All that's needed is
to modify the current cow disk system so that unused sectors don't take
any (much) space in the .cow file _without_ having to rely on filesystems
which support holes in files.
vmware (afaik) doesn't really compress disk images, at least not
compression in the gzip/zlib sense. What it does is understand the
filesystem in the disk image, so it knows where the unused sectors are,
and arranges for them to take more or less zero space in the .vmdk
file.
> The Ctrl-Shift-F2 monitor thing is a cute idea, but I really would like to
> at least optionally retain the old style monitor.
I agree it is a good idea. Mostly I just want to run WinXP without
having to have a seperate xterm for the monitor, so I vote in favour
of this one.
J
next prev parent reply other threads:[~2004-07-09 10:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 19:19 [Qemu-devel] RFC for new features Thomas Munn
2004-07-09 10:02 ` Johannes Schindelin
2004-07-09 10:34 ` Julian Seward [this message]
2004-07-09 11:27 ` [Qemu-devel] savevm handler for pckbd Johannes Schindelin
2004-07-10 13:41 ` Fabrice Bellard
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 2:41 [Qemu-devel] (Before) RFC for new features Natalia Portillo
2004-07-10 13:10 ` Fabrice Bellard
2004-07-10 14:03 ` [Qemu-devel] " Fabrice Bellard
2004-07-10 14:47 ` Antony T Curtis
2004-07-10 14:57 ` Fabrice Bellard
2004-07-08 20:50 Natalia Portillo
2004-07-08 22:48 ` Natalia Portillo
2004-07-09 19:04 ` Jocelyn Mayer
2004-07-09 19:28 ` Natalia Portillo
2004-07-08 18:14 Fabrice Bellard
2004-07-08 18:54 ` Antony T Curtis
2004-07-08 19:36 ` Jim C. Brown
2004-07-08 20:31 ` Jernej Simončič
2004-07-08 21:04 ` Jim C. Brown
2004-07-08 22:37 ` Jernej Simončič
2004-07-08 22:57 ` Jim C. Brown
2004-07-08 19:45 ` Jocelyn Mayer
2004-07-08 19:00 ` Karel Gardas
2004-07-08 21:44 ` vaise
2004-07-08 19:30 ` Jean-Michel POURE
2004-07-08 19:48 ` Brad Watson
2004-07-08 21:37 ` Jan Dittmer
2004-07-08 22:24 ` malc
2004-07-08 19:35 ` 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=200407091134.58693.jseward@acm.org \
--to=jseward@acm.org \
--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).