I'm pretty sure we had the same issue as you. After posting to the dev list and getting no response my colleague fixed it by modifying /xen-3.0.2-2/tools/ioemu/vl.c and changing
pstrcpy(ifr.ifr_name, IFNAMSIZ, "tun%d");
line to
*sprintf(ifr.ifr_name, "tun%d.%%d", domid);
and running:*
*/etc/xen/scripts/network-bridge start bridge=xenbr0 netdev=eth0 vifnum=0
/etc/xen/scripts/network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1*
*as our wrapper script
Our brctl show now looks like this:
bridge name bridge id STP enabled interfaces
xenbr0 8000.b2b6111693ac no peth0
tun1.0
vif0.0
xenbr1 8000.d63bb36ceb1e no peth1
tun1.1
vif0.1
Hope this helps.
Nick
*
matt wrote:
I've got the same problem with xen 3.0.2 (compiled form source, but
I've had the same issue with binaries) running on Ubuntu 6.06.
I've got two network cards and have a wrapper script around
network-bridge to create two bridges.
When I run a paravirtualised domain which has the following vif section:
vif = ['bridge=xenbr0','bridge=xenbr1']
I get a domain with two vifs that attach to the correct physical
interfaces. Which is what I'd expect.
However...
When I create a HVM domain with this vif section:
vif = ['type=ioemu, bridge=xenbr0','type=ioemu, bridge=xenbr1']
I get two vifs but both attached to the same bridge (whichever bridge
appears first in the script, the above example would attach both to
xenbr0)
brclt show looks like this:
xenbr0 ===> 8000.someStuff ====> vif0.0 peth0 vif12.1
xenbr1 ===> 8000.otherStuff ====> vif0.1 peth1 tun0 tun1 vif12.0
so any thoughts?
many thanks
Matt
Original
Message==========================================================================
Hello,
We have setup 6 xen guests VT(rhel3) on dmo0 FC5 and for each guest
there are 2 network interfaces eth0/eth1.
Now if we start the xen guests all the tun interfaces for eth1 goes to
xenbr1 and not do the defined bridge tsmbr1 oder tsmbr2 ?
Where are the scripts for setup tun interface ?
Has anybody a solution for this problem ?
2 Guests have this vif config:
vif = [ 'type=ioemu,bridge=xenbr1,mac=02:00:00:00:01:01',
'type=ioemu,bridge=tsmbr1,mac=02:00:00:00:01:02' ]
And 2 guest have this vif config:
vif = [ 'type=ioemu,bridge=xenbr1,mac=02:00:00:00:01:09',
'type=ioemu,bridge=tsmbr2,mac=02:00:00:00:01:10' ]
bridge name bridge id STP enabled interfaces
tsmbr1 8000.921f6ab823a2 no tun1
vif1.1
vif2.1
tsmbr2 8000.feffffffffff no vif3.1
vif4.1
vif5.1
vif7.1
vif9.1
xenbr0 8000.82469d13d88a no peth0
tun14
tun15
vif0.0
vif8.0
xenbr1 8000.06939ed49977 no peth1
tun0
tun10
tun11
tun12
tun13
tun2
tun3
tun4
tun5
tun6
tun7
tun8
tun9
vif0.1
vif1.0
vif2.0
vif3.0
vif4.0
vif5.0
vif7.0
vif9.0
xenbr2 8000.feffffffffff no peth2
vif0.2
vif8.1
many thanks,
Thomas
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
This e-mail is the property of Quadriga Worldwide Ltd, intended for the
addressee only and confidential. Any dissemination, copying or distribution of
this message or any attachments is strictly prohibited.
If you have received this message in error, please notify us immediately by
replying to the message and deleting it from your computer.
Messages sent to and from Quadriga may be monitored.
Quadriga cannot guarantee any message delivery method is secure or error-free.
Information could be intercepted, corrupted, lost, destroyed, arrive late or
incomplete, or contain viruses.
We do not accept responsibility for any errors or omissions in this message
and/or attachment that arise as a result of transmission.
You should carry out your own virus checks before opening any attachment.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of Quadriga. _______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home