From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: Re: domU's on 802.1q on unstable, where talking to dom0 now can't Date: Wed, 28 Sep 2005 09:39:53 -0400 Message-ID: <1127914793.4079.76.camel@pluto.linsolutions.com> References: <1127909888.4079.45.camel@pluto.linsolutions.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <1127909888.4079.45.camel@pluto.linsolutions.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, 2005-09-28 at 08:18 -0400, Ted Kaczmarek wrote: > FC4 dom0 > xen_changeset : Tue Sep 27 10:11:59 2005 +0100 a172340ae3f3 > > I was testing domU's on 802.1q ethernets and it was working fine. I > added the interfaces after all my domU's where already up, set up a dhcp > server on my dom0 for a few of the vms and connectivity between the > domU's and dom0 on the vlan was working. > > If I try to bring up everything from scratch with 802.1q interfaces the > domU's can't talk to the dom0. They can talk to each other though. > > > I tried lowering mtu size as far as 1460 to no avail. > > The dom0 does not have any traces of any of the domU's in its arp table. > > > Any insight would be appreciated. > > Regards, > Ted > > If the 802.1q interface is either brought on line after the domU's 802.1q or bounced it fixes the issue talking to dom0. Regards, Ted