BOOT EFI issue - WorkStationPro 15.5 - Ubuntu 18.04.05 LTS - bionic

Hello team,

After successfully having installed Ubuntu via Foreman (standard BIOS) I wanted to move forward and tried with EFI. Unfortunately, I cannot get more than a switch between “/grub2/grub.cfg-00:50:56…” octet blksize 1024 and “/httpboot/grub2/grub.cfg-00:50:56” octet blksize 1024. At the end the VM failed due to Virtual CPU entering a shutdown state. TCPDUMP is clear, the same file upload switches between httpboot and ftpboot. I put this filter on tcpdump:
=> tcpdump -vv -i ens33 port tftp

I was expecting to get a full load … I work on WorkStationPro before installing this solution in production environment …

Foreman Version:
Puppet CA, Puppet, Logs, TFTP, DHCP, DNS, and HTTPBoot - 2.2.0-rc3

VM Parameter:
parameters:
foreman_subnets:

  • name: LAN
    network: 192.168.1.0
    mask: 255.255.255.0
    gateway: 192.168.1.254
    dns_primary: 192.168.1.100
    dns_secondary: 8.8.8.8
    from: 192.168.1.110
    to: 192.168.1.115
    boot_mode: DHCP
    ipam: DHCP
    vlanid:
    mtu: 1500
    nic_delay:
    network_type: IPv4
    description: ‘’
    foreman_interfaces:
  • ip: 192.168.1.111
    ip6: ‘’
    mac: 00:50:56:3c:2e:53
    name: pxe-client.sas.local
    attrs: {}
    virtual: false
    link: true
    identifier: eth0
    managed: true
    primary: true
    provision: true
    subnet:
    name: LAN
    network: 192.168.1.0
    mask: 255.255.255.0
    gateway: 192.168.1.254
    dns_primary: 192.168.1.100
    dns_secondary: 8.8.8.8
    from: 192.168.1.110
    to: 192.168.1.115
    boot_mode: DHCP
    ipam: DHCP
    vlanid:
    mtu: 1500
    nic_delay:
    network_type: IPv4
    description: ‘’
    subnet6:
    tag:
    attached_to:
    type: Interface
    location: Default Location
    location_title: Default Location
    organization: Default Organization
    organization_title: Default Organization
    domainname: sas.local
    owner_name: Admin User
    owner_email: root@sas.local
    ssh_authorized_keys:
    foreman_users:
    admin:
    firstname: Admin
    lastname: User
    mail: root@sas.local
    description:
    fullname: Admin User
    name: admin
    ssh_authorized_keys:
    root_pw: “$5$4q6V2GZMj2najnc1$yyNxk7wHqDWyeQb6C1q8wOqGrNL/MS6u2r8tv30Fdm6”
    foreman_config_groups:
    puppetmaster: maas.sas.local
    puppet_ca: maas.sas.local
    foreman_env: production
    classes: {}
    environment: production

My OS templates:
[PXEGrub2 global default]
[Preseed default]
[Preseed default user data]
[Preseed default finish]

In /var/lib/tftpboot:
drwxr-xr-x 2 foreman-proxy root 4096 Oct 3 21:32 boot/
-rw-r–r-- 1 foreman-proxy root 24672 Oct 3 18:50 chain.c32
drwxr-xr-x 2 foreman-proxy root 4096 Oct 3 20:33 grub/
drwxr-xr-x 2 foreman-proxy root 4096 Oct 4 15:18 grub2/
-rw-r–r-- 1 foreman-proxy root 115812 Oct 3 18:50 ldlinux.c32
-rw-r–r-- 1 foreman-proxy root 180568 Oct 3 18:50 libcom32.c32
-rw-r–r-- 1 foreman-proxy root 23052 Oct 3 18:50 libutil.c32
-rw-r–r-- 1 foreman-proxy root 10144 Oct 3 18:50 mboot.c32
-rw-r–r-- 1 foreman-proxy root 26536 Oct 3 18:50 memdisk
-rw-r–r-- 1 foreman-proxy root 26232 Oct 3 18:50 menu.c32
drwxr-xr-x 2 foreman-proxy root 4096 Oct 3 18:50 poap.cfg/
-rw-r–r-- 1 foreman-proxy root 41661 Oct 3 18:50 pxelinux.0
drwxr-xr-x 2 foreman-proxy root 4096 Oct 3 20:33 pxelinux.cfg/
drwxr-xr-x 2 foreman-proxy root 4096 Oct 3 18:50 ztp.cfg/

