All of lore.kernel.org
 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: Fri, 04 Jul 2003 16:51:25 +0200	[thread overview]
Message-ID: <3F05946D.3060102@free.fr> (raw)
In-Reply-To: 20030703012314.9040F2C0CA@lists.samba.org

Rusty Russell wrote:
 > In message <3F02AA9D.1030307@free.fr> you write:
 >
 >> 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).
 >
 >
 > Sure: I used a temporary (unlinked) file because I couldn't see much
 > point in keeping it around.  Since most filesystems do sparse files,
 > it's quite efficient, too.
 >
 > -hdacow with an optional argument would work really well, if that's 
desired
 > behaviour.
 >
 > I'm glad I finally beat you to implementing something: you're
 > usually too quick 8)

Well, I don't have to maintain parts of the Linux kernel at the same 
time :-)

I am going to modify your patch today so that -hdacow is supported.

 >> 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.
 >
 >
 > OK, I'm getting errors with IDE on 2.5, but shouldn't be too hard to
 > track down.

I tested with 2.5.74 and fixed the initial IDE error. I also added the
emulation of the PC 'reset' pin so that vl can be shut down as a normal 
Linux system (only hard reset is supported, not power off, as it would 
require a more complicated real mode APM bios emulation).

Now I am looking for potential original uses of vl/QEMU !

Fabrice.

  reply	other threads:[~2003-07-04 14:52 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 ` [Qemu-devel] " Fabrice Bellard
2003-07-02 10:04   ` Thomas Glanzmann
2003-07-02 23:54   ` Rusty Russell
2003-07-04 14:51     ` Fabrice Bellard [this message]
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=3F05946D.3060102@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.