*** This bug is a duplicate of bug 1763644 ***
https://bugs.launchpad.net/bugs/1763644
I can confirm that the Xenial deployment works fine on both Moonshot and
ThunderX nodes now. (Although ThunderX should not be tested with 4.4
kernel anymore)
However, there is still a bug blocking the
I've changed all system with acpi-force with minimal kernel 16.04-hwe
and also removed acpi=force from global kernel cmdline. I believe it
shall make MAAS using correct combination.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
@dannf,
Is that getting set by the MAAS image or is that set inside of the MAAS
server itself to be added to the command line?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762655
The problem appears to be that acpi=force is being specified on the
command line. Not all arm64 servers support ACPI and, even for the ones
that do, there isn't sufficient support in the 4.4 kernel to support
them.
--
You received this bug notification because you are a member of Kernel
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
** Summary changed:
- Unable to deploy Xenial image on ARM64 nodes
+ Unable to deploy Xenial image on ARM64 nodes with MaaS 2.3.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762655
7 matches
Mail list logo