New preseed on Ubuntu 20.04

[fred]

Hello,
New Ubuntu, news problems!

They change the network install.
As new thread/doc said:
Netbooting the live server installer

And my new entry UEFI in menu.ipxe is:

Code:

:ubuntu2004
kernel iso/ubuntu/vmlinuz
initrd iso/ubuntu/initrd
imgargs vmlinuz initrd=initrd boot=casper ip=dhcp url=http://${66}/iso/ubuntu/focal-live-server-amd64.iso debian-installer/language=fr console-setup/layoutcode?=fr autoinstall ds=nocloud-net;s=http://${66}/iso/ubuntu/autoinstall/config.yml
boot

But autoinstall change too...
Automated Server Installs for 20.04

As I write in menu entry:

Code:

imgargs vmlinuz initrd=initrd boot=casper ip=dhcp url=http://${66}/iso/ubuntu/focal-live-server-amd64.iso debian-installer/language=fr console-setup/layoutcode?=fr autoinstall ds=nocloud-net;s=http://${66}/iso/ubuntu/autoinstall/config.yml

But not working, the installer boot to wizard.

Any ideas?
Thanks

[MultimediaMan]

It would be helpful to understand what the error is...

Screenshots are helpful.

Absent a Screenshot, can you reach the ISO by going to the URL?

Best,

M^3

[fred]

Hello,
I'm sorry I don't see error. Where I can find error log of this?

Simply, it's, how to integrate the news "preseed system" named autoinstall of the new Ubuntu 20.04 to iPXE?

Thanks!
Have a great day

[MultimediaMan]

OK, we could have two separate issues here: Is the issue iPXE or Ubuntu? If it iPXE, then this is the place for help. If it is Ubuntu, then this may not (but still may be) a place for help.

At the end of the day, iPXE is just a really flexible bootloader. You have to be careful about determining where the problems lie.

Saying the system doesn't work is unhelpful at best. Please describe the boot sequence and what you see from power on to PXE and beyond.

If you want to capture logs, there are several sections on how to do this: https://www.ipxe.org/buildcfg/console_syslog Syslog is not enabled by default due to security/ binary size issues. It is for debugging only.

I) Describe your DHCP TFTP environment and which iPXE bootloader you are using (undionly.kpxe, ipxe.efi, etc...) iPXE build numbers may be helpful.

II) Describe each of the following steps in the boot cycle:

A) BIOS splash screen (you should see this)
B) PXE Boot Screen (you should see this)
1. PXE DHCP Request
2. IP address info
C) iPXE Boot Screen (you should see this)
1. iPXE Kernel Entry
2. iPXE DHCP Request (you should see this)
3. Embedded/Downloaded Script Entry
4. Initrd/vmlinuz download
D) Ubuntu Kernel Entry (you should see this)
1. vmlinuz/ initrd Execution (you should see this)

Best,

M`3

[d4rk3]

This is what works for me:

Code:

set    imgargs    initrd=initrd.gz root=/dev/rd/0 ramdisk_size=14984 rw ip=dhcp auto=true keymap=us hostname=ubuntu vga=normal preseed/url=http://xxx/preseed.cfg

kernel http://xxx/linux ${imgargs}
initrd http://xxx/initrd.gz
boot

[fred]

Hello,
Thanks d4rk3 for your example, but it's not working.

Code:

set    imgargs    initrd=initrd.gz root=/dev/rd/0 ramdisk_size=14984 rw ip=dhcp auto=true keymap=us hostname=ubuntu vga=normal preseed/url=http://${66}/iso/ubuntu/autoinstall/config.yml
kernel iso/ubuntu/vmlinuz  ${imgargs}
initrd iso/ubuntu/initrd
boot

For MultimediaMan, I don't know what I can answer to you sorry...
rom-o-matic is not reachable, and on my VM I cannot compil a new .efi multiples errors... Sorry. I tried to answer this my template of snponly.efi

I can boot Ubuntu 20.04 installer without problem. Just my autoinstaller yaml is not use. Canonical change network boot method.

This is

Code:

#!ipxe

dhcp ||

echo IP pxe server: ${66}
sleep 2

set menu-url http://${66}/menu.ipxe

initrd ${menu-url} && goto success || goto failure

:success
echo Success!
sleep 2
goto command

:failure
echo Failure!
sleep 2

:command
chain ${menu-url} ||

#For Troubleshooting after Failure...
shell

So read this doc: Autonstall
And if someone know how to make it work with iPXE, it's will be very good.

I'll looking for for cloudinit and ipxe, maybe.

Thanks,

[MultimediaMan]

If you can get the installer to PXE boot using iPXE, the problem is definitely not iPXE. The problem lies in the syntax of your kernel parameters or within the autoinstall.yml file.

I was not able to duplicate your results, so it might be a good idea to post a redacted version of yout autoinstall.yml file.

[fred]

I know MultimediaMan that is not a iPXE problem.

I just ask for help to integrate the new Ubuntu Network install to iPXE. Not said that iPXE don't work.
Certainly I'm not clear in my explanations.

But I found something!

With this entry:

Code:

:ubuntu2004
kernel iso/ubuntu/vmlinuz
initrd iso/ubuntu/initrd
imgargs vmlinuz initrd=initrd boot=casper ip=dhcp url=http://${66}/iso/ubuntu/focal-live-server-amd64.iso debian-installer/language=fr console-setup/layoutcode?=fr autoinstall ds=nocloud-net;s=http://${66}/iso/ubuntu/autoinstall/
boot

Add this to imgargs:

Code:

autoinstall ds=nocloud-net;s=http://${66}/iso/ubuntu/autoinstall/

And create in $PWD/iso/ubuntu/autoinstall/ a file called: user-data with content of this documentation: AutoInstall references
And just touch another file called meta-data .

And It's autoinstall start!

But now, I have errors with content of user-data. My installation is hang on error.

[XaT]

Hi there,

Did someone try classic preseed for Desktop ?