Thanks a lot Sean, if it works as in Bionic/Queens then it is even released.
Is there a need for the super-deep dive what exactly fixed it to consider SRUs
or is Bionic/Queens fine for now?
** Changed in: libvirt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug
Some additional information: using libvirt 4.0
ii libvirt-clients 4.0.0-1ubuntu8
arm64Programs for the libvirt library
ii libvirt-daemon4.0.0-1ubuntu8
arm64Virtualization daemon
ii
Today I was able to test Queens+Bionic for the first time in about 2
weeks, without being roadblocked by bugs, Due to a resource constraint
in hardware i was only giving one host. I decided to deploy opentack-on-
lxd which uses the same bits as a multi-node deployment.
Marking bug as fix committed as this now works, with Bionic-Queens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM] : Unable to use Cinder volumes on ARM
To manage
Wanted to update this bug with my findings so far, I have found the
linaro commit that fixed this issue here:
https://www.redhat.com/archives/libvir-list/2016-October/msg00396.html
I was in the process of testing bionic, however was blocked due to a few
juju bugs last week,(See:
Yeah it seems this was discussed plenty of times but not accepted that
(actually in any) way.
I tried around a bit and discussed with more people, but didn't find a good way
to hard control it.
Note: on IRC it also came up that a hot-attach fails with the message in
comment #23.
But on a guest
I have tried to add this to the XML but it seems
that it is missing from the libvirt domain schema.
error: XML document failed to validate against schema: Unable to validate doc
against /usr/share/libvirt/schemas/domain.rng
Extra element devices in interleave
Element domain failed to validate
That is the new libvirt 4.0 which gives the better messages.
Interesting.
Could be an arm specific lack of virtio (which is generic).
IIRC there was something that arm only worked with modern (virtio 1) and might
force this.
But I could be wrong (too old info).
The XML as well as the qemu
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
Ok, if broken in pike+arm64 still that means it is broken in the latest
qemu/libvirt we currently have (until we bumped for Bionic/Queens).
That also implies that all fixes that were meant to be identified before can't
be the fix as they are in arm64+pike.
This will get more complex once we
I can confirm this is still an issue with pike + arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM] : Unable to use Cinder volumes on ARM
To manage notifications about this
For sanity sake I am currently attempting to reproduce this with pike on
arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM] : Unable to use Cinder volumes on ARM
To manage
Hi,
so far the data we have unfortunately makes it less clear.
All the reported failures are likely not what the referred fix is solving.
Because as outlined, Xenial (and thereby Mitaka) don't have the change
(https://libvirt.org/git/?p=libvirt.git;a=commit;h=a1344f70a) that got fixed by
the
It looks like so far we have the following data points. :
ARM64
-
1) Xenial-Mitaka : Fail (comm#3)
X86-64
-
a) Trusty - Mitaka : Fail (Comm #4)
b) Xenial-Mitaka : OK (Comm #7)
In addition, Linaro had confirmed that
https://bugs.linaro.org/show_bug.cgi?id=2462 (that trigerred the
Note: per comment #7
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1664737/comments/7
- I made this on x86_64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM] : Unable
@Ryan Beisner (1chb1n) : Oh, my apologies, I was only looking at the
libvirt version (as the fix seems to be there) and went by the
following statement in comm#13 : " But UCA-Newton has only Xenials
libvirt that is on libvirt 1.3.1 and should not be affected at all
either."
Are there components
@rkota - fyi Xenial-Newton uses the versions from Yakkety, so it affects
both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM] : Unable to use Cinder volumes on ARM
To manage
@paelzer : Many thanks for looking into this. Xenial-Mitaka test on
comm#7 was actually done by Dimitrii (dmitriis).Thanks go out to him.
Based on comm#13, your hypothesis seems to be that this should only
occur on Yakkety.
@dmitriis : Are you able to help with the tests #2-#5 on ServerStack or
Hi,
we have to be careful on the identified patch
https://libvirt.org/git/?p=libvirt.git;a=commit;h=0701abcb3
IMHO there surely has to go this along it to really work (that is the one
identified in linaro bug 2462):
https://libvirt.org/git/?p=libvirt.git;a=commit;h=fceeeda21
Also there is the
Please evaluate for backport to Xenial, Yakkety and Zesty libvirt to
resolve the issue with Mitaka, Newton and Ocata, respectively.
** Tags added: backport-potential
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: qemu (Ubuntu)
--
You
This bug seems to have been addressed in upstream libvirt, per comm#18
of https://bugs.linaro.org/show_bug.cgi?id=2462
Per Gem Gomez (Linaro) :
The upstream review, commit of the patch can be found on the libvirt upstream
mailing :
The upstream commit:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=0701abcb3ba78ba27cf1f47e01b3d9607ad37b72
Proposed is 1.3.1-1ubuntu10.8:
https://launchpad.net/ubuntu/xenial/+source/libvirt
A quick and dirty check for a part of a diff
Need to determine whether or not a fix mentioned here has been landed or
proposed:
https://bugs.linaro.org/show_bug.cgi?id=2462
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
** Tags added: arm64 uosci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM] : Unable to use Cinder volumes on ARM
To manage notifications about this bug go to:
>From Ryan Beisner (1chb1n) :
Xenial-Mitaka
I've confirmed that hot-plugging a cinder volume to a uefi arm64 nova
instance doesn't work out of the box.
After attaching the volume, it was necessary to reboot the instance in
order to detect and use the new volume.
$ openstack volume create
Dmitrii Shcherbakov (dmitriis) wrote on 2017-02-02:
@beisner
Had issues with deployment - for some reason a couple of undercloud VMs
got stuck (juju was waiting for a machine allocation while it already
booted) after running juju-deployer. Had to manually remove affected
units and 'juju
Ryan Beisner (1chb1n) wrote on 2017-02-02:
@dmitrii Can you please independently exercise the following?:
On ServerStack (x86_64):
- Boot a new nova instance.
- Create a cinder volume.
- Attach the cinder volume to the running nova instance (with openstack cli).
We are looking to confirm
Ryan Beisner (1chb1n) wrote on 2017-01-26:
This does not appear to specific to arm64. On an x86 internal dev cloud,
Trusty-Mitaka, I also have to reboot my nova instance after attaching
ceph-backed cinder volumes before they are usable.
Next steps: test again with vanilla cinder (not
From: Dann Frazier (dannf) :
Note that the reason I went about testing this was because I ran across this
one:
https://bugs.linaro.org/show_bug.cgi?id=2462
The symptoms don't seem to be the same - OpenStack in that case generated an
error on attach. In this case, there was no error, but the
Dmitrii Shcherbakov (dmitriis) wrote on 2017-02-02:
In general with a proper guest kernel support hot-plug of block devices
should work both with virtio and virtio-scsi on any arch:
http://www.linux-kvm.org/page/Hotadd_pci_devices#Add_a_disk
Verified that using a xenial host and a xenial guest
31 matches
Mail list logo
