** No longer affects: qemu
** Changed in: nova
Importance: Undecided => Medium
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1929710
Title:
virDomainGetBlockJobInfo fails during swap_volume as
I've added the QEMU project directly to this bug to see if anyone can
help us understand what the underlying block job failure is within QEMU
and why it then appears to remove the entire device from the instance
causing libvirt and Nova to fallover.
** Description changed:
Description
===
Thanks Christian,
I'll confirm that we see error from [2] with that PPA shortly.
In the meantime I've removed the device detach retry logic from
OpenStack Nova and now always see two DEVICE_DELETED events raised by
QEMU after a single device_del request from libvirt:
http://paste.openstack.org/s
Here's an example from QMP_requests_and_replies_from_libvirtd.log.gz
attached earlier to the bug by Kashyap. We can see two device_del
commands prior to only seeing a single event emitted by QEMU:
http://paste.openstack.org/show/798607/
# zgrep 0x7f768806eaf0 QMP_requests_and_replies_from_libvirt
While testing >=v5.0.0 on Fedora 32 I've stumbled across the following
change in QEMU:
https://github.com/qemu/qemu/commit/cce8944cc9efab47d4bf29cfffb3470371c3541b
The change suggests that previously parallel requests to detach a PCIe
device (such as virtio-blk) from QEMU would result in the orig
> @Christian Yes we can test this in OpenStack CI with PPAs if you
> could provide Bionic based builds.
I'm not sure what I was thinking here but we *can* use Focal based
builds of QEMU in CI now.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscri
@Christian Yes we can test this in OpenStack CI with PPAs if you could
provide Bionic based builds.
Better yet I could even try to setup a git bisect locally if you have
steps to build from a source tree somewhere?
@James Did you try using OpenStack CI sized hosts (8 vCPUs, 8GB of RAM)
and the QE
Public bug reported:
We are in the process of moving OpenStack CI across to use 20.04 Focal
as the underlying OS and encountering the following issue in any test
attempting to detach disk devices from running QEMU instances.
We can see a single DEVICE_DELETED event raised to libvirtd for the
/mac
