Hi
@ssevasta ,
This is a free community support forum, so posting here does not open an official support case. For formal case tracking, you would need to have an active support subscription.
That said, a staff member may still notice your post and take a look. However, you haven’t provided any useful technical details, such as an environment description, logs, or debug information.
In general, the error you’re seeing is typically caused by a stuck QEMU process. There are many possible ways to end up in this situation, the error itself is just a symptom.
If you can start from scratch and reliably reproduce the problem with a defined set of steps, please share that here as well. The best way for developers to address the issue is with a reproducible scenario.
Alternatively, you can report the problem via Proxmox Bugzilla, though given the limited details and the involvement of a third-party, unsupported application, it may be difficult to gain much traction there.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