In grub2/ folder:
lrwxrwxrwx 1 root root 7 Oct 3 18:50 boot -> …/boot/
-rw-r–r-- 1 foreman-proxy root 5725 Oct 3 21:32 grub.cfg
-rw-r–r-- 1 foreman-proxy foreman-proxy 5724 Oct 3 21:32 grub.cfg-00:50:56:3c:2e:53
-rw-r–r-- 1 foreman-proxy foreman-proxy 5724 Oct 3 21:32 grub.cfg-01-00-50-56-3c-2e-53
-rw-r–r-- 1 foreman-proxy foreman-proxy 1166336 Oct 3 18:50 grubx64.efi
lrwxrwxrwx 1 root root 11 Oct 3 18:50 shim.efi -> grubx64.efi
lrwxrwxrwx 1 root root 11 Oct 3 18:50 shimx64.efi -> grubx64.efi

Grub location:
/var/lib/tftpboot/grub2/grub.cfg

Grub Content:
[…]
else
menuentry ‘Foreman Discovery Image EFI’ --id discovery {
linuxefi boot/fdi-image/vmlinuz0 ${common}
initrdefi boot/fdi-image/initrd0.img
}
fi

In boot folder (no fdi-image/vmlinuz0 nor initrd0.img):
-rw-r–r-- 1 foreman-proxy foreman-proxy 46865774 Apr 25 2018 ubuntu-mirror-siJBlGH2vpRc-initrd.gz
-rw-r–r-- 1 foreman-proxy foreman-proxy 8249080 Apr 25 2018 ubuntu-mirror-siJBlGH2vpRc-linux

My configuration:

foreman-installer \

–foreman-proxy-tftp=true
–foreman-proxy-tftp-servername=192.168.1.100

foreman-installer \

–foreman-proxy-dhcp=true
–foreman-proxy-dhcp-interface=ens33
–foreman-proxy-dhcp-gateway=192.168.1.254
–foreman-proxy-dhcp-pxeserver=192.168.1.100
–foreman-proxy-dhcp-range=“192.168.1.110 192.168.1.115”
–foreman-proxy-dhcp-nameservers=“192.168.1.100”

foreman-installer \

–foreman-proxy-dns=true
–foreman-proxy-dns-managed=true
–foreman-proxy-dns-interface=ens33
–foreman-proxy-dns-server=192.168.1.100
–foreman-proxy-dns-zone=sas.local
–foreman-proxy-dns-reverse=1.168.192.in-addr.arpa
–foreman-proxy-dns-forwarders=8.8.8.8

foreman-installer --foreman-proxy-httpboot true \

–foreman-proxy-http true

Thanks for your help …

Gueug78400

Hi,

I removed grub.cfg-01-00-50-56-3c-2e-53 and I have now a grub loading inside my PXE-Client.
!!! I now have an issue with Foreman Discovery Image EFI which cannot find:
=> error: File not found
=> error: you need to load the kernel first

If anyone had any idea …

Thanks!!!

Gueug78400

Hi all,

I found my mistake; I forgot to install:
foreman-installer
–enable-foreman-proxy-plugin-discovery
–foreman-proxy-plugin-discovery-install-images=true
–foreman-proxy-plugin-discovery-source-url=http://downloads.theforeman.org/discovery/releases/latest/

I have the following now but still got an issue
/var/lib/tftpboot/grub2/boot/fdi-image# ll
total 249624
drwxr-xr-x 2 foreman-proxy foreman-proxy 4096 Oct 21 2019 ./
drwxr-xr-x 3 foreman-proxy foreman-proxy 4096 Oct 4 19:38 …/
-rw-r–r-- 1 foreman-proxy foreman-proxy 248859421 Oct 21 2019 initrd0.img
-rw-r–r-- 1 foreman-proxy foreman-proxy 250 Oct 21 2019 README
-rw-r–r-- 1 foreman-proxy foreman-proxy 153 Oct 21 2019 SHA256SUM
-rw-r–r-- 1 foreman-proxy foreman-proxy 6734016 Oct 21 2019 vmlinuz0

=> error: timeout reading 'boot/fdi-image/initrd0.img’

If you had any idea …

Thanks,

Gueug78400

Hi all,

I think the incident is linked to tftp:
tftp
tftp> connect 192.168.1.100
tftp> verbose
Verbose mode on.
tftp> get boot/fdi-image/initrd0.img
getting from 192.168.1.100:boot/fdi-image/initrd0.img to initrd0.img [netascii]

