The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state
back to "New" within the next 60 days, otherwise this report will be marked as
"Expired". Or mark it as "Fix Released" if the problem has been solved with a
newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1807073
Title:
qemu-guest-agent stop work when fsfreeze
Status in QEMU:
Incomplete
Bug description:
Create a live snapshot, we should first to fsfreeze the file system. We do
have only one disk mounted to /:
Filesystem Size Used Avail Use% Mounted on
udev 48G 0 48G 0% /dev
tmpfs 9.5G 8.7M 9.5G 1% /run
/dev/vda1 485G 1.5G 484G 1% /
tmpfs 48G 0 48G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 48G 0 48G 0% /sys/fs/cgroup
tmpfs 9.5G 0 9.5G 0% /run/user/0
snapshot action is OK, when we restore the snapshot, the file system became
read-only, and syslog seems stop writing until we fsck /dev/vda1 and mount -o
rw,remount /:
Dec 5 00:39:16 systemd[1]: Started Session 180 of user root.
Dec 5 00:45:05 qemu-ga: info: guest-fsfreeze called
Dec 5 07:00:45 kernel: [ 114.623823] EXT4-fs (vda1): re-mounted. Opts:
(null)
So after snapshoting, wo do fsthaw the file system, maybe the qga
dose not respond or stop work, this action dose not execute
successfully and there is no log to show the status of qemu-guest-
agent.
Version:
libvirt 1.2.17
qemu 2.3.0
qemu-guest-agent 2.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1807073/+subscriptions
