I've been having an odd problem where by creating a VM with a single
network interface in libvirt will require a restart before it can actually
get DHCP. It seems to just be a delay until the functionality is
available, since if you add a 2nd device it will eventually get a response
after failing for the first.
I've tried to listen to dhcp on the same subnet, and it's actually not
broadcasting a response until after the first interface fails. Has anyone
had any experience with this? It definitely seems like a libvirt issue,
but I was hoping there might be some work around by editing the libvirt
module, since I'm hesitant to work on a live KVM machine.
> I've tried to listen to dhcp on the same subnet, and it's actually not
> broadcasting a response until after the first interface fails. Has anyone
> had any experience with this? It definitely seems like a libvirt issue,
> but I was hoping there might be some work around by editing the libvirt
> module, since I'm hesitant to work on a live KVM machine.
First interface … meaning you have multiple ones? Try with only single
interface.
Are you using ISC DHCP daemon under Foreman management?
Have you turned off dnsmasq which is managed by libvirt?
I never experienced such an issue except one special case - I
mis-configured a VM with two interfaces in one subnet which was causing
issues with iptables (packet drops randomly).
This problem was because the interface was set with spanning tree protocol
enabled. It was timing out in time for a second interface to be
provisioned, but the first was timing out. I disabled in the network
bridge config file.
···
On Tuesday, April 5, 2016 at 12:37:25 PM UTC-7, Lukas Zapletal wrote:
>
> > I've tried to listen to dhcp on the same subnet, and it's actually not
> > broadcasting a response until after the first interface fails. Has
> anyone
> > had any experience with this? It definitely seems like a libvirt issue,
> > but I was hoping there might be some work around by editing the libvirt
> > module, since I'm hesitant to work on a live KVM machine.
>
> First interface ... meaning you have multiple ones? Try with only single
> interface.
>
> Are you using ISC DHCP daemon under Foreman management?
>
> Have you turned off dnsmasq which is managed by libvirt?
>
> I never experienced such an issue except one special case - I
> mis-configured a VM with two interfaces in one subnet which was causing
> issues with iptables (packet drops randomly).
>
> --
> Later,
> Lukas #lzap Zapletal
>
> This problem was because the interface was set with spanning tree protocol
> enabled. It was timing out in time for a second interface to be
> provisioned, but the first was timing out. I disabled in the network
> bridge config file.
Out of the curiousity, was this libvirt? It has stp flag turned on by
default and I don't see any problems here. Or did you mean other router
in the way, or the client itself?
