Looks to be providing the full kernel command line now.
http://paste.ubuntu.com/7249787/
Still cannot get it to boot completely, but I think its do to maybe it
was built without iscsi support, as this is required for the MAAS
booting kernel. Am I correct?
I checked the iscsi target, it is
It was actually the initramfs, that didn't have the matching modules.
Once I updated the initramfs, its all working as expected.
--
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/1306677
Verified that linux-image-3.13.0-27 fixed this bug.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Booting the PPC64EL kernel the command line get truncated at 512
characters. This looks to be a hard limit defined in
arch/powerpc/boot/opts.h.
The MaaS project, needs to be able to provide a command line longer than
512 characters, as iscsi targets and cloud-init parameters
I cannot run this command as I cannot get to a fully booted environment.
I get dropped into the busybox initramfs.
--
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/1306677
Title:
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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/1306677
Title:
[PPC64EL] kernel command line gets truncated at 512
I used linux-
image-3.13.0-24-powerpc64-smp_3.13.0-24.46~lp1306677_powerpc.deb and
extracted the vmlinux image from the package. I replaced the boot-kernel
image on the MAAS server, and I am seeing the same result in the dmesg
output. The kernel command line output is still truncated, looking the
I was able to get the linux-
image-3.13.0-24-powerpc64-smp_3.13.0-24.46~lp1306677_powerpc.deb to load
on qemu-system-ppc64, but the initramfs didn't match so it failed at a
point.
I used the ppc64el version of the kernel, and received the same result.
The command line is still truncated.
Here is
** Changed in: linux (Ubuntu Trusty)
Status: Fix Committed = Confirmed
--
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/1306677
Title:
[PPC64EL] kernel command line gets truncated
Just hit this same issue with nova-compute on Xenial and creating a
Xenial instance in nova. I worked around the issue with:
juju set-config nova-compute cpu-mode=host-passthrough
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This kernel is PXE booting from MAAS. We might be able to modify the
kernel on disk that pxelinux.0 pulls to get you more information.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
$ time ./test not-a-real-hostname
Trying to resolve: not-a-real-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)
real0m10.007s
user0m0.001s
sys 0m0.001s
--
You received this bug notification because you are a
The issue is with the systemd resolver not with glibc.
With systemd-resolve IP in /etc/resolv.conf:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
$ systemd-resolve --status
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on
This seems to be an issue with the kernel and not an issue with MAAS
directly. Which Ubuntu release is set as the commissioning release on
the Global Settings page? If you can provide the full console log of the
boot that would be helpful as well.
** Also affects: linux (Ubuntu)
Importance:
** Changed in: maas
Status: New => Invalid
--
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/1743595
Title:
modprobing mlx5_core doesn't bring the interface up
Status in MAAS:
17 matches
Mail list logo
