[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1070762] [NEW] savevm fails with inserted CD, "Device
From: |
Oliver Francke |
Subject: |
[Qemu-devel] [Bug 1070762] [NEW] savevm fails with inserted CD, "Device '%s' is writable but does not support snapshots." |
Date: |
Wed, 24 Oct 2012 09:58:51 -0000 |
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=on,snapshot=off" to qemu the
monitor-command sees the CD-ROM-device as being writeable?!
Somewhere I saw a "hint" for blockdev.c:
=== snip ===
--- /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 = media == MEDIA_CDROM;
+ dinfo->bdrv->read_only = 1;
break;
case IF_SD:
case IF_FLOPPY:
=== snap ===
after installing with this small patch applied it works, so insert CD, savevm
<somename> succeeds.
This should be fixed at all correct places, and the tags
"readonly=on,snapshot=off" 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=on,snapshot=off" to qemu the
monitor-command sees the CD-ROM-device as being writeable?!
Somewhere I saw a "hint" for blockdev.c:
=== snip ===
--- /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 = media == MEDIA_CDROM;
+ dinfo->bdrv->read_only = 1;
break;
case IF_SD:
case IF_FLOPPY:
=== snap ===
after installing with this small patch applied it works, so insert CD, savevm
<somename> succeeds.
This should be fixed at all correct places, and the tags
"readonly=on,snapshot=off" 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1070762/+subscriptions
- [Qemu-devel] [PULL 00/32] Block patches, Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 01/32] qemu-img: Fix division by zero for zero size images, Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 02/32] qemu-iotests: Test qemu-img operation on zero size image, Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 05/32] block: make bdrv_find_backing_image compare canonical filenames, Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 03/32] qmp: fix __accept() in qmp.py, Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 07/32] qemu-iotests: add relative backing file tests for block-commit (040), Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 04/32] qemu-img rebase: use empty string to rebase without backing file, Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 32/32] osdep: Less restrictive F_SEFL in qemu_dup_flags(), Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 27/32] qemu-iotests: add mirroring test case, Kevin Wolf, 2012/10/24
- [Qemu-devel] [PATCH 28/32] iostatus: forward block_job_iostatus_reset to block job, Kevin Wolf, 2012/10/24