Yeah if you are fine carrying the compat change that is the the best option.
James can overrule me if he objects.
** Changed in: libvirt (Ubuntu Zesty)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
James/Christian, Can we drop the zesty libvirt task for this since it is
fixed in zesty nova with a compatibility patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697610
Title:
aarch64: logfile
This bug was fixed in the package nova - 2:15.0.6-0ubuntu1
---
nova (2:15.0.6-0ubuntu1) zesty; urgency=medium
* New stable point release for OpenStack Ocata (LP: #1706297).
* d/p/aarch64-libvirt-compat.patch: Compatibility shim to resolve
issues on aarch64 architecture (LP: #1
This bug was fixed in the package nova - 2:15.0.6-0ubuntu1~cloud0
---
nova (2:15.0.6-0ubuntu1~cloud0) xenial-ocata; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
nova (2:15.0.6-0ubuntu1) zesty; urgency=medium
.
* New stable point release for OpenSta
I find the terminology here confusing in that packages are accepted in
to an ocata-proposed PPA and to zesty-proposed. While I understand that
the OpenStack release is called ocata I think referring to the package
in zesty as "zesty-ocata" is open to misinterpretation. One way to avoid
this would b
** Tags removed: verification-needed-zesty
** Tags added: verification-zesty-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697610
Title:
aarch64: logfile not supported in this QEMU binary
To
I have completed zesty-ocata/proposed testing and its working (I am able
to launch and connect to an instance successfully)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697610
Title:
aarch64: logf
Next steps: exercise zesty-ocata with proposed. Once the confirmed for
libvirt, we can get it into Zesty and the Ocata cloud archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697610
Title:
a
Libvirt 3.6 is in Artful now - if one wants to retest this for
Artful/Pike if you can (want?) to drop the change to go back to old
style console generation please feel free.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This bug was fixed in the package libvirt - 3.6.0-1ubuntu1
---
libvirt (3.6.0-1ubuntu1) artful; urgency=medium
* Merged with Debian unstable (3.6)
This closes several bugs:
- aarch64: improved chardev handling (LP: #1697610)
- Forbid locking memory without memtune (LP: #
xenial/ocata/proposed
Confirmed able to boot instances using the patched packages - console
and serial XML snippets LGTM:
$ apt-cache policy nova-compute
nova-compute:
Installed: 2:15.0.6-0ubuntu1~cloud0
Candidate: 2:15.0.6-0ubunt
Hi Christian
With regards to the nova fix - yes the patch reverts the behaviour on
ARM to use the old-style, functional on ARM way of doing console logs;
we can drop it as/when libvirt on ARM64 dtrt again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Tags added: libvirt-3.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697610
Title:
aarch64: logfile not supported in this QEMU binary
To manage notifications about this bug go to:
https://bugs
Hi James,
thanks for your work on this.
I agree that the backport to 2.5 will likely be too complex.
For 3.5 I didn't see more dependencies in the code, but might find some when
trying to do so.
I'm currently considering to move to libvirt 3.6 instead if that is working
smoothly as I have a few
Hello ChristianEhrhardt, or anyone else affected,
Accepted nova into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nova/2:15.0.6-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
This bug was fixed in the package nova - 2:16.0.0~b2-0ubuntu2
---
nova (2:16.0.0~b2-0ubuntu2) artful; urgency=medium
* d/tests/*: Drop nova-cert from DEP-8 tests.
* d/p/aarch64-libvirt-compat.patch: Compatibility shim to resolve
issues on aarch64 architecture (LP: #1697610).
@rkota
Reference: https://git.launchpad.net/~ubuntu-server-
dev/ubuntu/+source/nova/tree/debian/patches/aarch64-libvirt-compat.patch
basically we revert to the pre-ocata behaviour from the driver; so you
get as much as you got with OpenStack Newton.
--
You received this bug notification because
@James : Thanks for the new patch (comm #24)! Does this allow kernel
boot messages to be also captured and address the limitation mentioned
in comm #21 ? Thx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: nova (Ubuntu Zesty)
Status: Triaged => In Progress
** Changed in: nova (Ubuntu Zesty)
Assignee: (unassigned) => James Page (james-page)
** Description changed:
+ [Impact]
+ arm64 based openstack clouds can't boot instances with OpenStack Ocata or
later.
+
+ [Test Cas
OK - I've worked a slightly nicer patch to switch back to the pre-ocata
method of device creation for console log capture; this skips the use of
virtlogd (which is what the ocata changes make use of for pty devices)
on arm64.
--
You received this bug notification because you are a member of Ubunt
Reviewing patchsets for libvirt; looks like 3.6.0 will have the required
fixes for logfile support on aarch64, and the patchset to pick is approx
3 patches to 3.5.0.
The patchset for 2.5.0 is much larger so is probably no feasible as an
SRU (Christian - would be good if you can confirm this opinio
3.5.0 cherry-picks:
git cherry-pick -x ca5c5b997b348e650a086965c5e975c7101ee40e
git cherry-pick -x 56540950e73d331fc04443409c578e4354337309
git cherry-pick -x 426dc5eb28bade109bf27bdd10d7305a040b4a3e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I've made what at best can be called a compatibility patch for nova for
use with libvirt 2.5.0 or 3.5.0; it switches the type of the console to
virtio, which allows machines to boot, but no kernel boot messages are
captured - the first output it the login prompt.
Ideally we would backport the fixe
Working fixes here:
https://launchpad.net/~james-page/+archive/ubuntu/ocata
** Also affects: libvirt (Ubuntu Artful)
Importance: Medium
Assignee: James Page (james-page)
Status: In Progress
** Also affects: nova (Ubuntu Artful)
Importance: Medium
Assignee: James Page (ja
24 matches
Mail list logo
