Bug 546564
Summary: | dnsmasq is started even if no service configured | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marian Ganisin <mganisin> |
Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | berrange, clalance, crobinso, itamar, jforbes, veillard, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-11 10:32:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marian Ganisin
2009-12-11 08:54:00 UTC
This change is intentional. libvirt will always start dnsmasq because it is necessary to provide DNS and TFTPBoot services to guests using static IP config instead of DHCP. The libvirt virtual network capability is not intended to allow arbitrary end user customization. If you require that, then the recommendation is to configure it directly, and use type=bridge in libvirt guest domain config for NICs, instead of type=network. |