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 1461672

Summary: qemu-img core dumped when create external snapshot through ssh protocol without specifying image size
Product: Red Hat Enterprise Linux 7 Reporter: Ping Li <pingl>
Component: qemu-kvmAssignee: Jeff Cody <jcody>
Status: CLOSED ERRATA QA Contact: Ping Li <pingl>
Severity: high Docs Contact:
Priority: high    
Version: 7.4CC: aliang, chayang, cliao, coli, hachen, juzhang, knoel, michen, ngu, pingl, rbalakri, virt-maint, xuhan, xuwei
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-1.5.3-145.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 14:32:19 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: 1473046    

Comment 4 Jeff Cody 2017-10-01 03:56:22 UTC 
*** Bug 1461677 has been marked as a duplicate of this bug. ***
Comment 5 Miroslav Rezanina 2017-10-06 07:13:04 UTC 
Fix included in qemu-kvm-1.5.3-145.el7
Comment 6 Ping Li 2017-10-09 16:46:14 UTC 
Set the bug as verified according to the test result.

Verified the issue with below packages:
kernel-3.10.0-728.el7.x86_64
qemu-kvm-1.5.3-145.el7

Test steps:
1. Setup ssh environment
#ssh-keygen
#ssh-copy-id root.73.83
#exec /usr/bin/ssh-agent $SHELL
#ssh-add

2. Create snapshot via ssh protocol
# qemu-img create -f qcow2 -b 'json:{"file.driver":"ssh", "file.host":"10.73.73.83", "file.port":"22", "file.path":"/home/tests/diskfile/rhel75.qcow2", "file.user":"root", "file.host_key_check":"no"}' ssh.qcow2
Formatting 'ssh.qcow2', fmt=qcow2 size=21474836480 backing_file='json:{"file.driver":"ssh", "file.host":"10.73.73.83", "file.port":"22", "file.path":"/home/tests/diskfile/rhel75.qcow2", "file.user":"root", "file.host_key_check":"no"}' encryption=off cluster_size=65536 lazy_refcounts=off

3. Check info of image
# qemu-img info ssh.qcow2 
image: ssh.qcow2
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 17M
cluster_size: 65536
backing file: json:{"file.driver":"ssh", "file.host":"10.73.73.83", "file.port":"22", "file.path":"/home/tests/diskfile/rhel75.qcow2", "file.user":"root", "file.host_key_check":"no"}
Format specific information:
    compat: 1.1
    lazy refcounts: false

4. Boot up the guest
Comment 11 errata-xmlrpc 2018-04-10 14:32:19 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://access.redhat.com/errata/RHSA-2018:0816