[Bug]

[ijaggi1974]

Hey there! 👋 Thanks for taking the time to report this bug — we appreciate it!

Please keep in mind: PegaProx is developed and maintained entirely by volunteers in our free time. We do our best, but we can't work magic 🪄 — please be patient, we'll get to your issue as soon as we can.

Want to help keep PegaProx alive?

• ⭐ Star the project — it's free and helps a lot!
• 💖 Become a Sponsor — helps us dedicate more time to development
• 🤝 Contributing code or docs is always welcome too!

---

Describe the bug

While Migrating Vm's from VMware esxi to Proxmox getting error FAILED: qemu-img not found on target node. Install qemu-utils: apt install qemu-utils this happens while migrating to Proxmox 9.1

Steps to Reproduce

1. Migrate from Vmware Exsi to Proxmox,
2. Check Tasks and Event there we get the error

Expected behavior

Migration from Vmware Esxi VM's to Proxmox to go smoothly, so it was identified that the name of the packge qemu-utils has been changed in Proxmox 9.1 to pve-qemu-kvm. So qemu-utils has been checked by Pegaprox for migration.

Environment

• PegaProx Version: 0.9.13
• Installation Method: git Clone
• OS: Ubuntu 24.04
• Browser: Chrome 148
• Behind Reverse Proxy? No
• UI?

Logs

Migration Log - machine01 (f04acbff)
Close
[09:22:01] Phase: planning
[09:22:01] Planning migration of 'machine01' from 192.168.10.100
[09:22:02] VM has 2 disk(s), 14157.0 GB total
[09:22:02] Testing SSH to 192.168.10.100...
[09:22:03] SSH OK:192.168.10.100
[09:22:55] Tools missing: qemu-img, qemu-nbd, sshfs, sshpass (install for more transfer methods)
[09:22:55] FAILED: qemu-img not found on target node. Install qemu-utils: apt install qemu-utils
[09:22:55] Phase: failed
Error: qemu-img not found on target node. Install qemu-utils: apt install qemu-utils

Screenshots

Checklist

• I have searched existing issues to make sure this is not a duplicate
• I am using the latest version of PegaProx

[mkellermann97]

Thanks for the detailed report @ijaggi1974, and for catching this — the failure mode is real on PVE 9.x.

Important — do NOT run the apt install qemu-utils that our own error message suggests. On PVE 9.x that package conflicts with pve-qemu-kvm and can break the Proxmox installation. Our error string is actively bad advice on the newer PVE release; flagging it for rewrite.

What's happening: PegaProx's v2p preflight checks for qemu-img via which qemu-img on the target PVE node. On PVE 8 and below that binary was reliably in PATH via Debian's qemu-utils. On PVE 9.x the userland shape changed and the binary either lives elsewhere or isn't installed by default depending on the install image.

Two things would help us land the proper fix:

1. On your PVE 9.1 node, run dpkg -l | grep -E 'qemu-utils|pve-qemu' and find /usr -name qemu-img 2>/dev/null — that'll tell us whether qemu-img exists on PVE 9.1 (just in a different path) or is genuinely absent.

2. @MrMasterbay knows the PVE-side packaging history far better than I do — flagging for him to weigh in on the right per-version detection logic before we ship a fix that might recommend something equally dangerous on a different PVE generation.

opencollective.com/pegaprox if PegaProx is earning its keep elsewhere in your stack.

— Marcus

[ijaggi1974]

Hello. Thanks for the prompt response my* pve version is 9.1* as per your request please find the results 1. On your PVE 9.1 node, run dpkg -l | grep -E 'qemu-utils|pve-qemu' and find /usr -name qemu-img 2>/dev/null — that'll tell us whether qemu-img exists on PVE 9.1 (just in a different path) or is genuinely absent. *dpkg -l | grep -E 'qemu-utils|pve-qemu' ii pve-qemu-kvm 11.0.0-4 amd64 Full virtualization on x86 hardware* * find /usr -name qemu-img 2>/dev/null* * /usr/bin/qemu-img*

…

