snapshot=on fails with non file-based storage

Bug #1155677 reported by Richard Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QEMU
Won't Fix
Undecided
Stefan Hajnoczi

Bug Description

The snapshot=on option doesn't work with an nbd block device:

/usr/bin/qemu-system-x86_64 \
[...]
    -device virtio-scsi-pci,id=scsi \
    -drive file=nbd:localhost:61930,snapshot=on,format=raw,id=hd0,if=none \
    -device scsi-hd,drive=hd0 \
[...]

gives the error:

qemu-system-x86_64: -drive file=nbd:localhost:61930,snapshot=on,format=raw,id=hd0,if=none: could not open disk image nbd:localhost:61930: No such file or directory

If you remove the snapshot=on flag, it works (although that of course means that the block device is writable which we don't want).

Previously reported here:

  http://permalink.gmane.org/gmane.comp.emulators.qemu/148390

and I can confirm this still happens in qemu 1.4.0.

Changed in qemu:
status: New → In Progress
assignee: nobody → Stefan Hajnoczi (stefanha)
Revision history for this message
Thomas Huth (th-huth) wrote :

Triaging old bug tickets... I think this has likely been fixed in 2013 ... or can you still reproduce this issue with the latest version of QEMU? Could we close this ticket nowadays?

Revision history for this message
Richard Jones (rjones-redhat) wrote :

Let's close this. libguestfs doesn't use snapshot=on any longer.

Changed in qemu:
status: In Progress → Incomplete
Thomas Huth (th-huth)
Changed in qemu:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.