From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M9k1F-0003ar-Kx for qemu-devel@nongnu.org; Thu, 28 May 2009 14:07:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M9k1B-0003aO-Q9 for qemu-devel@nongnu.org; Thu, 28 May 2009 14:07:57 -0400 Received: from [199.232.76.173] (port=59358 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9k1B-0003aL-Jm for qemu-devel@nongnu.org; Thu, 28 May 2009 14:07:53 -0400 Received: from main.gmane.org ([80.91.229.2]:33479 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M9k1A-00079J-Er for qemu-devel@nongnu.org; Thu, 28 May 2009 14:07:52 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M9k16-0001qD-OT for qemu-devel@nongnu.org; Thu, 28 May 2009 18:07:48 +0000 Received: from 143.166.197.6 ([143.166.197.6]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 May 2009 18:07:48 +0000 Received: from Charles_Duffy by 143.166.197.6 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 May 2009 18:07:48 +0000 From: Charles Duffy Date: Thu, 28 May 2009 13:07:47 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: news Subject: [Qemu-devel] Global -snapshot not working where -drive ..., snapshot=on is fine List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Howdy. Running qemu-kvm-0.10.4, I'm observing -snapshot to fail in conjunction with -drive in cases where either creating a new qcow2 backing store with qemu-img or using -drive ...,snapshot=on succeeds. I'm trying to do a read-only mount of a disk image in need of ext3 journal recovery. Running without any snapshot support (with filesystem-level permissions allowing only read-only access to the disk), an (expected) failure occurs when trying to write to the disk: > EXT3-fs: INFO: recovery required on readonly filesystem. > EXT3-fs: write access will be enabled during recovery. > kjournald starting. Commit interval 5 seconds > EXT3-fs: recovery complete. > hda: dma_timer_expiry: dma status == 0x21 > hda: DMA timeout error Running with snapshot support enabled globally via -snapshot also fails with a timeout, this one happening earlier during drive detection: > ide1 at 0x170-0x177,0x376 on irq 15 > hda: max request size: 128KiB > hda: 2016 sectors (1 MB) w/256KiB Cache, CHS=2/16/63, (U)DMA > hda: cache flushes supported > hda:<4>hda: dma_timer_expiry: dma status == 0x61 > hda: DMA timeout error Running against a writable qcow2 image backed by da.qcow2 works, as does setting snapshot=on as part of the -drive specifier for da.qcow2. Any ideas? The full command line in use looks like the following: /usr/bin/qemu-kvm \ -drive file=da.qcow2 \ -m 384 \ -no-reboot \ -kernel /usr/lib64/guestfs/vmlinuz.centos-5.x86_64 \ -initrd /usr/lib64/guestfs/initramfs.centos-5.x86_64.img \ -append 'panic=1 console=ttyS0 guestfs=10.0.2.4:6666' \ -nographic \ -serial stdio \ -net channel,6666:unix:/tmp/libguestfsCgbezn/sock,server,nowait \ -net user,vlan=0 -net nic,model=virtio,vlan=0