Gueug78400

Hi all,

Could anyone explain to me why do I have a timeout with this file while PXE booting?
=> initrd0.img

I tried with a Linux client and I can download it:
tftp> get boot/fdi-image/initrd0.img
getting from 192.168.1.100:boot/fdi-image/initrd0.img to initrd0.img [netascii]
Received 250786022 bytes in 180.4 seconds [11121331 bits/sec]

I even change some options in TFTPD configuration file to test if this works:
cat /etc/default/tftpd-hpa

TFTP_USERNAME=“tftp”
TFTP_DIRECTORY="/var/lib/tftpboot"
TFTP_ADDRESS=":69"
TFTP_OPTIONS="–secure"
RUN_DAEMON=“yes”
OPTIONS="–blocksize 1024"
OPTIONS="-l -s /var/lib/tftpboot"

Thanks!!!

Gueug78400

Hello, well it looks like you are having some progress, so I am skipping to the last question then:

PXE uses TFTP protocol which is UDP-based (stateless). Therefore it will not work through NAT or firewalls, unless special L3/L2 handling is done. Test this from the same network you are trying to discover nodes in.

Alternatively, you can have a poor connection. When a single UDP packat is lost, TFTP will fail. This is particularly problem for big files like discovery initramdisk (300 MB).

You can workaround this by using iPXE EFI (ipxe.efi) or HTTP UEFI Boot which is a new feature introduced in the latest stable Foreman version.

https://docs.theforeman.org/master/Provisioning_Guide/index-foreman.html#creating-hosts-with-uefi-http-boot-provisioning_provisioning

Hi @lzap,

Thanks for your help, I read a lot of your answers on this community site; it is a great help!

I tried with either WorkStationPro and a Bare Metal (R440) inside a same subnet. I did a tftp from a client in order to discard any doubt and the result is the same; the below test is from my PXE client:
The grub menu pops up with Foreman Discovery Image EFI:


On Foreman server:
tcpdump -i enp94s0f0np0 port tftp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp94s0f0np0, link-type EN10MB (Ethernet), capture size 262144 bytes
21:35:55.177079 IP 10.3.8.181.1289 > maas.sas.local.tftp: 47 RRQ “grub2/grubx64.efi” octet tsize 0 blksize 1468
21:35:55.185840 IP 10.3.8.181.1290 > maas.sas.local.tftp: 39 RRQ “grub2/grubx64.efi” octet blksize 1468
21:35:55.269813 IP 10.3.8.181.25300 > maas.sas.local.tftp: 58 RRQ “grub2/x86_64-efi/command.lst” octet blksize 1024 tsize 0
21:35:55.270440 IP 10.3.8.181.25301 > maas.sas.local.tftp: 53 RRQ “grub2/x86_64-efi/fs.lst” octet blksize 1024 tsize 0
21:35:55.271389 IP 10.3.8.181.25302 > maas.sas.local.tftp: 57 RRQ “grub2/x86_64-efi/crypto.lst” octet blksize 1024 tsize 0
21:35:55.272137 IP 10.3.8.181.25303 > maas.sas.local.tftp: 59 RRQ “grub2/x86_64-efi/terminal.lst” octet blksize 1024 tsize 0
21:35:55.272787 IP 10.3.8.181.25304 > maas.sas.local.tftp: 44 RRQ “grub2/grub.cfg” octet blksize 1024 tsize 0
21:35:55.281080 IP 10.3.8.181.25305 > maas.sas.local.tftp: 72 RRQ “/httpboot/grub2/grub.cfg-4c:d9:8f:ba:36:3b” octet blksize 1024 tsize 0
21:35:55.287055 IP 10.3.8.181.25306 > maas.sas.local.tftp: 63 RRQ “/grub2/grub.cfg-4c:d9:8f:ba:36:3b” octet blksize 1024 tsize 0
21:35:55.293199 IP 10.3.8.181.25307 > maas.sas.local.tftp: 62 RRQ “grub2/grub.cfg-4c:d9:8f:ba:36:3b” octet blksize 1024 tsize 0
21:35:55.299780 IP 10.3.8.181.25308 > maas.sas.local.tftp: 56 RRQ “grub.cfg-4c:d9:8f:ba:36:3b” octet blksize 1024 tsize 0
21:36:15.454647 IP 10.3.8.181.25309 > maas.sas.local.tftp: 53 RRQ “boot/fdi-image/vmlinuz0” octet blksize 1024 tsize 0
21:36:15.627705 IP 10.3.8.181.25310 > maas.sas.local.tftp: 56 RRQ “boot/fdi-image/initrd0.img” octet blksize 1024 tsize 0


