If I have dhcpd running on my machine, and I wish to run virt-manager on the same machine.... How do I do that - its telling me an error for starting the network and the error is that DHCPD is already running - port in use.
Thanks,
Jerry
On 08/27/2015 01:43 PM, Jerry Geis wrote:
If I have dhcpd running on my machine, and I wish to run virt-manager on the same machine.... How do I do that - its telling me an error for starting the network and the error is that DHCPD is already running - port in use.
I'm mostly sure that if you want to run dhcpd, you just need to turn off the "default" network and use bridged networking instead.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/htm... (Hasn't really changed)
Under virt-manager, connect to the local host, then right-click on the local host and open "Details." Switch to the Virtual Networks tab, and uncheck the Autostart: On Boot option.
Guests will get dhcp from the bridged network, and will be on the same broadcast domain as the KVM host.
Hi,
On Fri, Aug 28, 2015 at 2:13 AM, Jerry Geis geisj@pagestation.com wrote:
If I have dhcpd running on my machine, and I wish to run virt-manager on the same machine.... How do I do that - its telling me an error for starting the network and the error is that DHCPD is already running - port in use.
Above problem is due to dnsmasq services which is used by virt-manager.
For virt-manager's networking details can be found at below link, http://wiki.libvirt.org/page/VirtualNetworking
Please refer below link to configure dnsmasq it. https://wiki.archlinux.org/index.php/Dnsmasq
--Regards Ashishkumar S. Yadav
Jerry Geis wrote:
If I have dhcpd running on my machine, and I wish to run virt-manager on the same machine.... How do I do that - its telling me an error for starting the network and the error is that DHCPD is already running - port in use.
It seems there's a problem with dnsmasq, which is used by virt-manager:
https://bugs.centos.org/view.php?id=7884 https://bugzilla.redhat.com/show_bug.cgi?id=1154953
The workaround mentioned in the bug reports is to downgrade dnsmasq to the version from CentOS 6.5.
Ron