+++ This bug was initially created as a clone of Bug #1811425 +++ There is a libvirt regression caused by: 63469116cc virDomainDiskTranslateSourcePool: split code to setup one storage source which tries to fix the bug 1804603. The problem is the referenced commit introduced a typo which caused libvirt to drop sources for all disks which have startup policy configured.
Patch posted upstream: https://www.redhat.com/archives/libvir-list/2020-March/msg00241.html
Pushed upstream as: 3918dbd84e virDomainDiskTranslateSourcePool: Check for disk type correctly v6.1.0-69-g3918dbd84e
To POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2020-March/msg00204.html
Hi Michal, I start domain with cdrom disk with startupPolicy='optional' failed, I think it may be a new bug, can you help to review it? Thank you in advance. Test Version: libvirt-6.0.0-10.el8 Test Steps: 1. Prepare a guest xml with cdrom disk with startupPolicy='optional'. # vim lmn.xml ... <disk type='file' device='cdrom'> <driver name='qemu' type='raw' cache='none'/> <source file='/var/lib/libvirt/images/non-exist.img' startupPolicy='optional'/> <target dev='sda' bus='sata'/> <readonly/> </disk> ... 2. Define the guest and start it. # virsh define lmn.xml; virsh start lmn Domain lmn defined from lmn.xml error: Failed to start domain lmn error: Cannot access storage file '/var/lib/libvirt/images/non-exist.img': No such file or directory
I cannot reproduce on upstream. I will investigate further.
Well, I can't reproduce downstream neither. Can you attach debug logs please?
Thanks for your review and test, I also cannot reproduce in other machine with the same libvirt version. So I think may there are some problems on my machine or guest xml, I'll check again.
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, 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/RHBA-2020:2017