Then I have a black screen for one minute and this message appears:
Error: timeout reading ‘boot/fdi-image/initrd0.img’


So I test with another system and this time in another subnet and it is successful; on the client …
tftp> get boot/fdi-image/vmlinuz0
getting from 10.3.8.194:boot/fdi-image/vmlinuz0 to vmlinuz0 [netascii]
Received 6782157 bytes in 82.9 seconds [654490 bits/sec]

On Foreman for this download:
21:42:33.622892 IP 10.102.25.69.34154 > maas.sas.local.tftp: 35 RRQ “boot/fdi-image/vmlinuz0” netascii


I don’t understand why I can download via a simple command tftp while my PXE client cannot retrieve these files:
=> vmlinuz0
=> initrd0.img

foreman2

Foreman

Thanks!!

@Gueug78400

Hi @lzap,

I put tcpdump on verbose:

From PXE client:
22:06:59.782830 IP (tos 0x0, ttl 255, id 15812, offset 0, flags [none], proto UDP (17), length 84)
10.3.8.181.25310 > maas.sas.local.tftp: [udp sum ok] 56 RRQ “boot/fdi-image/initrd0.img” octet blksize 1024 tsize 0

From a workstation:
22:13:07.749798 IP (tos 0x0, ttl 61, id 32768, offset 0, flags [DF], proto UDP (17), length 66)
10.102.25.69.50976 > maas.sas.local.tftp: [udp sum ok] 38 RRQ “boot/fdi-image/initrd0.img” netascii

Thanks,

@Gueug78400

Try to replace the grub binary on your TFTP server with this one from RHEL:

http://people.redhat.com/~lzapleta/grub/grub2-efi-x64-2.02-0.87.el7.x86_64/grubx64.efi

Share your findings.

Hi @lzap,

I have to admit that I have a boot now since I have switched the legacy grubx64.efi for the one you provided. Since these files are binaries it is impossible to know the difference between them.

Now asides from the screens above and a looping reboot which does not end, I still cannot finalize my installation. I was due to deploy Ubuntu and this grubx64.efi seems to be adapted for Redhat or CentOs?

Regards,

@Gueug78400

PS: HTTP 404 … I don’t understand why do we have a HTTP response from Apache ?

You hav a network misconfiguration, Foreman is not running on that address. Fix that.

In regard to Ubuntu Grub - I can’t tell, sorry. I only test on RHEL/CentOS and grub is part of the OS not Foreman. It’s probably some old version or some patches are missing.

Hi @lzap,

This product is great; I really need to make it work. I chose it over maas.io and I need my team to be convinced that I did the right choice. So I’m gonna review every step and redo my lab from scratch. You said it is a network issue, perhaps did I not install or use discovery plugin the right way. I’ve been working a full month on Foreman and still haven’t seen more than the tip of the iceberg.

Regards,

@Gueug78400

hi @lzap,

Below is the process I followed.

Foreman installation:
hostnamectl set-hostname maas.sas.local
cat > /etc/hosts << EOF
192.168.1.100 maas.sas.local maas
EOF

sudo apt-get -y install ca-certificates
cd /tmp && sudo wget https://apt.puppet.com/puppet6-release-bionic.deb
sudo dpkg -i /tmp/puppet6-release-bionic.deb

sudo echo “deb http://deb.theforeman.org/ bionic 2.2” | sudo tee /etc/apt/sources.list.d/foreman.list
sudo echo “deb http://deb.theforeman.org/ plugins 2.2” | sudo tee -a /etc/apt/sources.list.d/foreman.list
sudo apt-get -y install ca-certificates

sudo wget -q https://deb.theforeman.org/pubkey.gpg -O- | sudo apt-key add -

sudo apt-get update && sudo apt-get -y install foreman-installer

sudo foreman-installer

Troubleshoot- DB fixed:
sudo dpkg-reconfigure locales
=> en_US.UTF-8 UTF-8
Generating locales (this might take a while)…
en_US.UTF-8… done
Generation complete.

sudo locale -a
C
C.UTF-8
POSIX
en_US.utf8
/Troubleshoot - DB fixed

sudo foreman-installer
Preparing installation Done
Executing: foreman-rake upgrade:run
foreman-rake upgrade:run finished successfully!
Success!

