From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: agl@us.ibm.com, qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/2] Add virtagent file system freeze/thaw
Date: Tue, 01 Feb 2011 15:36:35 +0100 [thread overview]
Message-ID: <4D481A73.7040006@redhat.com> (raw)
In-Reply-To: <AANLkTi=h1vJ6Y0-PELURPeLNv63p0AUuogn3HMcz8Aj+@mail.gmail.com>
On 02/01/11 15:34, Stefan Hajnoczi wrote:
> On Tue, Feb 1, 2011 at 2:26 PM, Jes Sorensen <Jes.Sorensen@redhat.com> wrote:
>> I have to admit you lost me here, where do you get that 500ms time from?
>> Is that the XMLRPC polling time or? I just used the example code from
>> other agent calls.
>
> 500 ms is made up. I was thinking, "what would a reasonable polling
> interval be?" and picked a sub-second number.
>
> Can you explain how the timeout in fsfreeze can happen? It's probably
> because I don't know the virtagent details.
Ah ok.
>From what I understand, the XMLRPC code is setup to timeout if the guest
doesn't reply within a certain amount of time. In that case, the caller
needs to poll to wait for the guest to complete the freeze. This really
should only happen if you have a guest with a large number of very large
file systems. I don't know how likely it is to happen in real life.
Cheers,
Jes
next prev parent reply other threads:[~2011-02-01 14:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 10:58 [Qemu-devel] [PATCH 0/2] virtagent - fsfreeze support Jes.Sorensen
2011-02-01 10:58 ` [Qemu-devel] [PATCH 1/2] Add virtagent file system freeze/thaw Jes.Sorensen
2011-02-01 14:12 ` Stefan Hajnoczi
2011-02-01 14:26 ` Jes Sorensen
2011-02-01 14:34 ` Stefan Hajnoczi
2011-02-01 14:36 ` Jes Sorensen [this message]
2011-02-01 14:41 ` Stefan Hajnoczi
2011-02-01 17:22 ` Michael Roth
2011-02-01 14:48 ` [Qemu-devel] " Adam Litke
2011-02-01 15:02 ` Jes Sorensen
2011-02-01 16:50 ` Michael Roth
2011-02-02 8:38 ` Jes Sorensen
2011-02-02 7:57 ` [Qemu-devel] " Stefan Hajnoczi
2011-02-02 8:48 ` Jes Sorensen
2011-02-03 17:41 ` Michael Roth
2011-02-04 6:13 ` Stefan Hajnoczi
2011-02-04 16:27 ` Michael Roth
2011-02-04 16:52 ` Stefan Hajnoczi
2011-02-04 11:03 ` Jes Sorensen
2011-02-04 16:51 ` Michael Roth
2011-02-01 10:58 ` [Qemu-devel] [PATCH 2/2] Add monitor commands for fsfreeze support Jes.Sorensen
2011-02-01 11:25 ` [Qemu-devel] [PATCH 0/2] virtagent - " Vasiliy G Tolstov
2011-02-01 13:02 ` Jes Sorensen
2011-02-01 16:04 ` Richard W.M. Jones
2011-02-01 20:04 ` Vasiliy G Tolstov
2011-02-01 20:17 ` Richard W.M. Jones
2011-02-01 14:16 ` Stefan Hajnoczi
2011-02-01 14:28 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2011-02-02 8:42 [Qemu-devel] [PATCH v2 " Jes.Sorensen
2011-02-02 8:42 ` [Qemu-devel] [PATCH 1/2] Add virtagent file system freeze/thaw Jes.Sorensen
2011-02-04 10:57 [Qemu-devel] [PATCH v3 0/2] virtagent - fsfreeze support Jes.Sorensen
2011-02-04 10:57 ` [Qemu-devel] [PATCH 1/2] Add virtagent file system freeze/thaw Jes.Sorensen
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=4D481A73.7040006@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=agl@us.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).