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

[Xen-devel] Using stubdoms, vif is attached to the wrong bridge


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: George Dunlap <dunlapg@xxxxxxxxx>
  • Date: Wed, 29 Jul 2009 18:11:19 +0100
  • Delivery-date: Wed, 29 Jul 2009 10:11:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=GYtQ8jPGWPls/snvUnII6+5meHmQeCQl8ALIhXHDVV4I4oMiJn8xlkjKfy5tSpXWnx R+dhJAIhzA1EgbpxaaQN8I/mIRBe+/Z2iOd+8ZmcK74H92RkIDqODAghSND03khf5M3E BE41IOHmcCwkiSvugbRoXDFIqErgi0Rjrllaw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I've got a host with two NICs, eth0 and eth1.  eh0 is connected to the
normal network, eth1 is connected via crossover cable to another box.
(Set up to isolate off-box network testing from other traffic.)  I've
got a bridge set up for each interface (xenbr0 and xenbr1
respectively), and an HVM guest with two vifs, one attached to each
bridge.

When use qemu-dm, everything works as expected.

When I change to stubdom-dm (only change in the config file) the
second guest VIF ends up attached to xenbr0 instead of xenbr1.

I'm using xen-unstable.hg changeset 20004:23f33c39d68c, qemu-dm.git
commit 8eebdeff589fb1ae41e37ad1e3b3feff40761c9b

 -George

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


 


Rackspace

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