From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
pve-devel@lists.proxmox
Subject: [pbs-devel] applied: [RFC PATCH proxmox] http: enable http2 feature for hyper-util
Date: Tue, 22 Jul 2025 16:39:27 +0200 [thread overview]
Message-ID: <4473a142-4e81-4d9e-b698-f64586cb8058@proxmox.com> (raw)
In-Reply-To: <20250722114237.771607-1-d.csapak@proxmox.com>
Am 22.07.25 um 13:43 schrieb Dominik Csapak:> this is necessary for some esxi versions to be added as PVE storage on trixie
> otherwise it fails with:
>
> thread 'main' panicked at /usr/share/cargo/registry/hyper-util-0.1.12/src/client/legacy/client.rs:576:33:
> http2 feature is not enabled
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> create storage failed: failed to spawn fuse mount, process exited with status 25856
>
> tested with esxi 8.0.3 / PVE 9 beta
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> pve-esxi-import-tools have to be rebuilt with the new proxmox-http crate
> of course
>
> not sure what other implications enabling this feature has, the docs are
> rather sparse on that, so sending as RFC
It was active with the old hyper, where most the utils crates was included
directly in the main crate, so about the same implications as the usage in
proxmox-http in bookworm.
> proxmox-http/Cargo.toml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
applied, thanks!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-07-22 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 11:42 [pbs-devel] " Dominik Csapak
2025-07-22 14:39 ` Thomas Lamprecht [this message]
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=4473a142-4e81-4d9e-b698-f64586cb8058@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-devel@lists.proxmox \
/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