[fedora-virt] Cannot disconnect CD if cdrom is boot device

Discussion:

Andrew Ruch

2015-06-09 13:57:39 UTC

Hello,

I recently upgraded from Fedora 20 to Fedora 22. I'm running
libvirt-1.2.13.1-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 define_disk
self.hotplug(**hotplug_kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1111, in hotplug
self.attach_device(device)
File "/usr/share/virt-manager/virtManager/domain.py", line 1041, in
attach_device
self._backend.attachDevice(devxml)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 508, in
attachDevice
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?

Thanks,
Andrew Ruch

Cole Robinson

2015-06-09 15:08:40 UTC

Permalink

Post by Andrew Ruch
Hello,
I recently upgraded from Fedora 20 to Fedora 22. I'm running
libvirt-1.2.13.1-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
unsupported configuration: boot order 1 is already used by another device
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 define_disk
self.hotplug(**hotplug_kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1111, in hotplug
self.attach_device(device)
File "/usr/share/virt-manager/virtManager/domain.py", line 1041, in
attach_device
self._backend.attachDevice(devxml)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 508, in
attachDevice
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.

Thanks,
Cole

Andrew Ruch

2015-06-09 17:30:13 UTC

Permalink

Post by Cole Robinson

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.
Thanks,
Cole

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.