On Wed, 3 Jun 2026 at 13:42, mkellermann97 ***@***.***> wrote: *mkellermann97* left a comment (PegaProx/project-pegaprox#520) <#520 (comment)> Thanks for the detailed report @ijaggi1974 <https://github.com/ijaggi1974>, and for catching this — the failure mode is real on PVE 9.x. *Important — do NOT run the apt install qemu-utils that our own error message suggests.* On PVE 9.x that package conflicts with pve-qemu-kvm and can break the Proxmox installation. Our error string is actively bad advice on the newer PVE release; flagging it for rewrite. What's happening: PegaProx's v2p preflight checks for qemu-img via which qemu-img on the target PVE node. On PVE 8 and below that binary was reliably in PATH via Debian's qemu-utils. On PVE 9.x the userland shape changed and the binary either lives elsewhere or isn't installed by default depending on the install image. Two things would help us land the proper fix: 1. On your PVE 9.1 node, run dpkg -l | grep -E 'qemu-utils|pve-qemu' and find /usr -name qemu-img 2>/dev/null — that'll tell us whether qemu-img exists on PVE 9.1 (just in a different path) or is genuinely absent. 2. @MrMasterbay <https://github.com/MrMasterbay> knows the PVE-side packaging history far better than I do — flagging for him to weigh in on the right per-version detection logic before we ship a fix that might recommend something equally dangerous on a different PVE generation. opencollective.com/pegaprox if PegaProx is earning its keep elsewhere in your stack. — Marcus — Reply to this email directly, view it on GitHub <#520?email_source=notifications&email_token=ANSZXSZ6FPKVXWGQD5XLEML457MXNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRGAZTINRWG43KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4610346676>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANSZXS674UWIXSGWKB3TA6D457MXNAVCNFSM6AAAAACZW5SCW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMJQGM2DMNRXGY> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ANSZXS7FCEG24YHXEHDBXET457MXNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRGAZTINRWG43KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ANSZXS37OA3JGGEF6OO5V6T457MXNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRGAZTINRWG43KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

--

-- Regards, Inderjeet Singh Jaggi +919821233369

[mkellermann97]

Thanks @ijaggi1974 — your diag was exactly what we needed.

The takeaway from your output: pve-qemu-kvm 11.0.0-4 is installed and /usr/bin/qemu-img exists, so the binary is there. PegaProx was running which qemu-img via non-interactive SSH and getting a false-negative — most likely a PATH-stripping shell context on PVE 9.x, sometimes a which packaging shape change between PVE generations. Either way, the probe was too fragile.

Fixed on Testing as b5521cc: new preflight uses command -v (POSIX shell builtin, doesn't depend on the which binary) plus an absolute-path fallback that walks the six canonical bin/sbin dirs. Either path success counts. Also rewrote our error message so the dangerous apt install qemu-utils line is gone — replaced with the actual PVE-correct advice (apt install pve-qemu-kvm to reinstall if anything's missing, explicit DON'T on the qemu-utils path).

Once ghcr.io/pegaprox/pegaprox:latest rebuilds with the next release, your migration should clear the preflight and move to the actual ESXi-source steps. Reopen if it still bails on tool detection after the update.

opencollective.com/pegaprox — thanks for the careful triage info, that's what makes these obscure fixes ship-able.

— Marcus

[ijaggi1974]

Hello Team, Thanks for the update, hope the release is coming soon.

…

On Thu, 4 Jun 2026 at 12:47, mkellermann97 ***@***.***> wrote: *mkellermann97* left a comment (PegaProx/project-pegaprox#520) <#520 (comment)> Thanks @ijaggi1974 <https://github.com/ijaggi1974> — your diag was exactly what we needed. The takeaway from your output: pve-qemu-kvm 11.0.0-4 is installed and /usr/bin/qemu-img exists, so the binary is there. PegaProx was running which qemu-img via non-interactive SSH and getting a false-negative — most likely a PATH-stripping shell context on PVE 9.x, sometimes a which packaging shape change between PVE generations. Either way, the probe was too fragile. Fixed on Testing as b5521cc: new preflight uses command -v (POSIX shell builtin, doesn't depend on the which binary) plus an absolute-path fallback that walks the six canonical bin/sbin dirs. Either path success counts. Also rewrote our error message so the dangerous apt install qemu-utils line is gone — replaced with the actual PVE-correct advice (apt install pve-qemu-kvm to reinstall if anything's missing, explicit DON'T on the qemu-utils path). Once ghcr.io/pegaprox/pegaprox:latest rebuilds with the next release, your migration should clear the preflight and move to the actual ESXi-source steps. Reopen if it still bails on tool detection after the update. opencollective.com/pegaprox — thanks for the careful triage info, that's what makes these obscure fixes ship-able. — Marcus — Reply to this email directly, view it on GitHub <#520?email_source=notifications&email_token=ANSZXSYA5TRMQPYG3TAS5HL46EPBNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRHE4DSOBYGAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4619898802>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANSZXSZJ56VROUUT6ITQBXD46EPBNAVCNFSM6AAAAACZW5SCW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMJZHA4TQOBQGI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ANSZXS4UG6HZWTH6I4O5NA346EPBNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRHE4DSOBYGAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ANSZXS3EPLNLRUDVVALBHFT46EPBNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRHE4DSOBYGAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

--

-- Regards, Inderjeet Singh Jaggi +919821233369

[mkellermann97]

@ijaggi1974 — that's the missing piece, thanks. qemu-img is present at /usr/bin/qemu-img (shipped by your pve-qemu-kvm 11.0.0-4), so this was never a missing binary — it was our preflight using which, which doesn't resolve reliably under the non-login SSH shell PegaProx opens.

Fix is on Testing as b5521cc: the probe now falls back to checking /usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin directly, so it finds /usr/bin/qemu-img regardless of PATH. And to be clear — do NOT run the apt install qemu-utils our old error suggested; that line is gone too, since it can break pve-qemu-kvm on PVE 9.x.

If you can retest once the next build drops, that'd confirm it on your side. opencollective.com/pegaprox if PegaProx is pulling its weight in your stack.

— Marcus

[mkellermann97]

Shipped in v0.9.12.2. The preflight no longer leans on which — it resolves qemu-img via an absolute-path fallback (/usr/bin/qemu-img on your pve-qemu-kvm build), so the bogus "missing binary" is gone, and the dodgy apt advice is out too. Pull and give the migration another shot. Closing for now — reopen if it still trips. — MK

[ijaggi1974]

Hello mkellermann97, I have updated pregaptox to 0.9.12.2 still same error [image: image.png] still same error [image: image.png]

…

On Sat, 6 Jun 2026 at 03:19, mkellermann97 ***@***.***> wrote: Closed #520 <#520> as completed. — Reply to this email directly, view it on GitHub <#520?email_source=notifications&email_token=ANSZXS4DMZQ6MRYJUCVH6ST46M563A5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENRUGA2TANJUGA4TNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ#event-26405054096>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANSZXS3A3SSWDCC5QPWDA5346M563AVCNFSM6AAAAACZW5SCW2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRWGQYDKMBVGQYDSNQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ANSZXS47B6WEG66VQOPHV5D46M563A5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENRUGA2TANJUGA4TNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FKMZXW65DFOJPWS33T> and Android <https://github.com/notifications/mobile/android/ANSZXSYVEOSL2RV636O3PFD46M563A5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENRUGA2TANJUGA4TNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FOMZXW65DFOJPWC3TEOJXWSZA>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

--

-- Regards, Inderjeet Singh Jaggi +919821233369

[mkellermann97]

Reopening — thanks for retesting, and sorry, my close was too quick.

In 0.9.12.2 the preflight doesn't use which anymore: it runs command -v qemu-img and, if that comes up empty, walks /usr/bin (and the other sbin/bin dirs) for the binary. So if /usr/bin/qemu-img is really there it shouldn't trip. Two things would tell me what's actually happening, since the screenshot doesn't reach me as readable text:

1. The exact error line from the migration log — the wording changed in 0.9.12.2, so it'll confirm whether the new code is really running.
2. On the target Proxmox node: output of ls -l /usr/bin/qemu-img and command -v qemu-img.

And just to rule it out — did you docker compose pull + recreate the container (or run the in-app updater)? Want to be sure the image actually rolled to 0.9.12.2 and you're not on a cached layer.

PegaProx runs on donations (opencollective.com/pegaprox), but this one's our bug — let's nail it.

— MK

[ijaggi1974]

root@pve500:# ls -l /usr/bin/qemu-img
-rwxr-xr-x 1 root root 2245776 Feb 17 18:22 /usr/bin/qemu-img
root@pve500:# command -v qemu-img
/usr/bin/qemu-img

I have installed Pregaprox on a vm not as docker.

[mkellermann97]

Thanks — that's the useful bit: qemu-img is right there and command -v qemu-img resolves it, so the binary was never the problem. Which means that VM is almost certainly still running the old preflight: pre-0.9.12.2 it used which over a non-interactive SSH session, which false-negatives even though command -v works fine for you interactively. 0.9.12.2 switched to command -v — so if it's still failing, the new migration code didn't actually land on that box.

Quickest way to confirm — grep the installed file:

find / -name v2p.py -path '*pegaprox*' 2>/dev/null
grep -n 'command -v qemu-img\|which qemu-img' <that path>

If it shows which qemu-img, you're still on the old code and the in-app update didn't fully replace it (we just tightened that update path). Re-run the update, or paste the exact error line and I'll point you at the single file to drop in.

Donation-funded over at opencollective.com/pegaprox — appreciate you digging in with me on this.

— MK

[ijaggi1974]

pegaprox-bom01-in:~# find / -name v2p.py -path '*pegaprox*' 2>/dev/null /opt/PegaProx/config/backups/pegaprox_Beta_0.9.1_20260507_061440/pegaprox/core/v2p.py /opt/PegaProx/config/backups/pegaprox_Beta_0.9.9_20260508_070823/pegaprox/core/v2p.py /opt/PegaProx/config/backups/pegaprox_Beta_0.9.9.3_20260517_142017/pegaprox/core/v2p.py /opt/PegaProx/pegaprox/core/v2p.py /opt/PegaProx/backups/backup_0.9.12.1_20260606_064333/pegaprox/core/v2p.py /opt/PegaProx/backups/backup_0.9.10.3_20260525_031315/pegaprox/core/v2p.py /opt/PegaProx/backups/backup_0.9.10.2_20260519_035412/pegaprox/core/v2p.py /opt/PegaProx/backups/backup_0.9.9.3_20260517_155652/pegaprox/core/v2p.py /opt/PegaProx/backups/backup_0.9.9.1_20260512_062443/pegaprox/core/v2p.py /opt/PegaProx/backups/backup_0.9.11_20260602_091506/pegaprox/core/v2p.py

…

On Sat, 6 Jun 2026 at 14:59, mkellermann97 ***@***.***> wrote: *mkellermann97* left a comment (PegaProx/project-pegaprox#520) <#520 (comment)> Thanks — that's the useful bit: qemu-img is right there and command -v qemu-img resolves it, so the binary was never the problem. Which means that VM is almost certainly still running the *old* preflight: pre-0.9.12.2 it used which over a non-interactive SSH session, which false-negatives even though command -v works fine for you interactively. 0.9.12.2 switched to command -v — so if it's still failing, the new migration code didn't actually land on that box. Quickest way to confirm — grep the installed file: find / -name v2p.py -path '*pegaprox*' 2>/dev/null grep -n 'command -v qemu-img\|which qemu-img' <that path> If it shows which qemu-img, you're still on the old code and the in-app update didn't fully replace it (we just tightened that update path). Re-run the update, or paste the exact error line and I'll point you at the single file to drop in. Donation-funded over at opencollective.com/pegaprox — appreciate you digging in with me on this. — MK — Reply to this email directly, view it on GitHub <#520?email_source=notifications&email_token=ANSZXS6FBQKPZJ3MJNEQX4L46PP7NA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRTHAYTCMZYGM22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4638113835>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANSZXS73F4GGLNZQRFGLY4T46PP7NAVCNFSM6AAAAACZW5SCW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMZYGEYTGOBTGU> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ANSZXS2WEVI6NJ6PYXCKTWT46PP7NA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRTHAYTCMZYGM22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ANSZXS3BGT45RKW4QXUVBFL46PP7NA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRTHAYTCMZYGM22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

--

-- Regards, Inderjeet Singh Jaggi +919821233369