From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
agl@us.ibm.com, qemu list <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2] balloon: Don't try fetching info if machine is stopped
Date: Thu, 26 Aug 2010 08:22:31 -0500 [thread overview]
Message-ID: <4C766A97.4030107@codemonkey.ws> (raw)
In-Reply-To: <20100826081425.GD9564@redhat.com>
On 08/26/2010 03:14 AM, Daniel P. Berrange wrote:
> On Thu, Aug 26, 2010 at 10:05:44AM +0200, Paolo Bonzini wrote:
>
>> On 08/26/2010 08:05 AM, Amit Shah wrote:
>>
>>> This is what I have currently. It would need some timer handling in
>>> the save/load case as well, right?
>>>
>> When loading you won't have any pending "info balloon" command, so I
>> think the timer need not be preserved across migration.
>>
>> Also, 5 seconds for a stopped guest is actually a lot, so maybe Amit's
>> original patch or a variant thereof would make sense anyway.
>>
> We should have a combination of both. If we know the guest is stopped
> we should return immediately, otherwise we should use the timer as a
> way to cope with a crashed/evil guest.
>
Stopped doesn't necessarily mean that it's permanently stopped or even
that a user has stopped it.
We stop a guest during live migration and in some other cases (like on
disk error).
Returning immediately is an optimization on something that should be a
proper fix. Otherwise, you have a guest initiated DoS attack on
management tools.
Regards,
Anthony Liguori
> Daniel
>
next prev parent reply other threads:[~2010-08-26 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 0:48 [Qemu-devel] [PATCH V2] balloon: Don't try fetching info if machine is stopped Amit Shah
2010-08-20 10:13 ` [Qemu-devel] " Paolo Bonzini
2010-08-20 12:01 ` [Qemu-devel] " Amit Shah
2010-08-22 21:54 ` Anthony Liguori
2010-08-23 9:24 ` Daniel P. Berrange
2010-08-26 5:25 ` Amit Shah
2010-08-26 6:05 ` Amit Shah
2010-08-26 8:05 ` Paolo Bonzini
2010-08-26 8:14 ` Daniel P. Berrange
2010-08-26 13:22 ` Anthony Liguori [this message]
2010-08-26 8:17 ` Amit Shah
2010-08-26 8:19 ` Paolo Bonzini
2010-08-26 8:28 ` Daniel P. Berrange
2010-08-26 12:57 ` Luiz Capitulino
2010-08-26 13:30 ` Paolo Bonzini
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=4C766A97.4030107@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agl@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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.