Bug 277671
Summary: | libvirt starts dnsmasq inappropriately, preventing DNS queries from working | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Russell Robinson <russellr> | ||||||||
Component: | libvirt | Assignee: | Daniel Veillard <veillard> | ||||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 7 | CC: | xen-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: | 2007-09-05 14:52:35 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: | |||||||||||
Attachments: |
|
Description
Russell Robinson
2007-09-05 01:56:45 UTC
Created attachment 186791 [details]
Shell script to workaround the problem
Hum, that's strange ... Can you provide the output of the 'virsh dumpxml' command for the domain as well as the 'net-dumpxml' dump for the network you may have defined. Daniel Created attachment 187181 [details]
Virtual Machine XML
Created attachment 187191 [details]
Network XML
I've attached the files. Note that these XML files are exactly what Fedora Virtual Machine Manager creates, except I adjusted the <clock > tag for localtime and manually added the cdrom. regards, Russell Removing the "--bind-interfaces" and "--listen-address" flags is completely bogus because it prevents multiple copies of dnsmasq running at the same time, which is a central requirement to be able to serve different IP address ranges to different virtual networks. Further to
> dnsmasq is never set to listen for DNS queries on anything other than
> the private interface for the virtual machines.
This is explicitly the correct & desired behaviour. dnsmasq is *only* supposed
to be offering DNS to virtual machines on the particular virtual network it is
associated with. It is absolutely *not* supposed to answer queries from other
physical hosts. Note that the IP addresses given out are from the private
address pool 192.168.122.0/24, and this same range is used on all machines - the
guests at NAT'd to the outside world.
Hi, That's a fair enough explanation and I accept that. However, how does one make a VM accessible on a LAN? The case I have would not be unusual: 1. Host machine is on a LAN. 2. Guest machines are things like Windows. The VM's are merely replacements for what would otherwise be physical machines. 3. These Windows VM's need to be known on the LAN so that other machines can talk to them. Locking them behind a NAT process isn't always the way one want's things done. |