This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.31
---
qemu (1:2.5+dfsg-5ubuntu10.31) xenial; urgency=medium
* d/p/ubuntu/lp-1587065-qga-ignore-EBUSY-when-freezing-a-filesystem.patch:
Fix qemu-guest-agent failing to freeze filesystems that were mounted
multiple
Prior to the update:
$ virsh domfsfreeze x-freeze; virsh domfsthaw x-freeze
error: Unable to freeze filesystems
error: internal error: unable to execute QEMU agent command
'guest-fsfreeze-freeze': failed to freeze /: Device or resource busy
Thawed 0 filesystem(s)
$ sudo apt install qemu-guest-
Hello Dominique, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.31 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Tests are all ok, MP review was acked and case confirmed.
No Security Update since then in between, so sponsoring into SRU queue now ...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
** Description changed:
[Impact]
- * backport upstream fix to avoid double unmounts (e.g. bind mounts)
-hanging the freeze action.
+ * backport upstream fix to avoid double unmounts (e.g. bind mounts)
+ hanging the freeze action.
[Test Case]
* Prepare a guest
$ uvt-s
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
-
- * justification for backporting the fix to the stable release.
-
- * In addition, it is helpful, but not required, to include an
- explanation of how the upload fixes this bug.
+ * backport
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * An explanation of the effects of the bug on users and
- * justification for backporting the fix to the stable release.
+ * justification for backporting the fix to the stable release.
- *
** Changed in: qemu (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - multiple mounts block fsfreeze
Status in QE
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/348672
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - multiple m
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test Ca
Steps to reproduce
uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=amd64 release=xenial label=daily
uvt-kvm create --password ubuntu x-freeze arch=amd64 release=xenial label=daily
Add this to the guest definition and restart it
>From the hos
Fix is known and seems backportable, marking as server-next and subscribing for
somebody to take a look.
Also as mentioned it is in 2.9, so newer releases are already fixed.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Stat
This affects Ubuntu 16.04 as in #4
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - multipl
You've got to open this (or a new bug) against Ubuntu's qemu package to
get it included there. So far, this bug here is only opened against the
upstream QEMU project.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
de
Any chance this will ever get backported to 2.5 on Xenial?
cheers!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - multiple mounts block fsfreeze
Status in QEMU:
New
Was that this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ce2eb6c4a044d809c
?
That was included in QEMU v2.9.0, so I think we can set the status to "Fix
released" now?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
h
Same problem here ! More infos : https://forum.opennebula.org/t/backup-
live-vms-with-snapshots-quiesce-atomic/4471
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - mult
This has been merged in upstream Qemu a while ago.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - multiple mounts block fsfreeze
Status in QEMU:
New
Bug descriptio
I also have a path mounted twice, but this time it's devicemapper and
not AUFS like tim, so maybe not fs type related.
virsh version:
Compiled against library: libvirt 1.3.1
Using library: libvirt 1.3.1
Using API: QEMU 1.3.1
Running hypervisor: QEMU 2.5.0
KVM/QEMU Host command:
virsh
Strangely I've started having the same problem as Tim this week, beside
regular upgrade I did reboot since last backup... (Ubuntu LTS 16.04)
if I stop docker, the backup will proceed, otherwise i get the same
failed to freeze / error message, even with no container running, just
the daemon. That's
I have a related Problem with a libvirt Guest running some Docker-
Containers.
root@docker1:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 7.9G 2.9G 4.6G 39% /
udev 10M 0 10M 0% /dev
tmpfs 794M 8.6M 785M 2% /run
tmpfs 2.0G
I'm the responder from the Qemu list. I reviewed that C code a while ago
when I stumbled over it. If someone helps me through the Qemu patch
acceptance process then I'm willing to provide a patch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
22 matches
Mail list logo
