Skip to main content
Question

Proxmox Backup needs Update to Qemu Version 10

  • September 8, 2026
  • 1 reply
  • 3 views

Forum|alt.badge.img+4

Hi,

we have 2 Problems:

we are on Commvault 11.40.69. Proxmox 9.2.11

1)

With https://lore.proxmox.com/all/6e3ffc1e-ccfc-4ec6-93f7-03bef79c8b78@proxmox.com/T/

Proxmox needs Qemu Version 10 to support the Snapshot as Volume Chain.

Is there a plan to support Qemu Version 10 ? With a Maintenance Release ?

 

2)

A Restore of a Vmware VM to Proxmox work, but the Network Config is not converted.
469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKWrapper::CProxmoxConnection::LogError() - Error: [] [400]. POST [https://du1devpve02.tq-net.de:8006/api2/json/nodes/du1devpve01/qemu/100/config]
469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKWrapper::CProxmoxConnection::LogError() -   Err: [HTTP/1.1 400 Parameter verification failed.]
469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKWrapper::CProxmoxConnection::LogError() -   Req: [net0=e1000%3D00%3A0c%3A29%3Aa5%3Ae2%3A5e%2Cbridge%3Dvds01-LBT%20%E2%80%93%20vlan586%20%E2%80%93%20srv-t1-linux%20-%2010.150.86.0-24%20%28vDS01%29]
469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKWrapper::CProxmoxConnection::LogError() -   Rsp: [{"errors":{"net0":"invalid format - format error\nnet0.bridge: invalid format - invalid bridge ID 'vds01-LBT – vlan586 – srv-t1-linux - 10.150.86.0-24 (vDS01)'\n\n"},"message":"Parameter verification failed.\n","data":null}]


Regards,

 

Peter Rupp





 

1 reply

Forum|alt.badge.img+10
  • Vaulter
  • September 8, 2026

Hi Peter,

Thank you for raising this query.
I can see support added for snapshot as volume chain in Commvault 11.42.73. Unfortunately there is no backport for 11.40.

For your restore issue, it is stating the Proxmox cannot verify the creation request as the formatting is invalid. So it dumps the request. It looks like its trying to populate with invalid data, for example in my Proxmox server it populates:

Network Device (net0)   e1000=<MAC address>,bridge=vmbr0,firewall=1

Instead of bridge=<bridgename> it’s trying to create bridge=ds01-LBT – vlan586 – srv-t1-linux - 10.150.86.0-24 (vDS01)

While testing to see if that would be a valid name I get this in Proxmox VE it states the name field length cannot exceed 10 alphanumeric characters.

I would suggest creating a test VM, create a network with a short network name and test that restore. If that succeeds we can confirm the problem and rom there networks can be renamed in VMware or a support incident raised to see if the cross-hypervisor restore process can rename them.

Hopefully this helps.