[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

This works fine for me now, see attached. bug 1765668 is a different
issue, unrelated to the kernel.

** Attachment added: "xenial-guest-in-bionic.log"
   
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5123982/+files/xenial-guest-in-bionic.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[Po-Hsu Lin]

I can reproduce this in Bionic ARM64, bug 1765668

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-119.143

---
linux (4.4.0-119.143) xenial; urgency=medium

  * linux: 4.4.0-119.143 -proposed tracker (LP: #1760327)

  * Dell XPS 13 9360 bluetooth scan can not detect any device (LP: #1759821)
- Revert "Bluetooth: btusb: fix QCA Rome suspend/resume"

linux (4.4.0-118.142) xenial; urgency=medium

  * linux: 4.4.0-118.142 -proposed tracker (LP: #1759607)

  * Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty) (LP: #1758869)
- x86/microcode/AMD: Do not load when running on a hypervisor

  * CVE-2018-8043
- net: phy: mdio-bcm-unimac: fix potential NULL dereference in
  unimac_mdio_probe()

linux (4.4.0-117.141) xenial; urgency=medium

  * linux: 4.4.0-117.141 -proposed tracker (LP: #1755208)

  * Xenial update to 4.4.114 stable release (LP: #1754592)
- x86/asm/32: Make sync_core() handle missing CPUID on all 32-bit kernels
- usbip: prevent vhci_hcd driver from leaking a socket pointer address
- usbip: Fix implicit fallthrough warning
- usbip: Fix potential format overflow in userspace tools
- x86/microcode/intel: Fix BDW late-loading revision check
- x86/retpoline: Fill RSB on context switch for affected CPUs
- sched/deadline: Use the revised wakeup rule for suspending constrained dl
  tasks
- can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once
- can: af_can: canfd_rcv(): replace WARN_ONCE by pr_warn_once
- PM / sleep: declare __tracedata symbols as char[] rather than char
- time: Avoid undefined behaviour in ktime_add_safe()
- timers: Plug locking race vs. timer migration
- Prevent timer value 0 for MWAITX
- drivers: base: cacheinfo: fix x86 with CONFIG_OF enabled
- drivers: base: cacheinfo: fix boot error message when acpi is enabled
- PCI: layerscape: Add "fsl,ls2085a-pcie" compatible ID
- PCI: layerscape: Fix MSG TLP drop setting
- mmc: sdhci-of-esdhc: add/remove some quirks according to vendor version
- fs/select: add vmalloc fallback for select(2)
- hwpoison, memcg: forcibly uncharge LRU pages
- cma: fix calculation of aligned offset
- mm, page_alloc: fix potential false positive in __zone_watermark_ok
- ipc: msg, make msgrcv work with LONG_MIN
- x86/ioapic: Fix incorrect pointers in ioapic_setup_resources()
- ACPI / processor: Avoid reserving IO regions too early
- ACPI / scan: Prefer devices without _HID/_CID for _ADR matching
- ACPICA: Namespace: fix operand cache leak
- netfilter: x_tables: speed up jump target validation
- netfilter: arp_tables: fix invoking 32bit "iptable -P INPUT ACCEPT" failed
  in 64bit kernel
- netfilter: nf_dup_ipv6: set again FLOWI_FLAG_KNOWN_NH at flowi6_flags
- netfilter: nf_ct_expect: remove the redundant slash when policy name is
  empty
- netfilter: nfnetlink_queue: reject verdict request from different portid
- netfilter: restart search if moved to other chain
- netfilter: nf_conntrack_sip: extend request line validation
- netfilter: use fwmark_reflect in nf_send_reset
- ext2: Don't clear SGID when inheriting ACLs
- reiserfs: fix race in prealloc discard
- reiserfs: don't preallocate blocks for extended attributes
- reiserfs: Don't clear SGID when inheriting ACLs
- fs/fcntl: f_setown, avoid undefined behaviour
- scsi: libiscsi: fix shifting of DID_REQUEUE host byte
- Input: trackpoint - force 3 buttons if 0 button is reported
- usb: usbip: Fix possible deadlocks reported by lockdep
- usbip: fix stub_rx: get_pipe() to validate endpoint number
- usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input
- usbip: prevent leaking socket pointer address in messages
- um: link vmlinux with -no-pie
- vsyscall: Fix permissions for emulate mode with KAISER/PTI
- eventpoll.h: add missing epoll event masks
- x86/microcode/intel: Extend BDW late-loading further with LLC size check
- hrtimer: Reset hrtimer cpu base proper on CPU hotplug
- dccp: don't restart ccid2_hc_tx_rto_expire() if sk in closed state
- ipv6: Fix getsockopt() for sockets with default IPV6_AUTOFLOWLABEL
- ipv6: fix udpv6 sendmsg crash caused by too small MTU
- ipv6: ip6_make_skb() needs to clear cork.base.dst
- lan78xx: Fix failure in USB Full Speed
- net: igmp: fix source address check for IGMPv3 reports
- tcp: __tcp_hdrlen() helper
- net: qdisc_pkt_len_init() should be more robust
- pppoe: take ->needed_headroom of lower device into account on xmit
- r8169: fix memory corruption on retrieval of hardware statistics.
- sctp: do not allow the v4 socket to bind a v4mapped v6 address
- sctp: return error if the asoc has been peeled off in sctp_wait_for_sndbuf
- vmxnet3: repair memory leak
- net: Allow neigh contructor functions ability to modify the primary_key
- ipv4: Make neigh lookup keys for loopback/point-to-point devices be
  INADDR_ANY
   

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

After updating to the proposed kernel, I was able to boot a xenial cloud
image with qemu-efi from both xenial (DTB mode) and bionic (ACPI mode).

** Attachment added: "dmesg-xenial-host.txt"
   
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084478/+files/dmesg-xenial-host.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

** Attachment added: "dmesg-bionic-host.txt"
   
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084479/+files/dmesg-bionic-host.txt

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[Stefan Bader]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

My backport for option #3 has been merged, so no need for a change in
the cloud images or edk2.

** Changed in: cloud-images
   Status: New => Invalid

** Changed in: edk2 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: edk2 (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/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[Francis Ginther]

** Tags added: id-5a674ab10c375ca04060ea9a

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

** Description changed:

  [Impact]
  After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based 
guests will fail to boot.
  
  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
  
  [Regression Risk]
  I've tested booting a xenial cloud image in bionic (ACPI mode), and 
regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a 
Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
  
  Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel
  only supported 2 GICv3 systems - the 1 socket and 2 socket variants of
  the Cavium ThunderX CRB - and I've regression tested on those systems.
  
  Patch 6 only adds new macro definitions.
  
  Patch 7 is restricted to devicetree code, except for a change to
  earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed
  on the cmdline (vs. earlycon=something), this function used to return 0
  - but now it will return -ENODEV on non-devicetree systems, which is a
  subtle API change. However, according to kernel-parameters.txt (and the
  code itself), 'earlycon' by itself is only valid on devicetree systems.
  Just to be sure, I booted an x86 system up w/ 'earlycon' with and
  without this series, and observed no difference.
  
  Patch 8 adds the SPCR table parser, but no caller to it yet. It also
  modifies the same earlycon code as Patch 7 - here it avoids earlycon
  init in the case that the devicetree-specific 'earlycon' was passed. As
  mentioned in my analysis Patch 7, this codepath is only supported for
  devicetree systems, and has been regression tested on x86.
  
  Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only
  be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to
  build this for other archs - but I checked the logs, and there's no
  spcr.o built on other archs. (Not that that should be a problem - they
  would just grow a bit of unused code).
  
  Patch 10 only touches arm64-specific code, adding the call to
- parse_spcr().
+ parse_spcr(), so risk is limited to arm64.
  
  Patch 11 adds a new match method to the ARM-specific pl011 console
- driver.
+ driver, so regression risk to other architectures is negligible.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

@Robert: Actually, X-Gene is supported on trusty, which is non-GICv3,
but your point is taken. I personally think option #3 would be the best
option, but wasn't sure of the feasibility. However, I've been working
on the necessary kernel backports in the background over the past week,
and I now have something working that looks pretty clean/minimal. I'm
doing some regression testing now, and plan to submit to the kernel team
later this week.

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: edk2 (Ubuntu Xenial)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[Robert C Jennings]

Dann,

Regarding the 2nd option you listed: "Switch the xenial cloud-images to
use the HWE kernel. There's precedent for this (we did it for trusty to
add support for GICv3 systems). Existing VMs using 4.4 will still break
after upgrading qemu-efi past xenial."

As you know, the prior change to a Trusty images was made after
determining that there were no supported systems on the market with
GICv2 hardware; the impact of that change was deemed minimal.  A change
in cloud images to move from the GA to HWE kernel for an arm xenial
image could be disruptive and we would need to weigh the risks and
impact of that.  I think you know that well already, I just wanted to
reinforce that position and encourage edk2 and kernel developers to
investigate remediation in those areas first.  Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

Here are the 3 options for dealing with this I've come up with:

1) Disable ACPI in edk2 builds. That'd be an easy fix - but switching
away from upstream defaults isn't very future-proof. It also seems like
a pretty big regression risk for existing artful/bionic users who may be
depending on ACPI.

2) Switch the xenial cloud-images to use the HWE kernel. There's
precedent for this (we did it for trusty to add support for GICv3
systems). Existing VMs using 4.4 will still break after upgrading qemu-
efi past xenial.

3) Backport the necessary ACPI support to xenial's 4.4? That would fix
it everywhere, but I'm not sure how feasible/SRUable that would be.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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

[Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

I bisected this down to the following edk2 commit:

commit 78c41ff519b187d8979cda7074f007a6323f9acd (refs/bisect/bad)
Author: Ard Biesheuvel 
Date:   Thu Mar 9 16:59:34 2017 +0100

ArmVirtPkg/FdtClientDxe: make DT table installation !ACPI dependent

Instead of having a build time switch to prevent the FDT configuration
table from being installed, make this behavior dependent on whether we
are passing ACPI tables to the OS. This is done by looking for the
ACPI 2.0 configuration table, and only installing the FDT one if the
ACPI one cannot be found.

Which makes sense - arm64/ACPI support wasn't baked yet upstream in
v4.4.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744754

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

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