Created attachment 1847862 [details] migration video Description of problem: When trying to migrate Win10 VM with CD-ROM disk the migration fails with Event message "VirtualMachineInstance migration uid ... failed. reason:Live migration failed error encountered during MigrateToURI3 libvirt api call: virError(Code=8, Domain=10, Message='invalid argument: NBD URI must be supplied when migration URI uses UNIX transport method') Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create started Windows 10 VM with bootsource from http://cnv-qe-server.rhevdev.lab.eng.rdu2.redhat.com/files/cnv-tests/windows-images/win_10.qcow2 2. Note the VM Node 3. Launch VM migration Actual results: VM Node did not change Events tab contains the error messages: 1) server error. command Migrate failed: "migration job already executed" 2) VirtualMachineInstance migration uid ... failed. reason:Live migration failed error encountered during MigrateToURI3 libvirt api call: virError(Code=8, Domain=10, Message='invalid argument: NBD URI must be supplied when migration URI uses UNIX transport method') Expected results: VM Node changes Additional info:
This should be the core issue, move the bug to virt for investigation.
Created attachment 1847886 [details] vm yaml
The bug is successfully reproduced. The root cause seems to be that we set the migration as BlockMigration for CDRoms in certain cases. This should be avoided. I'm working on a PR right now and will post it very soon.
PR for bug fix: https://github.com/kubevirt/kubevirt/pull/7004
To verify, repeat steps in description.
verify with build: HCO:[v4.10.0-588] virt-launcher/images/v4.10.0-186 step: 1. create win10 vm with cdrom 2. start win10 vm, login vm and check win10 status. 3. do live migration 4. login vm again and check again. check migration status $ oc get virtualmachineinstancemigrations.kubevirt.io vm-win10-migration-2fnvb NAME PHASE VMI vm-win10-migration-2fnvb Succeeded vm-win10 migration finished w/o error. move to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Virtualization 4.10.0 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0947