Do this: * New VM * CDROM install * Customize before install * Add Hardware -> CDROM * New CDROM is assigned target=hda, qemu attempts to boot it first It's happening, because the install media is tracked internally as a transient 'install_device', which is removed from the final XML, which is what we show in the 'customize' wizard. IMO the install_device concept doesn't make much sense and only exists for historical reasons. If a user requests a CDROM install, we should just leave the CDROM _device_ permanently attached to the VM (but maybe eject the media). The more backportable fix might be to show the install time XML in 'customize' wizard, but that will have some other weirdness, like the install CDROM not being removable.
Fixed upstream: commit bfa5762d9e1e7ef1d909e8689c132f85196e00aa Author: Cole Robinson <crobinso> Date: Sat Jun 6 16:56:03 2015 -0400 guest: Add install cdrom in set_defaults, not start_install (bz 1220180)
virt-manager-1.2.1-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/virt-manager-1.2.1-1.fc22
Package virt-manager-1.2.1-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virt-manager-1.2.1-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9686/virt-manager-1.2.1-1.fc22 then log in and leave karma (feedback).
virt-manager-1.2.1-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.