[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[ChristianEhrhardt]

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 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Corey Bryant]

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 not supported in this QEMU binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Launchpad Bug Tracker]

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: #1697610).

 -- James Page   Tue, 25 Jul 2017 16:39:30 +0100

** Changed in: nova (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Ryan Beisner]

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 OpenStack Ocata (LP: #1706297).
   * d/p/aarch64-libvirt-compat.patch: Compatibility shim to resolve
 issues on aarch64 architecture (LP: #1697610).


** Changed in: cloud-archive/ocata
   Status: Fix Committed => Fix Released

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Brian Murray]

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 be specify the specific package versions that you tested as
these are different for the two repositories.  Thanks!

I spoke with Andrew about this and understand that comment #36 means the
version of the package in zesty-proposed so will fix the tag.

** Tags removed: verification-zesty-done
** Tags added: verification-done-zesty

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Andrew McLeod]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Andrew McLeod]

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: logfile not supported in this QEMU binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Ryan Beisner]

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:
  aarch64: logfile not supported in this QEMU binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[ChristianEhrhardt]

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.launchpad.net/bugs/1697610

Title:
  aarch64: logfile not supported in this QEMU binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Launchpad Bug Tracker]

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: #1708305)
  * Remaining changes:
- Disable sheepdog (universe dependency)
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Disable selinux
- Set qemu-group to kvm (for compat with older ubuntu)
- Regularly clear AppArmor profiles for vms that no longer exist
- Additional apport package-hook
- Modifications to adapt for our delayed switch away from libvirt-bin (can
  be dropped >18.04).
  + d/p/ubuntu/libvirtd-service-add-bin-alias.patch: systemd: define alias
to old service name so that old references work
  + d/p/ubuntu/libvirtd-init-add-bin-alias.patch: sysv init: define alias
to old service name so that old references work
  + d/control: transitional package with the old name and maintainer
scripts to handle the transition
- Backwards compatible handling of group rename (can be dropped >18.04).
- config details and autostart of default bridged network. Creating that is
  now the default in general, yet our solution provides the following on
  top as of today:
  + nat only on some ports 
  + autostart the default network by default
  + do not autostart if 192.168.122.0 is already taken (e.g. in containers)
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
  the group based access to libvirt functions as it was used in Ubuntu
  for quite long.
  + d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- d/p/ubuntu/enable-kvm-spice.patch: compat with older Ubuntu qemu/kvm
  which provided a separate kvm-spice.
- d/p/ubuntu/storage-disable-gluster-test: gluster not enabled, skip test
- d/p/ubuntu/ubuntu-libxl-qemu-path.patch: this change was split. The
  section that adapts the path of the emulator to the Debian/Ubuntu
  packaging is kept.
- d/p/ubuntu/ubuntu-libxl-Fix-up-VRAM-to-minimum-requirements.patch: auto
  set VRAM to minimum requirements
- d/p/ubuntu/xen-default-uri.patch: set default URI on xen hosts
- Add libxl log directory
- libvirt-uri.sh: Automatically switch default libvirt URI for users on
  Xen dom0 via user profile (was missing on changelogs before)
- d/p/ubuntu/apibuild-skip-libvirt-common.h: drop libvirt-common.h from
  included_files to avoid build failures due to duplicate definitions.
- Update README.Debian with Ubuntu changes
- Convert libvirt0, libnss_libvirt and libvirt-dev to multi-arch.
- Enable some additional features on ppc64el and s390x (for arch parity)
  + systemtap, zfs, numa and numad on s390x.
  + systemtap on ppc64el.
- fix conffile upgrade handling to avoid obsolete files
  and inactive duplicates (LP 1694159)
- d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
  vmlinuz available and accessible (Debian bug 848314)
