From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 127F0C433E0 for ; Tue, 9 Jun 2020 21:37:31 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D255420734 for ; Tue, 9 Jun 2020 21:37:30 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D255420734 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bugs.launchpad.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:39358 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jilw2-0005q2-58 for qemu-devel@archiver.kernel.org; Tue, 09 Jun 2020 17:37:30 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40670) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jilvR-0005PY-U1 for qemu-devel@nongnu.org; Tue, 09 Jun 2020 17:36:53 -0400 Received: from indium.canonical.com ([91.189.90.7]:59414) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jilvQ-0000su-Re for qemu-devel@nongnu.org; Tue, 09 Jun 2020 17:36:53 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1jilvO-00083i-FF for ; Tue, 09 Jun 2020 21:36:50 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 71B972E810D for ; Tue, 9 Jun 2020 21:36:50 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 09 Jun 2020 21:20:44 -0000 From: Rene <1807073@bugs.launchpad.net> To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=New; importance=Undecided; assignee=None; X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: dokbua slesru zhuhq X-Launchpad-Bug-Reporter: Hongquan Zhu (zhuhq) X-Launchpad-Bug-Modifier: Rene (dokbua) References: <154406426264.32667.2616897072259419283.malonedeb@chaenomeles.canonical.com> Message-Id: <159173764493.31259.9615874501960473780.malone@gac.canonical.com> Subject: [Bug 1807073] Re: qemu-guest-agent stop work when fsfreeze X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="ef9fc486e875d54078fa61cf91e898b895125d89"; Instance="production-secrets-lazr.conf" X-Launchpad-Hash: 7902a10df0e12e72f11f9d993b5bcdac9ea3263c Received-SPF: none client-ip=91.189.90.7; envelope-from=bounces@canonical.com; helo=indium.canonical.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/09 10:15:37 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -65 X-Spam_score: -6.6 X-Spam_bar: ------ X-Spam_report: (-6.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1807073 <1807073@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" I have a problem with fsfreeze that looks very similar to this, though I'm of course not 100% sure it's the same. When I try to snapshot one server, fsfreeze-freeze hangs, and after having timeout'ed the qemu agent has crashed: # qm guest cmd 105 fsfreeze-status thawed # qm guest cmd 105 fsfreeze-freeze ^C << hangs, having to break out of the command # qm guest cmd 105 fsfreeze-status QEMU guest agent is not running # qm reset 105 --skiplock # qm guest cmd 105 fsfreeze-status thawed Host is Proxmox 5, VM is Centos 7 with Cpanel. This happens every time I try to snapshot the server. Other VM's on the host freeze fine without problem. I don't find anything interesting under /var/log. Please let me know if there is anything I can do to help debug this problem. -- = 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