/Foreman installation

Foreman Configuration:
sudo foreman-installer
–foreman-proxy-tftp=true
–foreman-proxy-tftp-servername=192.168.1.100
Preparing installation Done

sudo foreman-installer
–foreman-proxy-dhcp=true
–foreman-proxy-dhcp-interface=ens33
–foreman-proxy-dhcp-gateway=192.168.1.254
–foreman-proxy-dhcp-pxeserver=192.168.1.100
–foreman-proxy-dhcp-range=“192.168.1.110 192.168.1.115”
–foreman-proxy-dhcp-nameservers=“192.168.1.100”
Preparing installation Done

sudo foreman-installer
–foreman-proxy-dns=true
–foreman-proxy-dns-managed=true
–foreman-proxy-dns-interface=ens33
–foreman-proxy-dns-server=192.168.1.100
–foreman-proxy-dns-zone=sas.local
–foreman-proxy-dns-reverse=1.168.192.in-addr.arpa
–foreman-proxy-dns-forwarders=8.8.8.8
Preparing installation Done

sudo foreman-installer
–enable-foreman-proxy-plugin-discovery
–foreman-proxy-plugin-discovery-install-images=true
–foreman-proxy-plugin-discovery-source-url=Index of /discovery/releases/latest

Foreman-Discovery:
Document: https://theforeman.org/static/legacy/manuals/Discovery%202.0.pdf
sudo foreman-installer --enable-foreman-plugin-discovery

sudo apt-get install ruby-smart-proxy-discovery

sudo foreman-installer
–foreman-plugin-discovery-install-images=true
ERROR: Unrecognised option ‘–foreman-plugin-discovery-install-images’

sudo wget http://downloads.theforeman.org/discovery/releases/latest/fdi-image-latest.tar -O /var/lib/tftpboot/boot && cd /var/lib/tftpboot/boot
sudo tar -xvf fdi-image-latest.tar

sudo chown foreman-proxy:foreman-proxy -R /var/lib/tftpboot/

Go to https://maas.sas.local/settings
=> Activate:
==> Default PXE global template entry form blank to ‘discovery’
Source: Chapter 6. Provisioning Bare Metal Hosts Red Hat Satellite 6.6 | Red Hat Customer Portal

Troubleshoot in template:
default=<%= global_setting(“default_pxe_item_global”, “local”) %>

sudo foreman-installer
–enable-foreman-proxy-plugin-discovery
–foreman-proxy-plugin-discovery-install-images=true
Foreman is running at https://maas.sas.local

sudo fuser 8443/tcp
8443/tcp: 1045

sudo ps -aux | grep 1045
foreman+ 1045 - Ssl 11:22 0:01 ruby /usr/share/foreman-proxy/bin/smart-proxy --no-daemonize
=> Discovery Proxy is now available in subnet.
/Foreman-Discovery
/Foreman Configuration

Deployment test:
Boot fails with:
error: timeout reading ‘boot/fdi-image/initrd0.img’

grubx64.efi creation:
Option 1:
Source: Feature #12635: Options to deploy Grub and PXELinux EFI loaders in TFTP root - Installer - Foreman
=> Download:
sudo cd /tmp/
sudo wget http://security.ubuntu.com/ubuntu/pool/main/g/grub2/grub-efi-amd64-bin_2.02-2ubuntu8.17_amd64.deb
sudo dpkg -i grub-efi-amd64-bin_2.02-2ubuntu8.17_amd64.deb
dpkg: error processing package grub-efi-amd64-bin (–install):
dependency problems - leaving unconfigured
sudo apt-get install -y grub-efi-amd64-bin
sudo cd /var/lib/tftpboot/grub2/
sudo mv grubx64.efi grubx64.efi.bak

grub-mkimage — Make a bootable GRUB image:
-O --format - x86_64-efi, …
-d --directory (source) - Use images and modules from DIR.
-o --output=FILE
-p --prefix - Set prefix directory. The default value is /boot/grub.
Source: grub2-mkimage: Make a bootable GRUB image. - Linux Manuals (1)

