On Tue, Jun 9, 2015 at 9:08 AM, Cole Robinson <crobinso(a)redhat.com> wrote:
On 06/09/2015 09:57 AM, Andrew Ruch wrote:
> I recently upgraded from Fedora 20 to Fedora 22. I'm running
> libvirt-184.108.40.206-1.fc22.x86_64 and virt-manager-1.2.0-1.fc22.noarch.
> I'm no longer able to disconnect a CD from the CDROM device if the
> device is enabled as a boot device. I'm using virt-manager to manage
> the guests.
> This is my workflow. I have a RHEL 6 installer with a custom
> kickstart. I install the guest using the my custom RHEL ISO, meaning
> the CDROM is enabled as a boot device. During the post phase of the
> kickstart, the RHEL ISO is ejected and a custom configuration ISO is
> inserted to finish the custom part of the installation. This used to
> work in Fedora 20. I now get the following error:
> unsupported configuration: boot order 1 is already used by another device
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/addhardware.py", line
> 1420, in change_config_helper
> define_func(devobj=devobj, do_hotplug=True, **define_args)
> File "/usr/share/virt-manager/virtManager/domain.py", line 804, in
> File "/usr/share/virt-manager/virtManager/domain.py", line 1111, in
> File "/usr/share/virt-manager/virtManager/domain.py", line 1041, in
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 508, in
> if ret == -1: raise libvirtError ('virDomainAttachDevice()
> failed', dom=self)
> libvirtError: unsupported configuration: boot order 1 is already used
> by another device
> I also noticed that even after install, if the CDROM device is enabled
> as a boot device, no media can be connected/disconnected while the
> guest is running. I know this could be avoided by disabling it as a
> boot device, but I would expect it to work more like it used to in
> Fedora 20. Is there something else I can set in my configuration that
> would allow me to connect/disconnect media if it's a bootable device?
> Or do I need to open an issue?
There's a new virt-manager version in f22... probably won't fix it but it's
worth trying. sudo yum --enablerepo=updates-testing update virt-manager
If it still reproduces, please reproduce with virt-manager --debug, and attach
the output to a fedora virt-manager bug report and I'll take a look.
I didn't find any updates to virt-manager, but I did download the
newest libvirt in the "updates-testing" repo. Same problem. I created
Bugzilla Issue 1229819.