From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm problem: bonding network interface breaks dhcp Date: Wed, 04 Nov 2009 11:07:09 +0200 Message-ID: <4AF1443D.8020109@redhat.com> References: <4AF0502C.5010304@aixigo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Harald Dunkel Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35428 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753377AbZKDJHK (ORCPT ); Wed, 4 Nov 2009 04:07:10 -0500 In-Reply-To: <4AF0502C.5010304@aixigo.de> Sender: kvm-owner@vger.kernel.org List-ID: On 11/03/2009 05:45 PM, Harald Dunkel wrote: > Hi folks, > > I am trying to use a bonding network interface as a bridge > for a virtual machine (kvm). Host and guest are both running > 2.6.31.5. Problem: The guest does not receive the DHCPOFFER > reply sent by my dhcp server. There is no such problem if > the host uses just a single network interface instead of > bond0. > > Looking at tcpdump on the Linux guest there are several dhcp > discover packages like > > 15:17:44.005306 00:16:36:2f:f1:d2> ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68> 255.255.255.255.67: BOOTP/DHCP, Request from 00:16:36:2f:f1:d2, length 300, xid 0x4c31213d, secs 10, Flags [none] > Client-Ethernet-Address 00:16:36:2f:f1:d2 [|bootp] > > The dhcp server receives these packages, and sends out > a reply > > 15:17:45.927589 00:16:36:2f:f1:d2> ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68> 255.255.255.255.67: BOOTP/DHCP, Request from 00:16:36:2f:f1:d2, length 300, xid 0x4c31213d, secs 10, Flags [none] > Client-Ethernet-Address 00:16:36:2f:f1:d2 [|bootp] > 15:17:45.927658 00:15:17:94:16:65> 00:16:36:2f:f1:d2, ethertype IPv4 (0x0800), length 364: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 350) 172.19.96.123.67> 172.19.97.243.68: BOOTP/DHCP, Reply, length 322, xid 0x4c31213d, secs 10, Flags [none] > Your-IP 172.19.97.243 > Client-Ethernet-Address 00:16:36:2f:f1:d2 [|bootp] > > This reply never shows up on the guest. > > > Can you tcpdump on bond0, br0, vnet0, and the guest's interface to see where the packet is lost? -- error compiling committee.c: too many arguments to function