--- Begin Message ---
On Fri, Jan 12, 2024 at 01:04:50PM +, Esi Y wrote:
> On Fri, Jan 12, 2024 at 01:40:44PM +0100, Fabian Grünbichler wrote:
> >
> > > Esi Y via pve-devel hat am 12.01.2024 13:33
> > > CET geschrieben:
> > > On Thu, Jan 11, 2024 at 11:51:20AM +0100, Fabian Grünbichler wrote
--- Begin Message ---
On Thu, Jan 11, 2024 at 11:51:16AM +0100, Fabian Grünbichler wrote:
> if the target node has already stored their SSH host key on pmxcfs, pin it and
> ignore the global known hosts information.
>
> Signed-off-by: Fabian Grünbichler
> ---
> src/PVE/SSHInfo.pm | 15 ++
On 1/12/24 21:08, Alexandre Derumier wrote:
New epyc cpu already support 168 threads
qemu 8.1 support 1024 cores with q35
---
www/manager6/qemu/ProcessorEdit.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www/manager6/qemu/ProcessorEdit.js
b/www/manager6/qemu/Processo
> On Thu, Jan 11, 2024 at 11:51:16AM +0100, Fabian Grünbichler wrote:
> > if the target node has already stored their SSH host key on pmxcfs, pin it
> > and
> > ignore the global known hosts information.
> >
> > Signed-off-by: Fabian Grünbichler
> > ---
> > src/PVE/SSHInfo.pm | 15 +
>>mhmm.. in the backend we don't actually have a limit, maybe it's time
>>to remove the limit in the ui
>>altogether? it does not help anyway:
>>for numbers that are not too big (too many for qemu, too many for the
>>host)
>>it's not the right limit (qemu) or we don't know at that point in the
>>
Am 15.01.24 um 13:43 schrieb DERUMIER, Alexandre:
>
>
> Maybe an improvement in qemu-server, could be to add additional check
> at vm start, (maybe a simple warn), depending of qemu version or
> setup.
> For example, 1024 cores only works with q35 && qemu 8.1,
> it could be interesting to give a
--- Begin Message ---
On Mon, Jan 15, 2024 at 12:51:48PM +0100, Fabian Grünbichler wrote:
> > On Thu, Jan 11, 2024 at 11:51:16AM +0100, Fabian Grünbichler wrote:
> > > if the target node has already stored their SSH host key on pmxcfs, pin
> > > it and
> > > ignore the global known hosts informati
Tested cluster creation with three new nodes on 8.1 and the patches
Cluster creation and further ssh communication (eq. migration) worked
flawless
Tested-by: Hannes Duerr
On 1/11/24 11:51, Fabian Grünbichler wrote:
this series replaces the old mechanism that used a cluster-wide merged known
Fallback to v.ref when we do not use an alias or ipset in order to be
able to use normal CIDRs as source / destination address again
Signed-off-by: Stefan Hanreich
---
www/manager6/form/IPRefSelector.js | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/www/manager6/form/IPRe
Am 05/01/2024 um 15:07 schrieb Max Carrara:
> These two patches allow the Ceph Dashboard to work again as intended.
>
> The first patch provides a backport of a pull request [0] which removes
> the dependency on PyJWT. [1]
>
> The second patch removes two usages of functions that use PyOpenSSL, [
Am 05/01/2024 um 10:26 schrieb Fiona Ebner:
> Reported in the community forum:
> https://forum.proxmox.com/threads/139006/post-621739
>
> Signed-off-by: Fiona Ebner
> ---
> pvecm.adoc | 4
> 1 file changed, 4 insertions(+)
>
>
applied, thanks!
___
Am 03/01/2024 um 16:18 schrieb Maximiliano Sandoval:
> This patch follows the the discussion at
> https://lists.proxmox.com/pipermail/pve-devel/2023-December/061192.html.
>
> The use of exclamation and question marks is improved, one or two typos
> are fixed, and we use lowercase rather than "Head
12 matches
Mail list logo
