惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Engineering at Meta
Engineering at Meta
G
Google Developers Blog
WordPress大学
WordPress大学
M
MIT News - Artificial intelligence
D
DataBreaches.Net
云风的 BLOG
云风的 BLOG
爱范儿
爱范儿
Microsoft Security Blog
Microsoft Security Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Blog — PlanetScale
Blog — PlanetScale
T
Tailwind CSS Blog
S
SegmentFault 最新的问题
阮一峰的网络日志
阮一峰的网络日志
博客园 - 三生石上(FineUI控件)
酷 壳 – CoolShell
酷 壳 – CoolShell
Recent Announcements
Recent Announcements
T
The Blog of Author Tim Ferriss
I
InfoQ
MyScale Blog
MyScale Blog
V
V2EX
B
Blog
罗磊的独立博客
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Possible regression in PVE 9.2.3: owner = VM when migrati...
invalid@exam · 2026-06-25 · via Proxmox Support Forum

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?