- d/test/smoke-lxc workaround for debbug 848317/867379
- d/t/control, d/t/smoke-lxc: fix up lxc smoke test (Debian bug 848317)
- Extended handling of apparmor profiles - clear lost profiles via cron
- Add dnsmasq configuration to work with system wide dnsmasq (drop >18.04,
  no more UCA onto Xenial then which has global dnsmasq by default).
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- conffile handling of files dropped in 3.5 (can be dropped >18.04)
  + /etc/init.d/virtlockd was sysv init only
  + /etc/apparmor.d/local/usr.sbin.libvirtd and
/etc/apparmor.d/local/usr.lib.libvirt.virt-aa-helper are now generated
by dh_apparmor as needed
- Reworked apparmor Delta, especially the more complex delta is dropped
  now, also our former delta is now split into logical pieces, has
  improved comments and is part of a continuous upstreaming effort.
  Listing related remaining changes:
  + d/p/0001-apparmor-Allow-pygrub-to-run-on-Debian-Ubuntu.patch: apparmor:
Allow pygrub to run on Debian/Ubuntu
  + d/p/0002-apparmor-libvirt-qemu-Allow-macvtap-access.patch: apparmor,
libvirt-qemu: Allow macvtap access
  + d/p/0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
  + d/p/0004-apparmor-Explicit-deny-for-setpcap.patch: apparmor: Explicit
deny for setpcap
  + d/p/0005-apparmor-libvirt-qemu-Allow-use-of-sgabios.patch: apparmor,
libvirt-qemu: Allow use of sgabios
  + d/p/0006-apparmor-libvirt-qemu-Silence-lttng-related-deny-mes.patch:

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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-0ubuntu1~cloud0
  Version table:
 *** 2:15.0.6-0ubuntu1~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu 
xenial-proposed/ocata/main arm64 Packages
100 /var/lib/dpkg/status
 2:15.0.5-0ubuntu1~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu 
xenial-updates/ocata/main arm64 Packages
 2:13.1.4-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 
Packages
 2:13.0.0-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages


** Tags removed: verification-ocata-needed
** Tags added: verification-ocata-done

** Changed in: cloud-archive/pike
   Status: Triaged => Fix Committed

** Changed in: cloud-archive/pike
   Status: Fix Committed => Fix Released

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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-0ubuntu1~cloud0
  Version table:
 *** 2:15.0.6-0ubuntu1~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu 
xenial-proposed/ocata/main arm64 Packages
100 /var/lib/dpkg/status
 2:15.0.5-0ubuntu1~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu 
xenial-updates/ocata/main arm64 Packages
 2:13.1.4-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 
Packages
 2:13.0.0-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages


** Tags removed: verification-ocata-needed
** Tags added: verification-ocata-done

** Changed in: cloud-archive/pike
   Status: Triaged => Fix Committed

** Changed in: cloud-archive/pike
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[ChristianEhrhardt]

** 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[ChristianEhrhardt]

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 other things that would need that as well. But for now 
I need to move up qemu before going back to libvirt.

Do I understand correctly that with the nova fix that uses the old
console generation works for now (but lacks the early messages) and
once/if a fixed libvirt is in artful we can consider dropping the change
from nova again?.

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Steve Langasek]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nova (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Launchpad Bug Tracker]

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).

 -- James Page   Thu, 27 Jul 2017 13:29:38 +0100

** Changed in: nova (Ubuntu Artful)
   Status: In Progress => Fix Released

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

@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 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[Raghuram Kota]

@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/bugs/1697610

Title:
  aarch64: logfile not supported in this QEMU binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

** 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 Case]
+ Deploy OpenStack
+ Boot instance
+ Instance fails to boot with "logfile not supported in the QEMU binary" error 
message
+ 
+ [Regression Potential]
+ Low; the proposed patch reverts to using the pre-ocata code path, skipping
+ use of virtlogd for arm based architectures.
+ 
+ [Original Bug Report]
  This is a spin-off to bug 1673467 as it is a different issue:
  
  Got this today via Mail, linking here:
  
  none:
  
  https://pastebin.canonical.com/190574/
  
  host-model:
  
  https://pastebin.canonical.com/190578/
  
  host-passthrough
  
  https://pastebin.canonical.com/190579/
  
