Need help: Looks like `ppc64le_defconfig` missing certain configs related default(virbr0) libvirt bridge network and fails to start the same
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 14
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
KVM libvirt default bridge network does not start with below error when kernel built with ppc64le_defconfig whereas same kernel built with fedora rawhide(30) kernel it just works fine.
error: Failed to start network default
error: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --insert LIBVIRT_INP --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT' failed: iptables: No chain/target/match by that name.
Looks like some configs to be enabled, and there are more related configs, needs help around the same.
Below is my upstream libvirt bug report for the same issue, which has details on what are all the missing configs from fedora rawhide.
Background: https://bugzilla.redhat.com/show_bug.cgi?id=1683174#c9
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ppc64le_defconfig kernel configuration and compare it with the Fedora Rawhide kernel configuration described in the linked Red Hat bug report. Identify the missing networking or netfilter options, verify the resulting kernel can start libvirt's default virbr0 network, and confirm the iptables chain/target error is gone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100