From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36696) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQxqL-0007AR-Dc for qemu-devel@nongnu.org; Wed, 24 Oct 2012 06:05:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TQxqD-0002Mf-GC for qemu-devel@nongnu.org; Wed, 24 Oct 2012 06:05:45 -0400 Received: from indium.canonical.com ([91.189.90.7]:48233) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQxqD-0002MZ-AQ for qemu-devel@nongnu.org; Wed, 24 Oct 2012 06:05:37 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1TQxqC-0000YP-PR for ; Wed, 24 Oct 2012 10:05:36 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id B6B342E8070 for ; Wed, 24 Oct 2012 10:05:36 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 24 Oct 2012 09:58:51 -0000 From: Oliver Francke Sender: bounces@canonical.com References: <20121024095851.10767.86404.malonedeb@gac.canonical.com> Message-Id: <20121024095851.10767.86404.malonedeb@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1070762] [NEW] savevm fails with inserted CD, "Device '%s' is writable but does not support snapshots." Reply-To: Bug 1070762 <1070762@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Public bug reported: Hi, yesterday unfortunately a customer reported a failed snapshot of his VM. Going through the logfile I discovered: "Device 'ide1-cd0' is writable but does not support snapshots" this is with qemu-1.2.0 and 1.0.1 at least... Why writeable? Even if I specify "-drive ...,readonly=3Don,snapshot=3Doff" to qemu the mon= itor-command sees the CD-ROM-device as being writeable?! Somewhere I saw a "hint" for blockdev.c: =3D=3D=3D snip =3D=3D=3D --- /tmp/blockdev.c 2012-10-24 11:37:10.000000000 +0200 +++ blockdev.c 2012-10-24 11:37:17.000000000 +0200 @@ -551,6 +551,7 @@ case IF_XEN: case IF_NONE: dinfo->media_cd =3D media =3D=3D MEDIA_CDROM; + dinfo->bdrv->read_only =3D 1; break; case IF_SD: case IF_FLOPPY: =3D=3D=3D snap =3D=3D=3D after installing with this small patch applied it works, so insert CD, save= vm succeeds. This should be fixed at all correct places, and the tags "readonly=3Don,sna= pshot=3Doff" should do it, too. Or even just work after specifying a drive = being a CD-rom should do the trick ;-) Another "bad habit" is, that the ISO/DVD-file has to be writeable to be changed? Thnx for attention and regards, Oliver. ** Affects: qemu Importance: Undecided Status: New -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1070762 Title: savevm fails with inserted CD, "Device '%s' is writable but does not support snapshots." Status in QEMU: New Bug description: Hi, yesterday unfortunately a customer reported a failed snapshot of his VM. Going through the logfile I discovered: "Device 'ide1-cd0' is writable but does not support snapshots" this is with qemu-1.2.0 and 1.0.1 at least... Why writeable? Even if I specify "-drive ...,readonly=3Don,snapshot=3Doff" to qemu the m= onitor-command sees the CD-ROM-device as being writeable?! Somewhere I saw a "hint" for blockdev.c: =3D=3D=3D snip =3D=3D=3D --- /tmp/blockdev.c 2012-10-24 11:37:10.000000000 +0200 +++ blockdev.c 2012-10-24 11:37:17.000000000 +0200 @@ -551,6 +551,7 @@ case IF_XEN: case IF_NONE: dinfo->media_cd =3D media =3D=3D MEDIA_CDROM; + dinfo->bdrv->read_only =3D 1; break; case IF_SD: case IF_FLOPPY: =3D=3D=3D snap =3D=3D=3D after installing with this small patch applied it works, so insert CD, sa= vevm succeeds. This should be fixed at all correct places, and the tags "readonly=3Don,s= napshot=3Doff" should do it, too. Or even just work after specifying a driv= e being a CD-rom should do the trick ;-) Another "bad habit" is, that the ISO/DVD-file has to be writeable to be changed? Thnx for attention and regards, Oliver. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1070762/+subscriptions