qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice.bellard@free.fr>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Snapshot block device support
Date: Wed, 02 Jul 2003 11:49:17 +0200	[thread overview]
Message-ID: <3F02AA9D.1030307@free.fr> (raw)
In-Reply-To: 20030702065122.0DAD72C0D3@lists.samba.org

I had plans to implement "copy on write" disk images...I find your 
approach original. My initial plan was just to add a second disk image 
for each disk containing the changes. It should be easy to do it from 
your code (for example by adding options '-hdacow file' where file is 
the snapshot file you use).

About IDE, it is working (at least with kernel 2.4.20). Someone has even 
compiled a linux kernel inside QEMU (slowdown factor of about 15), so vl 
begins to be usable for real tasks. There are still known problems if 
several processes use floating point at the same time.

Fabrice.

Rusty Russell wrote:
> Hi Fabrice,
> 
> 	I haven't got the IDE emulation to work for me yet (is it
> supposed to yet?), but this allows the "-snapshot" option and "C-a s"
> to commit the disks.  The blocks which change are committed to backing
> store, and a bitmap of changed blocks is kept.
> 
> Diff + new test file below.
> Rusty.

  reply	other threads:[~2003-07-02  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02  6:50 [Qemu-devel] [PATCH] Snapshot block device support Rusty Russell
2003-07-02  9:49 ` Fabrice Bellard [this message]
2003-07-02 10:04   ` [Qemu-devel] " Thomas Glanzmann
2003-07-02 23:54   ` Rusty Russell
2003-07-04 14:51     ` Fabrice Bellard
2003-07-06  2:26       ` Rusty Russell
2003-07-06 14:08         ` Fabrice Bellard
2003-07-07  8:15           ` Rusty Russell
2003-07-07 12:51             ` Fabrice Bellard

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=3F02AA9D.1030307@free.fr \
    --to=fabrice.bellard@free.fr \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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).