sudo grub-mkimage -O x86_64-efi -d /usr/lib/grub/x86_64-efi -o /var/lib/tftpboot/grub2/grubx64.efi -p “” find /usr/lib/grub/x86_64-efi/*.mod -printf "%f " | sed -e 's/\.mod//g'
due to backtick, “`” the find and sed commands are executed before the main command grub-mkimage
<= find /usr/lib/grub/x86_64-efi/.mod -printf "%f " | sed -e ‘s/.mod//g’ replaces all ".mod" by “*” ; example:
acpi.mod => acpi; adler32.mod => adler32 …
==> Error while booting: “The firmware encountered an unepected exception …”

Option 2:
sudo wget http://downloads.theforeman.org/foreman-bootloaders/foreman-bootloaders-fedora-201707171807.tar.bz2
I extracted grubx64.efi and copied it to grub2 directory.
/grubx64.efi creation

I tried a new installation and could ping PXE-Client (Discovery status: Success) at this step:

I don’t understand why the installation doesn’t initiate ; the only choice is to reboot and I got the same screen. It should load the kernel (vmlinuz0). This file is in the right place, in boot:

/var/lib/tftpboot/grub2/boot/fdi-image# ll
total 249624
drwxr-xr-x 2 foreman-proxy foreman-proxy 4096 Oct 21 2019 ./
drwxr-xr-x 3 foreman-proxy foreman-proxy 4096 Oct 10 15:22 …/
-rw-r–r-- 1 foreman-proxy foreman-proxy 248859421 Oct 21 2019 initrd0.img
-rw-r–r-- 1 foreman-proxy foreman-proxy 250 Oct 21 2019 README
-rw-r–r-- 1 foreman-proxy foreman-proxy 153 Oct 21 2019 SHA256SUM
-rw-r–r-- 1 foreman-proxy foreman-proxy 6734016 Oct 21 2019 vmlinuz0

Below are my templates for the OS:

I put Default PXE Global on “discovery”:

Screenshot from 2020-10-10 22-15-53

My subnet:

I did a tftp test:
root@gregory-XPS-13-9380:/tmp# tftp
tftp> verbose
Verbose mode on.
tftp> connect 192.168.1.100
tftp> get boot/fdi-image/vmlinuz0
getting from 192.168.1.100:boot/fdi-image/vmlinuz0 to vmlinuz0 [netascii]
Received 6782157 bytes in 4.9 seconds [11072909 bits/sec]

Did I miss anything??

Best regards,

@Gueug78400

@lzap,

PS: Build is set to “false” but doesn’t seem a 404 to me … Perhaps I’m wrong. In fact no 404 in the logs … Token is ok.

Hi @lzap,

I tried with Discovery this time (the VM was visible there with its MAC address) but I encountered two issues:

  1. PXE-Client boots automatically; a good point. But I have to remove this file otherwise the client fails:
    => grub.cfg-00:50:56:3c:2e:53

  2. Grub points on “Chainload Grub2 EFI from ESP” default menu and I have the following screen:

Do I need to create a boot in /var/lib/tftpboot/EFI/ubuntu and add grubx64.efi, and the rest?

Regards,

@Gueug78400

@lzap,

I removed IPv6 from the newly created host and got this screen. It seems that grub.cfg-00:50:56:3c:2e:53 doesn’t trouble me anymore; I left it.

Grub2.cfg:

Each time I have a different behavior; not easy to scope where is the root cause.

Regards,

@Gueug78400

PS: What is strange, I deleted the host in Foreman and have issues with Dsicovery plugin. My host still boots with Fetching Netboot Image without the standard PXE process. My host is not discovered in Foreman GUI. Is there any method to restart discovery service?

systemctl | grep foreman
foreman-proxy.service - loaded active running Foreman Proxy
foreman.service - loaded active running Foreman
foreman.socket - loaded active running Foreman HTTP Server Accept Sockets

I restarted these three services but the behavior is the same:
systemctl restart foreman-proxy.service
systemctl restart foreman.service
systemctl restart foreman.socket

Regards,

@Gueug78400

@lzap,

I restarted Foreman server too; I changed my VM MAC address. I recreated a host from scratch and I still have Fetching Netboot Image … I use the legacy and default PXEGrub2 template now.

I have no explanation; I don’t understand what happens now. Even the VM was hard restarted.

I had to remove the VM and recreate another one not to get this behavior as if some data was in the VM’s UEFI. Discovery doesn’t find any VM now.

@Gueug78400

hi @lzap,

Even after having recreated the VM I have my screen … “Fetching Netboot Image”. EFI is really different from BIOS; it was really easy with the latter. Legacy BIOS is going to be replaced forever that the reason I insist on it …

https://www.bleepingcomputer.com/news/hardware/intel-plans-to-end-legacy-bios-support-by-2020/

Regards,

@Gueug78400