I'm trying to kickstart a KVM guest. Historically, I could just start the guest connected to my bridged network interface, and my PXE server would hand out a DHCP address and then the tftp server would hand over the initrd.img and vmlinuz files. After upgrading from F35 to F36, I am not seeing any traffic from the guest at the PXE server. Has something changed between F35 and F36? This used to work without any hassle.
I choose to create a new guest. I choose "Manual Install." I choose Fedora 35 as the OS. I set the memory and vCPUs. I choose my disk size. I choose to connect to the bridged network (device name is bridge0, which matches the bridge name on my workstation). I choose "Customize configuration before install" and then Finish. At the customization screen, I go to "Boot options" and check the box next to the NIC. I choose Apply. I choose "Begin installation." The screen comes up, and I see the guest trying to PXE boot, but I never see any DHCP or tftp requests on the PXE server. I know the PXE server works, because I can kickstart guests on a virtualization hypervisor off the PXE server no problem.
To set up my workstation, I connected to Cockpit and drilled down to Networking. I chose to create a new bridged device and associated it with my physical NIC.
I've done this in previous versions of Fedora and not had any problems with it.
What am I doing wrong?
Thanks! Thomas
On 5/22/22 22:54, Thomas Cameron wrote:
I'm trying to kickstart a KVM guest. Historically, I could just start the guest connected to my bridged network interface, and my PXE server would hand out a DHCP address and then the tftp server would hand over the initrd.img and vmlinuz files. After upgrading from F35 to F36, I am not seeing any traffic from the guest at the PXE server. Has something changed between F35 and F36? This used to work without any hassle.
I choose to create a new guest. I choose "Manual Install." I choose Fedora 35 as the OS. I set the memory and vCPUs. I choose my disk size. I choose to connect to the bridged network (device name is bridge0, which matches the bridge name on my workstation). I choose "Customize configuration before install" and then Finish. At the customization screen, I go to "Boot options" and check the box next to the NIC. I choose Apply. I choose "Begin installation." The screen comes up, and I see the guest trying to PXE boot, but I never see any DHCP or tftp requests on the PXE server. I know the PXE server works, because I can kickstart guests on a virtualization hypervisor off the PXE server no problem.
To set up my workstation, I connected to Cockpit and drilled down to Networking. I chose to create a new bridged device and associated it with my physical NIC.
I've done this in previous versions of Fedora and not had any problems with it.
What am I doing wrong?
Thanks! Thomas
Just in case anyone else runs into this. I wound up going into Cockpit and deleting the bridge interface. I rebooted and then added a new bridge. Now I can kickstart my KVM guests.
No idea why that worked. <shrug>
Thomas
On Mon, 23 May 2022 15:54:28 -0500 Thomas Cameron wrote:
No idea why that worked. <shrug>
I had bridges stop working because they disabled the code that would copy the MAC address from the physical interface attached to the bridge. Had to add a specific MAC address to the bridge definition (I forget how long ago that was, probably one or two releases ago). Then my DHCP server would assign it the proper IP again.
Tom Horsley wrote:
On Mon, 23 May 2022 15:54:28 -0500 Thomas Cameron wrote:
No idea why that worked. <shrug>
I had bridges stop working because they disabled the code that would copy the MAC address from the physical interface attached to the bridge. Had to add a specific MAC address to the bridge definition (I forget how long ago that was, probably one or two releases ago). Then my DHCP server would assign it the proper IP again.
A related discussion was brought up on the devel list a few weeks ago:
Subject: upstream systemd discussion about MACAddressPolicy for bonds and bridges https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
It points to an upstream discussion:
https://lists.freedesktop.org/archives/systemd-devel/2022-May/047893.html
I don't know if that will be useful or of interest to anyone. :)
-
Thomas Cameron -
Todd Zullinger -
Tom Horsley