| Summary: | Firewall prevents networking in VMs | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kai Engert (:kaie) (inactive account) <kengert> |
| Component: | firewalld | Assignee: | Thomas Woerner <twoerner> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | jpopelka, kengert, twoerner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-10 17:15:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
What kind of VMs have you been using? Created and set up by libvirt? Yes, all of them had been created using virt-manager. Linux VMs, RHEL/Fedora. Are there errors in the logs related to libvirt or firewalld? Is the libvirt configuration modified? Please attach the output of the iptables-save command. Looks I didn't have the time to follow up with the requested details :( |
Installed a fresh F19. Attempted to make use of VMs that I had used on a different system. Actual behaviour: VMs couldn't start networking, they were stuck in "connecting" I didn't think of the defaul firewall as a potential cause. Once I did, the only obvious remedy was: disable firewall Questions: (a) Could firewalld allow communication with local VMs by default? (b) If (a) => no, then: Could there be an easily discoverable fix to allow the user to allow such communication, without having to disable the firewall?