Commit 43f892f
committed
fix(v2p): pick the real device line from
_pvesm_alloc_disk ran `pvesm path <vol> 2>&1` and took line 0 as the device
path. With 2>&1 a storage plugin that logs a warning to stderr (e.g. a custom
plugin 'implementing an older storage API') prints it BEFORE the path, so
line 0 is the warning and the real path is missed — _ensure_block_device then
fails and the disk transfer aborts.
Now scan for the line that actually looks like a device path (/dev/...) or a
librbd URI (rbd:...) instead of blindly taking line 0.
Verified end-to-end on a real ESXi->Proxmox->Ceph RBD migration (Windows
Server 2025, 90 GB): the migrated RBD holds a real GPT/UEFI disk (EFI System
+ MSR + NTFS basic-data + WinRE) — data landed on the real block device.
Refs #538pvesm path output1 parent fc92dd5 commit 43f892f
1 file changed
Lines changed: 7 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3280 | 3280 | | |
3281 | 3281 | | |
3282 | 3282 | | |
3283 | | - | |
| 3283 | + | |
| 3284 | + | |
| 3285 | + | |
| 3286 | + | |
| 3287 | + | |
| 3288 | + | |
| 3289 | + | |
3284 | 3290 | | |
3285 | 3291 | | |
3286 | 3292 | | |
| |||
0 commit comments