[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2021-02-18 Thread Frank Heimes
As discussed per chat, closing this ticket hereby. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873887 Title: virt-clone fails on a suspended (paused) guest, whereas documentation claims the

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2021-02-18 Thread Christian Ehrhardt 
IMHO for this change is not worth to trigger an SRU for it. If someone insists he'd have to outline a convincing case for it. ** Also affects: virt-manager (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: virt-manager (Ubuntu Focal) Status: New => Won't Fix --

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2021-02-11 Thread Frank Heimes
** Changed in: virt-manager (Ubuntu) Status: Triaged => Fix Released ** Changed in: ubuntu-z-systems Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2021-02-11 Thread Frank Heimes
The virt-manager package on hirsute got recently updated to v3.2: virt-manager | 1:3.2.0-3| hirsute/universe Since this seems to have been fixed with 3.0 this should be now Fix Released (for H). In focal as well as in groovy there is still a v2.2.1 where the behavior was always

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2021-01-26 Thread bugproxy
--- Comment From lagar...@br.ibm.com 2021-01-26 15:56 EDT--- I see the virt-manager package is updated in 21.04. ** Tags removed: targetmilestone-inin2004 ** Tags added: targetmilestone-inin2104 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2020-11-16 Thread Frank Heimes
** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873887 Title: virt-clone fails on a suspended (paused) guest, whereas

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2020-10-09 Thread Christian Ehrhardt 
FYI - this will be in v3.0 once we will merge it and isn't important enough (IMHO) to be backported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873887 Title: virt-clone fails on a suspended

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2020-06-03 Thread bugproxy
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2004 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873887 Title: virt-clone fails on a suspended (paused) guest, whereas

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2020-04-21 Thread Christian Ehrhardt 
And while I was looking to spawn that discussion see what I've found: upstream Bug & Discussion: https://bugzilla.redhat.com/show_bug.cgi?id=1725330 And the fix was dropping the mention (and some remaining code) of that ability:

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2020-04-21 Thread Christian Ehrhardt 
Isolated convert command: $ sudo qemu-img convert -f qcow2 -O qcow2 -o compat=1.1,lazy_refcounts /var/lib/uvtool/libvirt/images/focal-nvdimm.qcow /var/lib/uvtool/libvirt/images/focal-nvdimm-clone.qcow qemu-img: Could not open '/var/lib/uvtool/libvirt/images/focal-nvdimm.qcow': Failed to get

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2020-04-20 Thread Frank Heimes
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Incomplete ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Server Team

[Bug 1873887] Re: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful.

2020-04-20 Thread Christian Ehrhardt 
Since ages qemu is locking the image files (I think since 18.04) and that seems to block the command here. IIRC Read-only readers can flag their open calls to skip that (e.g. qemu-img has an option --force-share). Not sure what virt-clone uses here, but whatever it is needs the similar treatment.