From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50772) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUjpG-0006dF-AI for qemu-devel@nongnu.org; Wed, 05 Dec 2018 21:55:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gUjpC-0004Uz-AZ for qemu-devel@nongnu.org; Wed, 05 Dec 2018 21:55:42 -0500 Received: from indium.canonical.com ([91.189.90.7]:36366) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gUjpB-0004Rh-Un for qemu-devel@nongnu.org; Wed, 05 Dec 2018 21:55:38 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1gUjpA-00074g-7T for ; Thu, 06 Dec 2018 02:55:36 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 167962E80D1 for ; Thu, 6 Dec 2018 02:55:36 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 06 Dec 2018 02:44:22 -0000 From: Hongquan Zhu Reply-To: Bug 1807073 <1807073@bugs.launchpad.net> Sender: bounces@canonical.com Message-Id: <154406426264.32667.2616897072259419283.malonedeb@chaenomeles.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1807073] [NEW] qemu-guest-agent stop work when fsfreeze List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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: (n= ull) 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 d= o 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 beca= me read-only, and syslog seems stop writing until we fsck /dev/vda1 and mou= nt -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