From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19YRv9-0008Ri-97 for qemu-devel@nongnu.org; Fri, 04 Jul 2003 10:52:19 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19YRuZ-0007Cj-4K for qemu-devel@nongnu.org; Fri, 04 Jul 2003 10:51:43 -0400 Received: from smtp4.wanadoo.fr ([193.252.22.26] helo=mwinf0504.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.20) id 19YRtg-0006jU-1u for qemu-devel@nongnu.org; Fri, 04 Jul 2003 10:50:48 -0400 Message-ID: <3F05946D.3060102@free.fr> Date: Fri, 04 Jul 2003 16:51:25 +0200 From: Fabrice Bellard MIME-Version: 1.0 References: <20030703012314.9040F2C0CA@lists.samba.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] Snapshot block device support Reply-To: qemu-devel@nongnu.org List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , To: Rusty Russell Cc: qemu-devel@nongnu.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.