From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH V2 qemu-server 1/2] enable balloon free-page-reporting
Date: Wed, 16 Mar 2022 18:48:08 +0100 [thread overview]
Message-ID: <a5ebac8e-89fc-6ecf-287a-f57e2e81fa39@proxmox.com> (raw)
In-Reply-To: <20220306124647.2267293-2-aderumier@odiso.com>
On 06.03.22 13:46, Alexandre Derumier wrote:
> Allow balloon device driver to report hints of guest free pages to the host,
> for auto memory reclaim
>
> https://lwn.net/Articles/759413/
> https://events19.linuxfoundation.org/wp-content/uploads/2017/12/KVMForum2018.pdf
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> PVE/QemuServer.pm | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 42f0fbd..a9e86b3 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -3846,7 +3846,9 @@ sub config_to_command {
> # enable balloon by default, unless explicitly disabled
> if (!defined($conf->{balloon}) || $conf->{balloon}) {
> my $pciaddr = print_pci_addr("balloon0", $bridges, $arch, $machine_type);
> - push @$devices, '-device', "virtio-balloon-pci,id=balloon0$pciaddr";
> + my $ballooncmd = "virtio-balloon-pci,id=balloon0$pciaddr";
> + $ballooncmd .= ",free-page-reporting=on" if min_version($machine_version, 6, 2);
do we even need to guard this behind 6.2 machine version, as I tried to add it
on a running host and migrations in both directions went just fine with a windows
10 VM.
Asking mostly because we already have QEMU 6.2 available publicly on pvetest and
use it also for some infrastructure of ours, so if it really would be breaking
we'd need to use our separate qemu-version independent machine bump mechanism
(+pve1).
But it seems that its not required, or did you find that it can indeed break live
migration? fwiw, for us is really only forward migration, from vm without reporting
enabled to vm with reporting enabled, relevant.
> + push @$devices, '-device', $ballooncmd;
> }
>
> if ($conf->{watchdog}) {
next prev parent reply other threads:[~2022-03-16 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 12:46 [pve-devel] [PATCH V2 qemu-server 0/2] " Alexandre Derumier
2022-03-06 12:46 ` [pve-devel] [PATCH V2 qemu-server 1/2] " Alexandre Derumier
2022-03-16 17:48 ` Thomas Lamprecht [this message]
2022-03-16 19:32 ` DERUMIER, Alexandre
2022-03-17 8:35 ` Thomas Lamprecht
2022-03-28 10:06 ` DERUMIER, Alexandre
2022-03-06 12:46 ` [pve-devel] [PATCH V2 qemu-server 2/2] add test for virtio-balloon free-page-reporting=on. (qemu 6.2) Alexandre Derumier
2022-04-27 9:23 ` [pve-devel] applied: [PATCH V2 qemu-server 0/2] enable balloon free-page-reporting Thomas Lamprecht
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=a5ebac8e-89fc-6ecf-287a-f57e2e81fa39@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.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