Proxmox VE 8.4 released!

Hi,
Hi @t.lamprecht,
I have tried to use the sample to integrate the borg module to our Proxmox Server, but I haven't see any change on the GUI to check the borg.
Can you introduce some document about how to integrate the borg module.
if you have applied the patches, you can configure an external Borg storage with the pvesm command, then it will show up in the UI.
Note however that this plugin is currently only intended for backup provider developers as a guide line, it is not officially supported for production use!
 
  • Like
Reactions: ProxKen
No impact? So even when using the CLI command: vzdump <vmid> it still doesn't do lzo compression by default after that change? That would be surprising.

AFAIK, any backup jobs specific settings will override those in the vzdump.conf .

If you are looking for a GUI default - I'm not sure why you would want that, you can easily select it from the dropdown-menu (maybe laziness or for other sysadmins?).

Note: I have not tested if changing the compression in the vzdump.conf file changes the default chosen in the GUI - but I can understand that it does not.
Fiona has acknowledged this issue, and I will do a feature request so it applies to the GUI not just CLI.
 
Last edited:
  • Like
Reactions: gfngfn256
What do you expect etcher to do differently than dd? (As it happens, I did also try etcher as I was originally making the usb stick on a mac before I switched to linux to remove variables. 8.4 doesn't work when written with etcher or dd, 7.4 worked with dd.)
i have had rufus and other tools fail where balena etcher works (i have been doing a lot of testing of ISOs over the last year) also Ventoy has been extremely problematic with all sorts of weird issue, others have the same experience, rufus is generally good, until it isn't - not sure what the issue is there, ventoy's weird mounting logic is problematic for certain images depending on what the initramfs has in terms of drivers in the image
 
I did also try etcher as I was originally making the usb stick on a mac
From the official docs; Instructions for macOS
before I switched to linux to remove variables
Instructions for GNU/Linux


i have had rufus and other tools fail where balena etcher works (i have been doing a lot of testing of ISOs over the last year) also Ventoy has been extremely problematic with all sorts of weird issue, others have the same experience, rufus is generally good, until it isn't - not sure what the issue is there, ventoy's weird mounting logic is problematic for certain images depending on what the initramfs has in terms of drivers in the image
I agree (search these forums) on the inconsistent experience of users trying to install/boot from their "created" USB medium. There is quite a bit in the docs worth looking at in this regard. As you will see there:
The Proxmox VE installation media is a hybrid ISO image. It works in two ways:
  • An ISO image file ready to burn to a CD or DVD.
  • A raw sector (IMG) image file ready to copy to a USB flash drive (USB stick).
This itself is probably one of the causes for the inconsistent experience.

Also see the note in the section Using the Proxmox VE Installer:
Make sure that booting from the installation medium (for example, USB) is enabled in your server’s firmware settings. Secure boot needs to be disabled when booting an installer prior to Proxmox VE version 8.1.

This change is probably also effecting the OP's experience.
 
  • Like
Reactions: scyto
Hi,

if you have applied the patches, you can configure an external Borg storage with the pvesm command, then it will show up in the UI.
Note however that this plugin is currently only intended for backup provider developers as a guide line, it is not officially supported for production use!
Thank you for your feedback. One more question: when will Proxmox officially support backup provider for production use?
 
Hi,
Thank you for your feedback. One more question: when will Proxmox officially support backup provider for production use?
third-party backup providers can already rely on the API and implement a solution. It is supported for production use. But not the example plugins, those are just examples.
 
Hi,

third-party backup providers can already rely on the API and implement a solution. It is supported for production use. But not the example plugins, those are just examples.
Yes, but do you have any document about how to integrate the plugin? I just see the example, thus I don't understand how to implement it. I'm a new bie with this. Please help to support. Thank you
 
Yes, but do you have any document about how to integrate the plugin? I just see the example, thus I don't understand how to implement it. I'm a new bie with this. Please help to support. Thank you
Integrate as in being a user (admin) or are you a developer? For the former the plugin creator should provide you with instructions, for the latter you need to basically do the same thing as for custom storage plugins, and IIRC the examples have debian packaging definitions included one can base their work of, and if you want to create a plugin then some level of developer experience is a hard requirement in any case. And specific developer questions are best asked on our mailing list or at least in a separate thread here.
 
  • Like
Reactions: Johannes S
I'd rather resources spun on an uid/gid resource mapping interface integrated into PVE… wouldn't that be glorious ? :dream:
yes, its one of the reasons i kept with docker in a VM for each of my docker swarm VM nodes on top of each proxmox node

@blackpaw give virtioFS is part of the qemu/kvm toolkit and LXC uses none of that, probably not. If you want an alternate way to do bind mounts create a ceph rbd per container and then mount that in the container using cephfuse (userland).... not sure that is easier that permissions mapping :-)
 
  • Like
Reactions: Johannes S