Bug 1084360

Summary:	[doc] Document behavior of --reuse-external (VIR_DOMAIN_SNAPSHOT_CREATE_REUSE_EXT)
Product:	Red Hat Enterprise Linux 7	Reporter:	Peter Krempa <pkrempa>
Component:	libvirt	Assignee:	Peter Krempa <pkrempa>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dyuan, eblake, mzhan, rbalakri, shyu, xuzhang
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libvirt-1.2.7-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 07:33:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Krempa 2014-04-04 07:56:35 UTC

Description of problem:
Documentation for the flag doesn't mention a few important facts about the required properties the re-used image has to have set manually.

The backing path needs to be set prior to snapshot otherwise it will not work afterwards. The image needs to be in qcow format ....

Comment 1 Peter Krempa 2014-07-14 07:31:14 UTC

Fixed upstream:

commit 6f04fb151bae22ce349190e5c769334403b025ce
Author: Peter Krempa <pkrempa>
Date:   Mon Jul 7 14:38:10 2014 +0200

    doc: Be more specific about semantics of _REUSE_EXT flag
    
    Snapshots and block-copy have a flag that forces qemu to re-use existing
    file. Our docs weren't exactly clear on what the existing file should
    contain for this to actually work.
    
    Re-word the docs a bit to state that the file needs to be pre-created in
    the desired format and the backing chain metadata needs to be set prior
    to handing it over to qemu.

v1.2.6-130-g6f04fb1

Comment 3 Shanzhi Yu 2014-11-20 07:24:45 UTC

Change to verify after read man virsh page

Comment 5 errata-xmlrpc 2015-03-05 07:33:44 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0323.html