[Bug] Migrated disk(s) not attached as VirtIO

[ajoergensen]

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

When explicitly setting disk bus to 'virtio' in the migration wizard, the disks are attached as SCSI in the Proxmox VM

Steps to Reproduce

1. Select virtio as disk bus type
2. Migrate
3. Disk is attached as scsiX

Expected behavior

Disks should be attached as virtioX

Environment

• PegaProx Version: Beta 0.9.13.2
• Installation Method: Manual
• OS: Debian 13
• Browser: Firefox 152
• Behind Reverse Proxy? nginx
• UI? Default

Logs

[14:09:12] Disk 0: cloned → transferred → attached as scsi0

Screenshots

Checklist

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

[mkellermann97]

Good find — clean one. The migration config builder had an allowlist that accepted scsi/sata/ide but not virtio, so your explicit virtio pick silently fell back to the detected bus (scsi). Fixed on Testing (v2p): virtio is now honored and attaches as virtioN. It ships in the next build — heads-up that a virtio boot disk needs virtio-blk in the guest (Linux: built in; Windows: the virtio drivers, which the wizard's driver-injection option can pre-stage). Thanks for the precise repro and the log line — opencollective.com/pegaprox keeps the fixes coming. — Marcus

[mkellermann97]

Fixed in v0.9.13.3 — the migration wizard now honours an explicit virtio disk bus (it was silently falling back to SCSI). — Marcus