[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Just a note that the udev rules change from comment 6 seems to be necessary to reliably get an image booted under QEMU to bring up a getty on the serial console. What seems to happen without it is that udevd spends all its time running copies of 'readlink', and it doesn't get around to telling

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Thanks for the followup. Closing the debian-installer part now. The work on the Debian side wrt. multiplexing the installer UI to mutiple consoles sounds interesting, but I don't think we should houd our breath for it -- I think this is going to be tricky given how different the capabilities of VT

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

--- Comment From gpicc...@br.ibm.com 2016-09-19 15:26 EDT--- Very nice pitti, thanks for the clarification. And thanks a lot for your effort in this bug. Seems there is a request/RFC to add GNU screen support to debian- installer, so it can show the menu in multiple terminals [1] [2].

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

That d-i behaviour agrees with how the kernel interprets those: https://www.kernel.org/doc/Documentation/serial-console.txt -- i. e. kernel messages appear on all "console="s, but the last one defines what /dev/console points to. -- You received this bug notification because you are a member of

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

gpiccoli, great finding! Indeed it seems debian-installer interprets console= arguments and prefers the *last* one: rootskel-1.115ubuntu1/src/sbin/reopen-console-linux: if [ -z "$console" ]; then # Locate the last enabled console present on the command line

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

This bug was fixed in the package systemd - 229-4ubuntu8 --- systemd (229-4ubuntu8) xenial-proposed; urgency=medium * Queue loading transient units after setting their properties. Fixes starting VMs with libvirt. (LP: #1529079) * Connect pid1's stdin/out/err fds to /dev/null

Re: [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Breno Leitão [2016-09-12 20:53 -]: > Per previous comment, I understand that this bug is still not fixed, > correct? Yes, as it isn't even understood yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Martin, Per previous comment, I understand that this bug is still not fixed, correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615021 Title: Unable to network boot Ubuntu 16.04 installer

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

I ran the test case for systemd on a 16.04.1 desktop live system with an USB ethernet device. I confirm that naming still works as intended, MAC naming can be disabled with the /dev/null symlink, and the readlink calls are gone. (Again, note that this was merely the side issue, not the main boot

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Note, there hasn't been any debian installer fix yet, as we don't even understand what's actually happening there. There has just been an SRU to systemd/udev to fix the "No such file or directory" error message in udev rules, but apparently that was not the actual problem. -- You received this

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Hello bugproxy, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

This bug was fixed in the package systemd - 231-5 --- systemd (231-5) unstable; urgency=medium [ Iain Lane ] * Let graphical-session-pre.target be manually started (LP: #1615341) [ Felipe Sateler ] * Add basic version of git-cherry-pick * Replace

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

This bug was fixed in the package busybox - 1:1.22.0-19ubuntu2 --- busybox (1:1.22.0-19ubuntu2) yakkety; urgency=medium * debian/patches/readlink-in-slash-bin.patch: put readlink in /bin/ like coreutils. Closes LP: #1615021. -- Steve Langasek

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

I don't actually know what BOOT_DEBUG does -- I've never seen it before, it does not appear anywhere in my yakkety system, and it's for sure not something the kernel, initramfs-tools, or systemd look at. My best guess is that this is a debian-installer specific debug flag. So from what I can

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

If this screen output is for a case when the installer *did* show up, I don't think it's going to tell us much about where things have hung in the case that it *didn't* show up. If there's a particular invocation of udev that lets you reproduce the problem, I suggest sticking with that, and

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Thanks for reporting this! Indeed this is a silly rule construction, *brown paperbag*. I fixed this for the next Debian/Yakkety upload in https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=b42e1f8af2 and backported it to Xenial in

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

** Description changed: == Comment: #7 - Guilherme Guaglianoni Piccoli - 2016-08-19 10:08:07 == The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to download the latest vmlinux and initrd.gz files available, and kexec them with no parameters

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

I've thought about this some more, and while the /bin/readlink /usr/bin/readlink in busybox is a bug, fixing this is definitely not going to fix the problem in the installer. In the installer, /etc/udev/rules.d/80-net-setup-link.rules will never exist since this is an admin override; so the

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615021 Title: Unable to network boot Ubuntu 16.04 installer normally on

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Examining the initrd shows that readlink is provided as /usr/bin/readlink -> /bin/busybox, not as /bin/readlink where systemd expects it (and where it's shipped on an installed system). This is a bug in debian-installer's construction of that image - though gee it would be nice if systemd didn't

[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

** Changed in: systemd (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/1615021 Title: Unable to network boot Ubuntu 16.04 installer normally on Briggs To