From: "MATSUDA, Daiki" <matsudadik@intellilink.co.jp>
To: qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [BUG] qemu-ga: failed to fsfreeze-thaw on RHEL 5.8 Guest
Date: Mon, 28 May 2012 08:12:12 +0900 [thread overview]
Message-ID: <4FC2B4CC.8090505@intellilink.co.jp> (raw)
In-Reply-To: <4FBF1F36.1080303@intellilink.co.jp>
I researched the source of the bug.
qemu-ga calls guest_fsfreeze_build_mount_list from
qemp_guest_fsreeze_thaw in qga/commands-posix.c. And it tries to read
/etc/mtab (= MOUNTED) to get mounted filesystems. But when they are
frozen, getmntent(fp) is not finished in the situation /etc/mtab in
frozen filesystem.
I suggest to read the list from not frozen filesystem file or on-memory
data, e.g. /proc/mounts.
Regards
MATSUDA Daiki
--- qga/commands-posix.c.orig 2012-05-28 08:10:47.842332018 +0900
+++ qga/commands-posix.c 2012-05-28 08:11:01.598340937 +0900
@@ -347,7 +347,7 @@ static int guest_fsfreeze_build_mount_li
{
struct mntent *ment;
GuestFsfreezeMount *mount;
- char const *mtab = MOUNTED;
+ char const *mtab = "/proc/mounts";
FILE *fp;
fp = setmntent(mtab, "r");
> I encountered the serious bug on QEMU Guest Agent.
>
> environment
> Guest OS : RHEL 5.8 / 5.7 (i686)
> Guest Agent Version : qemu-1.1.0rc2 and rc3
>
> I am trying to take snapshot via virsh snapshot-create-as command. And
> to freeze guest's filesystem and take snapshot is succeed. But after
> sending the thaw command to Guest, time error occurs on libvirt qemu
> agent because of not catch Guest's answer.
> In addition, its situation is worst because the Guest Filesystem is kept
> as frozen.
>
> The problem does not occur on RHEL 6.2 Guest OS and in about qemu-1.0 it
> does not occur.
>
> Regards
> MATSUDA Daiki
>
>
>
>
next prev parent reply other threads:[~2012-05-27 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 5:57 [Qemu-devel] [BUG] qemu-ga: failed to fsfreeze-thaw on RHEL 5.8 Guest MATSUDA, Daiki
2012-05-27 23:12 ` MATSUDA, Daiki [this message]
2012-05-28 0:49 ` Michael Roth
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=4FC2B4CC.8090505@intellilink.co.jp \
--to=matsudadik@intellilink.co.jp \
--cc=mdroth@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).