- 
- @admcleod - While my system is preparing to test this I think the logs you 
added are already kind of proving that the issue this bug was reported about is 
kind of solved.
+ @admcleod - While my system is preparing to test this I think the logs
+ you added are already kind of proving that the issue this bug was
+ reported about is kind of solved.
  
  In regard to your logs - the related error:
  none:
  -> Passes the initialization but then breaks on logfile
  
  host-model:
  -> Fails due to host-model being broken
  
  host-passthrough
  -> Passes the initialization but then breaks on logfile
  
  That said it seems to me the config overall is broken in regard to the 
logfile in some sort.
  When host-model is selected it fails earlier on init (this is the actual bug 
that was discussed in comments #1-#20), if called without host-model the init 
goes on.
  But then in general this seems to have issues around the logfile in some way.
  "libvirtError: unsupported configuration: logfile not supported in this QEMU 
binary"
  
  To reproduce I took the recommende "host-passthrough" case and made the 
following modifications to run without a real openstack around it:
  #0 packages that drag in all dependencies
  sudo apt install uvtool-libvirt nova-compute
  
  #1 create nvram vars from template to match XML
  sudo cp /usr/share/AAVMF/AAVMF_VARS.fd 
/var/lib/libvirt/qemu/nvram/instance-0010_VARS.fd
  sudo chown libvirt-qemu:kvm 
/var/lib/libvirt/qemu/nvram/instance-0010_VARS.fd
  
  #2 Replace openstack disks with something local that boots
  wget 
https://cloud-images.ubuntu.com/zesty/current/zesty-server-cloudimg-arm64.img
  
-   
-   
-   
-   
+   
+   
+   
+   
  
  
  #3 since we don't have the OS created net, replace with the default network
  
-   
-   
-   
+   
+   
+   
  
  
  #4 Create the logdir that nova specified in the "real" case
  sudo mkdir /var/lib/nova/instances/5f488b37-8906-4006-b736-70860856f290/
  sudo chown nova:nova 
/var/lib/nova/instances/5f488b37-8906-4006-b736-70860856f290/
  
- 
  With the above I was able to get your new bug around "logfile not supported 
in this QEMU binary".
  Ok, that certainly is a different bug - I can switch between host-model (old 
issue) and host-passthrough and be good.
  The logfile issue is a different one, so we track it in a new bug  = Here.

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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 opinion or not).

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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 fixes in development to both 2.5.x and
3.5.x in artful and zesty.

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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 (james-page)
   Status: In Progress

** Also affects: libvirt (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: nova (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: libvirt (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: libvirt (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: nova (Ubuntu Zesty)
   Importance: Undecided => Medium

** No longer affects: charm-nova-compute

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/pike
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/ocata
   Status: New => Triaged

** Changed in: cloud-archive/pike
   Status: New => Triaged

** Changed in: cloud-archive/pike
   Importance: Undecided => Medium

** Changed in: cloud-archive/ocata
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Artful)
   Status: In Progress => Triaged

** Changed in: libvirt (Ubuntu Artful)
 Assignee: James Page (james-page) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in 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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

[James Page]

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 (james-page)
   Status: In Progress

** Also affects: libvirt (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: nova (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: libvirt (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: libvirt (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: nova (Ubuntu Zesty)
   Importance: Undecided => Medium

** No longer affects: charm-nova-compute

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/pike
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/ocata
   Status: New => Triaged

** Changed in: cloud-archive/pike
   Status: New => Triaged

** Changed in: cloud-archive/pike
   Importance: Undecided => Medium

** Changed in: cloud-archive/ocata
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Artful)
   Status: In Progress => Triaged

** Changed in: libvirt (Ubuntu Artful)
 Assignee: James Page (james-page) => (unassigned)

-- 
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.launchpad.net/cloud-archive/+bug/1697610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs