WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-u

To: Scott Meyers <scottmeyers@xxxxxxxx>
Subject: Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Tue, 30 Aug 2011 00:23:24 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 29 Aug 2011 14:24:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <SNT127-W38C09C508E0FCD2A83A6D5C9140@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <SNT127-W406E00A1722D989EC85D2BC9130@xxxxxxx> <20110826112557.GD32373@xxxxxxxxxxx> <20110826135434.GK32373@xxxxxxxxxxx> <SNT127-W38C09C508E0FCD2A83A6D5C9140@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Aug 29, 2011 at 03:52:59PM -0500, Scott Meyers wrote:
> 
> 
> Pasi,
> 
> Thank you for updating your tutorial.
> 
> Per your suggestion, I installed bridge-utils-1.2-9.fc13.i686 and the error 
> message is gone:
> 
> [root@pe1950]# brctl show
> bridge name bridge id  STP enabled interfaces
> virbr0  8000.000000000000 yes
> 
> 
> But, I still can not create a DomU. The bridge won't communicate with the 
> system. When I try to create DomU, "xm create -c vm101" The system can't find 
> CentOS mirror or the Kickstart file. Here is the result of the command 
> ifconfig:
> 
> 
> [root@pe1950]# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:15:C5:EF:77:DC  
>           inet addr:70.50.188.15  Bcast:70.50.188.255  Mask:255.255.255.0
>           inet6 addr: fe80::215:c5ff:feef:77dc/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:10220 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:852 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:731545 (714.3 KiB)  TX bytes:172998 (168.9 KiB)
>           Interrupt:16 Memory:f8000000-f8012800 
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:2 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:152 (152.0 b)  TX bytes:152 (152.0 b)
> 
> vif4.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:216 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:5 overruns:0 carrier:0
>           collisions:0 txqueuelen:32 
>           RX bytes:6264 (6.1 KiB)  TX bytes:70 (70.0 b)
> 
> virbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
>           inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1816 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:57784 (56.4 KiB)  TX bytes:11194 (10.9 KiB)
> 
> 
> Here is a copy of the DomU config file:
> 
>  
> 
> [root@pe1950]# cat /etc/xen/vm101
> # Standard variables
> kernel          = "/tmp/centos_5"
> ramdisk         = "/tmp/centos_5.img"
> extra           = "text ks=http://MYDOMIAN.tld/ks/ks.cfg";
> 
> name = "vm101"
> uuid = "813c0e59-8566-4386-95c1-0cc27af85a6d"
> maxmem = 512
> memory = 512
> vcpus = 1
> disk = [ "tap:aio:/vm/vm101/xvda.img,xvda,w" ]
> vif = [ "mac=00:16:3e:56:73:92,bridge=virbr0,script=vif-bridge" ]
> 
> 
> 
> [root@pe1950]# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 70.50.188.0   *                 255.255.255.0   U     0      0        0 eth0
> 192.168.122.0   *               255.255.255.0   U     0      0        0 virbr0
> link-local      *               255.255.0.0     U     1002   0        0 eth0
> default         MYDOMAIN.tld    0.0.0.0         UG    0      0        0 eth0
> 
> Any idea what to do to solve this problem? Thank you
> 
>  


virbr0 is created by libvirtd/dnsmasq, so it's not really part of Xen.

Anyway, some things to verify:

- do you have ip_forwarding (routing) enabled in dom0?
- How are your firewall rules in dom0?
- Is dnsmasq running?
- Do you see domU dhcp requests in system logs (from dnsmasq) ?
- After the domU is started run "brctl show" - is the domU vif connected to 
virbr0 bridge?
- Run "tcpdump -i virbr0 -nn" - do you see the traffic from the vm?
- Does the domU get an IP? 


Those should get you going.

-- Pasi


> 
>  
> 
>  
> 
>  
> 
>  
> 
> > From: pasik@xxxxxx
> > To: scottmeyers@xxxxxxxx
> > CC: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 
> > bridge-utils IGMP snooping
> > 
> > I also added that info to http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial now.
> > 
> > -- Pasi                                       

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