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 1360119 - Fail to edit the guest's XML associated with a saved state file with virsh save-image-edit command
Summary: Fail to edit the guest's XML associated with a saved state file with virsh sa...
Keywords:
Status: CLOSED DUPLICATE of bug 1229255
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1229255
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-26 04:35 UTC by yisun
Modified: 2016-07-27 02:45 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1229255
Environment:
Last Closed: 2016-07-27 02:45:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 yisun 2016-07-26 04:37:58 UTC 
per https://bugzilla.redhat.com/show_bug.cgi?id=1229255#c10
This issue also reproduced on x86_64 platform(which doesn't have problem before), so clone this bug here for tracking.
Comment 3 Andrea Bolognani 2016-07-26 07:48:40 UTC 
(In reply to yisun from comment #1)
> per https://bugzilla.redhat.com/show_bug.cgi?id=1229255#c10
> This issue also reproduced on x86_64 platform(which doesn't have problem
> before), so clone this bug here for tracking.

Does it make sense to have two separate bugs track this?
Wouldn't it be less confusing to just move Bug 1229255 to
Hardware: All and keep tracking the issue there?
Comment 4 Andrea Bolognani 2016-07-26 11:28:38 UTC 
Guannan mentioned that a new bug was filed because this issue
didn't seem to affect libvirt < 2.0.0 on x86.

I actually think that there has been no regression on x86,
and that the bug was affecting both architectures even before;
what might have happened is that the bug has been made easier
to trigger because the domain XML has become bigger on x86.

It would be very interesting to take the domain XML from
libvirt 2.0.0 and use it to define a guest on earlier libvirt,
and see whether performing the same steps on both libvirt
versions has the same result.
Comment 5 yisun 2016-07-27 02:45:06 UTC 
(In reply to Andrea Bolognani from comment #4)
> Guannan mentioned that a new bug was filed because this issue
> didn't seem to affect libvirt < 2.0.0 on x86.
> 
> I actually think that there has been no regression on x86,
> and that the bug was affecting both architectures even before;
> what might have happened is that the bug has been made easier
> to trigger because the domain XML has become bigger on x86.
> 
> It would be very interesting to take the domain XML from
> libvirt 2.0.0 and use it to define a guest on earlier libvirt,
> and see whether performing the same steps on both libvirt
> versions has the same result.

Your assumption is correct, with same xml, it reproduced on previous libvirt versions. I'll close this bug, add comment to original bug and change the "platform" from "ppc" to "all". thx. 





 ============ libvirt-1.2.17-13.el7.x86_64 ============

[root@localhost 1.2.17-13.el7]# service libvirtd restart
Redirecting to /bin/systemctl restart  libvirtd.service
[root@localhost 1.2.17-13.el7]# rpm -qa | grep libvirt-1
libvirt-1.2.17-13.el7.x86_64
[root@localhost 1.2.17-13.el7]# rpm -qa | grep libvirt-1^C
[root@localhost 1.2.17-13.el7]# virsh save-image-edit /tmp/vm.save 
error: operation failed: new xml too large to fit in file
Failed. Try again? [y,n,f,?]: 
error: operation failed: new xml too large to fit in file

[root@localhost 1.2.17-13.el7]# virsh save-image-define /tmp/vm.save /tmp/old_vm.xml --running
error: Failed to update /tmp/vm.save
error: operation failed: new xml too large to fit in file


 ============ libvirt-1.3.5-1.el7.x86_64 ============
[root@localhost 1.3.5-1.el7]# rpm -qa | grep libvirt-1
libvirt-1.3.5-1.el7.x86_64
[root@localhost 1.3.5-1.el7]# service libvirtd restart
Redirecting to /bin/systemctl restart  libvirtd.service
[root@localhost 1.3.5-1.el7]# virsh save-image-edit /tmp/vm.save 
error: operation failed: new xml too large to fit in file
Failed. Try again? [y,n,f,?]: 
error: operation failed: new xml too large to fit in file

[root@localhost 1.3.5-1.el7]# vim /tmp/old_vm.xml 
[root@localhost 1.3.5-1.el7]# virsh save-image-define /tmp/vm.save /tmp/old_vm.xml --running
error: Failed to update /tmp/vm.save
error: operation failed: new xml too large to fit in file

*** This bug has been marked as a duplicate of bug 1229255 ***
Note You need to log in before you can comment on or make changes to this bug.