Meanwhile, I have been testing this on xenial queens, and am receiving what appears to be a more documented error.
[ 720.314053] virtio_blk virtio4: virtio: device uses modern interface but does not have VIRTIO_F_VERSION_1
[ 720.325082] virtio_blk: probe of virtio4 failed with error -22
Meanwhile, I have been testing this on xenial queens, and am receiving what appears to be a more documented error.
[ 720.314053] virtio_blk virtio4: virtio: device uses modern interface but does not have VIRTIO_F_VERSION_1
[ 720.325082] virtio_blk: probe of virtio4 failed with error -22
https:/ /pastebin. canonical. com/209188/ - this happens every time the volume is added. "Removing" the volume produces an acceptable set of messages, e.g. https:/ /pastebin. canonical. com/209298/
e.g.
https:/ /lists. gnu.org/ archive/ html/qemu- devel/2016- 08/msg03385. html
The implication here is to test toggling disable-modern and disable-legacy although I am not sure how to achieve this via openstack to test.
qemu, libvirt and kernel versions:
ubuntu@ node-loewy: ~$ qemu-system-aarch64 --version dfsg-0ubuntu5~ cloud0)
QEMU emulator version 2.10.1(Debian 1:2.10+
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
ubuntu@ node-loewy: ~$ libvirtd --version
libvirtd (libvirt) 4.0.0
ubuntu@ node-loewy: ~$ uname -a
Linux node-loewy 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:10:26 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
qemu-system-aarch64 command: https:/ /pastebin. canonical. com/209299/
domain xml with disk added: https:/ /pastebin. canonical. com/209300/
domain xml diff (with and without disk): https:/ /pastebin. canonical. com/209301/