Ubuntu cloud images end in .img but are qcow2 inside. When you uploaded one to a storage for import, the Proxmox VE interface renamed it to .img.raw, so the import treated it as a raw disk and the guest would not boot. On 30 September 2026 the Proxmox team applied our fix for that bug along with four others: six commits across pve-manager and proxmox-widget-toolkit.
What we changed in Proxmox VE
| Report | What the fix changes |
|---|---|
| #8015 | Uploading or downloading a .img image asks for its format instead of appending .raw |
| #6475 | The upload window shows only the file name, without C:\fakepath\ |
| #5608 | PCI, USB and directory mapping names are validated as you type, as in the API |
| #7108 | An IPSet no longer offers aliases it already holds |
| #6943 | The network selector shows IPv6 interface comments |
A patch goes by mail, not by pull request
The Proxmox repositories are read-only for contributors. Code arrives as a patch sent with git send-email to the pve-devel list, from an author with a signed contributor licence agreement. Reviewers answer in the thread with Reviewed-by and Tested-by trailers, and a Proxmox developer applies the patch.
We sent four fixes on 29 September, #6475 three days earlier. All five landed the next day.
What this means if you run Proxmox
The people who write these fixes also deploy Proxmox for clients and migrate their machines off VMware. When a bug sits in Proxmox itself, we fix it upstream, and your servers stay on the official packages, with no local patches for the next update to overwrite.
Setting up or taking over Proxmox is covered on our Servers and DevOps page.
Was this post helpful?
