[Xen-devel] Xen 4.0.1 Driver Domain Issue

[Jason Sonnek <jsonnek@xxxxxxxxx>]

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 the same configuration 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        vif12.0
                                                                   

However, packets originating at (for instance) eth0 on Domain 12 never arrive on vif12.0. If I run 'xm network-list 12', I see:

Idx BE     MAC Addr.     handle state evt-ch tx-/rx-ring-ref BE-path
0   10 00:16:3e:63:a5:20    0     1      -1    -1   /-1      /local/domain/10/backend/vif/12/0

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 (although I don't see any error messages to this effect in the log, which is attached).

Any suggestions?

Thanks!

Jason

xend.log
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel