From: Hongquan Zhu <zhuhq@certusnet.com.cn>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1807073] [NEW] qemu-guest-agent stop work when fsfreeze
Date: Thu, 06 Dec 2018 02:44:22 -0000 [thread overview]
Message-ID: <154406426264.32667.2616897072259419283.malonedeb@chaenomeles.canonical.com> (raw)
Public bug reported:
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
** Affects: qemu
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/1807073
Title:
qemu-guest-agent stop work when fsfreeze
Status in QEMU:
New
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
next reply other threads:[~2018-12-06 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 2:44 Hongquan Zhu [this message]
2019-04-07 8:17 ` [Qemu-devel] [Bug 1807073] Re: qemu-guest-agent stop work when fsfreeze sles
2019-04-07 8:23 ` sles
2019-04-08 5:16 ` Hongquan Zhu
2020-06-09 21:20 ` Rene
2021-04-20 6:50 ` Thomas Huth
2021-06-20 4:17 ` Launchpad Bug Tracker
2021-08-09 9:43 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=154406426264.32667.2616897072259419283.malonedeb@chaenomeles.canonical.com \
--to=zhuhq@certusnet.com.cn \
--cc=1807073@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.