Search results

exactly. you already have one cephfs that is configured as storage. the "Create CephFS" button allows you to create more ;)

if you want to enable HA, you need to ensure that your network is stable enough for corosync to not lose quorum: https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_cluster_network otherwise, it can happen that some or all nodes in the cluster get fenced...

there's a very high level roadmap here: https://pve.proxmox.com/wiki/Roadmap#Roadmap smaller features are "just" tracked in the bug tracker. most community engagement happens here in the forum and in the enterprise support channels.

by the very definition of what a gateway is, you can only have one. I am not sure what you are trying to achieve, but it is very likely not solved by having "two gateways". please describe your actual problem in detail, then we might arrive at a solution ;)

like I said last week - "/sys/firmware/edi/efivars is how the kernel exposes EFI variables, it's not a place where you can store anything other than variable values". if proxmox-boot-tool manages the boot aspect of a PVE system, then the ESP(s) are not mounted unless needed. you can manually...

I'm not sure I follow.. most features are developed in-house, some are contributed by the community. in this case, @spirit wrote the patch

you don't need to have a fingerprint if the cert is trusted by the system.. could you try connecting with `curl -v` and `proxmox-backup-client login --repository ....` and print the output here?

you are mixing up two things: - if the PVE packages are upgraded, services are restarted/reloaded/left-alone as needed by the package maintainer scripts that are executed before/during/after upgrades, including things like a pve-container upgrade triggering a reload of pveproxy/pvedaemon even...

https://pbs.proxmox.com/docs/installation.html#install-proxmox-backup-server-on-debian ;)

it depends what those tools are and how they work I'd say, but yes, the EFI dir on the ESP is where efi binaries are put (usually in a subdir). for example, you should see a proxmox subdir containing our bootloader files. no, I am not involved with OPNsense at all (other than as a user) -...

any mail client should do ;)

vielleicht koenntest du ein foto / screenshot der "langen liste" posten? ;)

das klingt nach einem sehr anderen problem.. probier mal "quiet" wegzumachen im bootloader menü ("e" druecken, dann editieren, dann f10), vielleicht siehst du dann mehr - ich vermute es wird ein problem mit der grafikkarte sein.. sonst ist ueber Debian bookworm installieren auch eine option...

you cannot use kvm64, since that doesn't have all the features that that distro requires.. you need to use a CPU type that does (either one of the physical ones matching your CPU, or host, or the "bumped baseline" x86-64-v2-AES). please read the docs, they explain it in more detail.

https://bugzilla.proxmox.com/show_bug.cgi?id=4295

the ESP is either not mounted (if there are multiple and keeping them in sync is handled by proxmox-boot-tool), or it is mounted at /boot/efi (if there is only one that is directly written to by various system packages). /sys/firmware/edi/efivars is how the kernel exposes EFI variables, it's not...

please check the documentation and your configuration - nobody else will be able to tell you how your system is configured..

what do you mean with the limit no longer takes effect? 150MB/s is 150 x 8 Mbps = 1200 Mbps, accounting for some overhead ~1000Mbs of effective throughput doesn't seem unreasonable?

no, see the docs: https://pve.proxmox.com/pve-docs/chapter-qm.html#_cpu_type

PVE doesn't really care where the backup files are coming from, as long as it can read them..