Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1322752

Summary:	An error "Must specify storage creation parameters for non-existent path" occurs when doing virt-clone with --preserve-data
Product:	Red Hat Enterprise Linux 7	Reporter:	Xiaodai Wang <xiaodwan>
Component:	virt-manager	Assignee:	Pavel Hrdina <phrdina>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	juzhou, mxie, mzhan, tzheng, xzhong
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1342438 (view as bug list)		Environment:
Last Closed:	2016-06-03 07:30:43 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:
Bug Depends On:
Bug Blocks:	1342438

Description Xiaodai Wang 2016-03-31 09:10:09 UTC

Description of problem:
An error "Must specify storage creation parameters for non-existent path" occurs when doing virt-clone with --preserve-data

Version-Release number of selected component (if applicable):
virt-manager-1.2.1-8.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Prepare a shutdown vm.
2. Clone the vm with --preserve-data options and with a non-existent file.
# virt-clone -o vm1 -n vm2 -f /var/lib/libvirt/images/vm2 --preserve-data
or 
# virt-clone -o vm1 --auto-clone --preserve-data

Actual results:
An error occurs as below.
ERROR    Could not use path '/vm1-new.img' for cloning: Must specify storage creation parameters for non-existent path '/vm1-new.img'.

Expected results:
virt-clone should not report error and create a vm successfully.

Additional info:

Comment 2 Pavel Hrdina 2016-06-03 07:30:43 UTC

This isn't a bug.  If you use --preserve-data you have to provide an existing disk image via --file options.  The --preserve-data means that virt-clone will not modify in any way disk images specified via --files, it will use those files directly for the new guest created by this clone command, which means that the disk images must exists.  Man page for virt-clone states the same.