Proxmox VE: our changes to an open source project
A server virtualisation platform with KVM machines and LXC containers, managed from the browser. It takes fixes through the pve-devel mailing list rather than pull requests.
- Language
- Perl and JavaScript
- Repositories
- pve-manager, proxmox-widget-toolkit
- Project site
- proxmox.com
Every change merged into Proxmox VE
Newest first, as written on git.proxmox.com. Next to the date is the short hash of the commit a maintainer applied; the row opens it.
September 2026
6- 29 Septebf648dfix #8015: ui: download url: let the user choose the .img image formatpve-manager
- 29 Septb92a9adfix #6943: ui: network selector: show comments of IPv6 entries (proxmox-widget-toolkit)proxmox-widget-toolkit
- 29 Sept2380c3dfix #8015: ui: upload: let the user choose the .img image formatpve-manager
- 29 Sept55c76c2fix #5608: ui: resource mappings: validate the name like the API doespve-manager
- 29 Sept8efee57fix #7108: ui: ipset: do not offer aliases that are already addedpve-manager
- 26 Septe42092efix #6475: ui: upload: only show the file name of the selected filepve-manager
What these fixes changed
Interface fixes in pve-manager and proxmox-widget-toolkit: file upload shows only the file name, ipset no longer offers aliases already added, upload and download-from-URL let you pick the .img format, resource mapping names are validated the way the API does, and the network selector shows comments of IPv6 entries.
Patches through pve-devel, not pull requests
Proxmox does not take pull requests. Patches go by email to pve-devel after signing a contributor licence agreement, and a maintainer applies them to the repository.
What it taught us
In a large infrastructure project the interface must validate data the same way the API does, or users only learn about an error after submitting. We also learned to work through a mailing list: a patch has to stand on its own, without a comment thread to explain it.
A Bugzilla report
A numbered bug described by users. Our patches answer these reports:
- #64751 patch
- #71081 patch
- #80152 patches
- #56081 patch
- #69431 patch
A patch via git send-email
To the pve-devel list, explained in the email. From us: 6 patches.
Review on the list
Review and testing by the project's maintainers, on the same list.
Applied in the repository
A commit with our authorship on git.proxmox.com:
Proxmox VE among all our changes
Day by day from 5 September 2026 to 11 October 2026. A column is every change merged that day, the accent is the changes in Proxmox VE.
- Changes in Proxmox VE
- Changes in other projects
6 merged changes in Proxmox VE
The first on 26 September 2026, the latest on 29 September 2026.
On the same days
Changes of ours were also merged into: compromise, python-benedict.
Questions about our changes to Proxmox VE
Where these changes come from, who merged them and whether we can fix something in your library.
Read next
More about this work and the other projects with our changes.
Using Proxmox VE in your project?
If something in it does not work, we fix it at the source and leave a workaround until the release. We reply within an hour.