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
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
