From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id B559B92FEC for ; Thu, 16 Feb 2023 13:35:08 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9E0642889D for ; Thu, 16 Feb 2023 13:35:08 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Thu, 16 Feb 2023 13:35:08 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id D134847571; Thu, 16 Feb 2023 13:35:07 +0100 (CET) Message-ID: Date: Thu, 16 Feb 2023 13:35:06 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Content-Language: en-US To: pve-devel@lists.proxmox.com, "aderumier@odiso.com" , Thomas Lamprecht References: <20230213120021.3783742-1-aderumier@odiso.com> <3ba0178a-aa18-1c45-c7d6-7105954e3e83@proxmox.com> From: Fiona Ebner In-Reply-To: <3ba0178a-aa18-1c45-c7d6-7105954e3e83@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.125 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.257 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] partially-applied: [PATCH v4 qemu-server 00/16] rework memory hotplug + virtiomem X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2023 12:35:08 -0000 Am 15.02.23 um 14:42 schrieb Fiona Ebner: > Am 13.02.23 um 13:00 schrieb Alexandre Derumier: >> This patch series rework the current memory hotplug + virtiomem. >> >> memory option now have extra options: >> >> memory: [[current=]] [,max=] [,virtio=<1|0>] >> ex: memory: current=1024,max=131072,virtio=1 >> >> >> for classic memory hotplug, when maxmemory is defined, >> we use 64 fixed size dimm. >> The max option is a multiple of 64GB. >> >> The virtio option enable new virtio-mem support, >> instead of plugging dimm, it's add/removed block inside >> big dimm. >> virtio-mem can use 32000 blocks, the blocksize is compute from >> max memory. >> >> > Thanks! Applied the first 4 patches, will take a look at the others > tomorrow. We still need to adapt HA before memory can be turned into a > format string here ;) I'll try and work out patches to make HA independent of config details. @Thomas: based on our brief discussion off-list, would the following be okay? Add a get_derived_property() method to AbstractConfig.pm, taking a (partial) config and the name for the derived property. The first two will be 'maxcpu' and 'maxmem' (should I use 'max-cpu' or different names?), because that's what HA manager needs. The partial config needs to contain all actual properties needed to compute the derived property, e.g. 'vcpus', 'sockets' and 'cores' for 'maxcpu' in case of VMs. If we switch to get_guest_config_properties(), there needs to be a second method to request which properties are actually needed for the computation of the derived property beforehand. Whenever something in the actual properties changes, the calculation needs to be adapted to still yield the same result for the derived property, but this can be done entirely in the VM/CT plugin implementation. Whenever HA manager needs something new, a new derived property is implemented in the plugins and dependency bumps for qemu-server/pve-container are done.