Possible regression in PVE 9.2.3: owner = VM when migrating ISO attached as media=disk

[Blecherer]

Environment
Proxmox VE: 9.2.3
Kernel: 7.0.12-1-pve
QEMU: 11.0
Cluster: 2 Nodes
Shared VM storage: Ceph RBD
Local storage on both nodes:
/var/lib/vz
same storage ID: local
VM configuration

OpenCore is attached like this:
ide0: local:iso/opencore-osx-proxmox-vm.iso,cache=unsafe,media=disk,size=96M

The file exists:
pvesm path local:iso/opencore-osx-proxmox-vm.iso

returns
/var/lib/vz/template/iso/opencore-osx-proxmox-vm.iso

Only this VM references the file:
grep -R "opencore-osx-proxmox-vm.iso" /etc/pve/qemu-server/

returns
/etc/pve/qemu-server/109.conf:
ide0: local:iso/opencore-osx-proxmox-vm.iso,...
Migration error

Live migration immediately aborts with
starting migration of VM 109 to node 'dcmhvx0002'
found local disk 'local:iso/opencore-osx-proxmox-vm.iso' (attached)
can't migrate local disk 'local:iso/opencore-osx-proxmox-vm.iso':
owned by other VM (owner = VM )

ERROR: Problem found while scanning volumes

The interesting part is
owner = VM
There is no VMID.
QEMU command line
Proxmox generates
-device ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0
with
filename=/var/lib/vz/template/iso/opencore-osx-proxmox-vm.iso

The image is opened as
read-only=false
Expected behaviour
Either
migration should succeed if the identical ISO exists on the target node,
or
Proxmox should refuse migration because the storage is local,
or
the error message should identify the actual VM owner.
Instead the migration fails with
owner = VM
without a VMID.
Additional information
This configuration is generated by the popular OSX-PROXMOX installer, which intentionally attaches the OpenCore ISO as
media=disk
instead of a CD-ROM.
The VM itself boots and works correctly.
Only the migration fails.

Question
Is this a known regression in the volume ownership check introduced in Proxmox VE 9.x / QEMU 11, or is attaching an ISO as media=disk no longer a supported migration scenario?

 

[bbgeek17]

I would say there is definitely a problem in the logic here. The ISO cannot be "owned" by the VM, its a shared object. The reason its "VM" is due to failing to determine the owner's ID and the ID value not being set.

Historically you would get an error saying that migration with local ISO is not possible. The regression here is the less clear error message.

I did a quick search in the bugzilla and did not see this reported yet, so it may be worth filing there - https://bugzilla.proxmox.com/

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[fiona]

Hi,
as discussed in an older thread, it's not an actual ISO, so the installer should pretend that it is. There is the import content type, that can be used instead (also usable via UI): https://pve.proxmox.com/pve-docs/chapter-qm.html#_ova_ovf_import

The installer probably changes the configuration without using our CLI or API, because it should not even be possible to set such a disk:

[I] root@pve9a1 ~# qm set 100 --scsi2 dir:iso/new.iso,media=disk
400 Parameter verification failed.
scsi2: explicit 'media=cdrom' is required for iso images
qm set <vmid> [OPTIONS]
[I] root@pve9a1 ~ [255]# qm create 100 --scsi2 dir:iso/new.iso,media=disk
400 Parameter verification failed.
scsi2: explicit 'media=cdrom' is required for iso images
qm create <vmid> [OPTIONS]