From: David Hildenbrand <david@redhat.com>
To: Dexuan Cui <decui@microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"sashal@kernel.org" <sashal@kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH] hv_balloon: Add the support of hibernation
Date: Thu, 12 Sep 2019 12:11:34 +0200 [thread overview]
Message-ID: <dfee4472-da92-fdc7-f277-c98c2e37d09b@redhat.com> (raw)
In-Reply-To: <42de5835-8faa-2047-0f77-db51dd57b036@redhat.com>
On 12.09.19 12:08, David Hildenbrand wrote:
> On 12.09.19 01:36, Dexuan Cui wrote:
>> When hibernation is enabled, we must ignore the balloon up/down and
>> hot-add requests from the host, if any.
>>
>> Fow now, if people want to test hibernation, please blacklist hv_balloon
>> or do not enable Dynamic Memory and Memory Resizing. See the comment in
>> balloon_probe() for more info.
>>
>
> Why do you even care about supporting hibernation? Can't you just pause
> the VM in the hypervisor and continue to live a happy life? :)
(to be more precise, most QEMU/KVM distributions I am aware of don't
support suspend/hibernation of guests for said reason, so I wonder why
Hyper-V needs it)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-09-12 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 23:36 [PATCH] hv_balloon: Add the support of hibernation Dexuan Cui
2019-09-12 10:08 ` David Hildenbrand
2019-09-12 10:11 ` David Hildenbrand [this message]
2019-09-12 19:18 ` Dexuan Cui
2019-09-13 7:46 ` David Hildenbrand
2019-09-13 20:54 ` Dexuan Cui
2019-09-13 21:44 ` David Hildenbrand
2019-09-14 0:26 ` Dexuan Cui
2019-09-25 20:03 ` Dexuan Cui
2019-09-26 7:19 ` David Hildenbrand
2019-09-26 17:42 ` Dexuan Cui
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=dfee4472-da92-fdc7-f277-c98c2e37d09b@redhat.com \
--to=david@redhat.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.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).