[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Bridging DomUs using Driver Domain

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Jason Sonnek <jsonnek@xxxxxxxxx>
  • Date: Wed, 19 Jan 2011 13:26:17 -0600
  • Delivery-date: Wed, 19 Jan 2011 11:28:29 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=FEg6aOD5jCggdpxLd0X7XSFSjRWGV3nNxyAsXVy1t73wpjwFsKUY03UKVV/fvAbd1F m11VMqYDRxFuKbY8WI+5Sys1Nf5SS/C7rTwjoLms7IOCpidTNZpv1cX9wxHf3erWBzot JvslVRUCQhYa3Sjsg2USndRKh9J5hYRp/naKI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm trying to bridge two HVM DomUs using a bridge hosted in a driver domain (rather than in Dom0) in Xen 4.0.1. I've succeeded in doing this using PV guests on Xen 4.0.1, and using HVM guests on Xen 3.3, but it doesn't work in Xen 4.0.1.

The vif specification in my HVM guest configuration file looks like so:

# virtual interface on driver-domain bridge
vif=[ 'mac=00:16:3e:69:2a:33,backend=driver-domain,bridge=br1,model=rtl8139']

When I start domain Y with front-end virtual interface ethX, I see the corresponding backend virtual interface vifY.X attached to br1 in the driver domain, so the vif-bridge/hotplug scripts in the driver domain appear to be doing the right thing:

driver-domain:~ # brctl show
bridge name    bridge id        STP enabled    interfaces
br1                 8000.feffffffffff             no        vif20.0

However, packets originating at (for instance) eth2 on Domain 26 never arrive on vif26.2. If I run 'xm network-list 26', I see:

Idx BE     MAC Addr.     handle state evt-ch tx-/rx-ring-ref BE-path
0   0  00:16:3e:58:5d:24    0     1      -1    -1   /-1      /local/domain/0/backend/vif/26/0 
1   18 00:16:3e:60:20:11    1     1      -1    -1   /-1      /local/domain/18/backend/vif/26/1 
2   18 00:16:3e:62:10:be    2     1      -1    -1   /-1      /local/domain/18/backend/vif/26/2 

Since the interface state is 1 (initializing) and the event channel and tx/rx-rings are all -1 (invalid), this strongly suggests that the virtual interface initialization is failing. However, there are no messages in the qemu-dm.log or the xend.log that offer any clues to me.

Any suggestions? I've been at this for a while, so I have voluminous debugging data if it would help anyone, but I don't want to post a bunch of useless logs.



Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.