Bug 587605
Summary: | Failed to re-base qcow2 snapshot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Qunfang Zhang <qzhang> |
Component: | kvm | Assignee: | Virtualization Maintenance <virt-maint> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.6 | CC: | ehabkost, kwolf, lihuang, llim, mjenner, ndai, tburke, virt-maint, ykaul |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kvm-83-180.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-01-13 23:35:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Qunfang Zhang
2010-04-30 11:19:38 UTC
Does this work with 170? Looks like it's related to Naphtali's read-only support which was added in 171. Adding him to CC. Re-test in kvm-170, and this issue does not exist. This time I only create sn1,sn2 and sn3, write some file in each snapshot, and then rebase sn3 to sn1. # qemu-img rebase -b sn1 -F qcow2 -f qcow2 sn3 in kvm-170: # qemu-img rebase -b sn1 -F qcow2 -f qcow2 sn3 # qemu-img info sn3 image: sn3 file format: qcow2 virtual size: 80G (85899345920 bytes) disk size: 230M cluster_size: 65536 backing file: sn1 (actual path: sn1) in kvm-172: [root@localhost ~]# qemu-img rebase -b sn1 -F qcow2 -f qcow2 sn3 qemu-img: Error while writing to COW image: Permission denied Verified on kvm-83-180.el5, passed. Verified on kvm-83-207.el5, host install tree: RHEL5.6-Server-20101029.0, with the steps in bug description. passed. So, I will change the status to VERIFIED. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0028.html |