public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 qemu-server] qemu-agent: allow hotplug of fstrim_cloned_disk option.
Date: Tue, 05 Oct 2021 13:12:02 +0200	[thread overview]
Message-ID: <1633432128.w00qu8ioxe.astroid@nora.none> (raw)
In-Reply-To: <20211005094602.1974632-1-aderumier@odiso.com>

On October 5, 2021 11:46 am, Alexandre Derumier wrote:
> This option don't have any impact on device itself.
> 
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
>  PVE/QemuServer.pm | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 076ce59..907d522 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -4829,6 +4829,8 @@ sub vmconfig_hotplug_pending {
>  	    } elsif ($opt eq 'cpulimit') {
>  		my $cpulimit = $conf->{pending}->{$opt} == 0 ? -1 : int($conf->{pending}->{$opt} * 100000);
>  		$cgroup->change_cpu_quota($cpulimit, 100000);
> +	    } elsif ($opt eq 'agent') {
> +		vmconfig_update_agent($conf, $opt, $value);
>  	    } else {
>  		die "skip\n";  # skip non-hot-pluggable options
>  	    }
> @@ -4988,6 +4990,23 @@ sub vmconfig_update_net {
>      }
>  }
>  
> +sub vmconfig_update_agent {
> +    my ($conf, $opt, $value) = @_;
> +
> +    if ($conf->{$opt} && (my $old_agent = parse_guest_agent($conf))) {
> +
> +	my $agent = parse_guest_agent({$opt => $value});
> +
> +	# skip non hotpluggable value

shouldn't this be the other way round? check keys which are different, 
and have a list of hotpluggable ones, skip if any others are different?

that way if we add another property to the agent it's fail-safe 
(defaults to not being hotpluggable) until it is added to the explicit 
list.

> +	if (safe_string_ne($agent->{enabled}, $old_agent->{enabled}) ||
> +	    safe_string_ne($agent->{type}, $old_agent->{type})) {
> +		    die "skip\n";
> +	}
> +    } else {
> +	die "skip\n";
> +    }
> +}
> +
>  sub vmconfig_update_disk {
>      my ($storecfg, $conf, $hotplug, $vmid, $opt, $value, $arch, $machine_type) = @_;
>  
> -- 
> 2.30.2
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 
> 




  reply	other threads:[~2021-10-05 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  9:46 Alexandre Derumier
2021-10-05 11:12 ` Fabian Grünbichler [this message]
2021-10-05 12:13   ` DERUMIER, Alexandre

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=1633432128.w00qu8ioxe.astroid@nora.none \
    --to=f.gruenbichler@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal