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-users

[Xen-users] Problem with network bridge when starting domU

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Problem with network bridge when starting domU
From: "Levin Johnson" <levin.johnson@xxxxxxxxx>
Date: Mon, 11 Jun 2007 10:37:28 -0400 (EDT)
Delivery-date: Mon, 11 Jun 2007 07:35:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Lycos. Inc.
Priority: Normal
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

I am new to Xen and I ran into some problem when trying to
xm create a FC6 domU with Xen 3.1. My dom0 is a FC5 running
the 2.6.18-xen kernel. This might just be a stupid configuration
issue that I am not aware of so please bear with me.

Here is what my cfg file looks like:

kernel = "/boot/vmlinuz-2.6.18-xen"
memory = 256
name = "fedora.fc6"
disk = ['file:/home/ljohnson/stuff/xen/fc6/fedora.fc6.img,sda1,w',
'file:/home/ljohnson/stuff/xen/fc6/fedora.swap,sda2,w']
root = "/dev/sda1 ro"
vif = [ '' ]

I was able to start the domain without the virtual nic. However,
with the vif in the cfg file, I got the following error when
creating the domain:

Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified

I have already turned off iptables on my machine and dom0's network
seems to work fine. I have also tried "vif = [ '', "bridge=xenbr0' ] but
the same error still shows up. If I set the mac address myself by
"vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ]", xm create hangs
and attempt to switch to the domU's console with "xm consle fedora.fc6"
also hangs. Any suggestion on where to look ?

The output from brctl show:

bridge name     bridge id               STP enabled     interfaces
xenbr0             8000.feffffffffff     no                      vif0.0
                                                                           &nb! sp;    peth0

The output from ifconfig:

eth0   Link encap:Ethernet  HWaddr 00:12:3F:FC:47:AF
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::212:3fff:fefc:47af/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1492  Metric:1
          RX packets:2224 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2501 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1597004 (1.5 MiB)  TX bytes:444505 (434.0 KiB)

eth1   Link encap:Ethernet  HWaddr 00:13! :CE:67:E4:31
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:404 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2236 (2.1 KiB)  TX bytes:220 (220.0 b)
          Interrupt:18 Base address:0x6000 Memory:dfbff000-dfbfffff

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:450 errors:0 dropped:0 overruns:0 frame:0
          TX packets:450 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:58377 (57.0 KiB)  TX bytes:58377 (57.0 KiB)

peth0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
            inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
            UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
            RX packets:2222 errors:0 dropped:0 overruns:0 frame:0
            TX packets:2504 errors:0 dropped:0 overruns:0 carrier:0
  !           collisions:0 tx queuelen:1000
            RX bytes:1606400 (1.5 MiB)  TX bytes:456597 (445.8 KiB)
            Interrupt:16

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
             inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
             UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
             RX packets:2501 errors:0 dropped:0 overruns:0 frame:0
             TX packets:2225 errors:0 dropped:0 overruns:0 carrier:0
             collisions:0 txqueuelen:0
             RX! bytes:444505 (434.0 KiB)  TX bytes:1597074 (1.5 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
               UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
               RX packets:20 errors:0 dropped:0 overruns:0 frame:0
               TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
               collisions:0 txqueuelen:0
               RX bytes:2608 (2.5 KiB)  TX bytes:0 (0.0 b)

Regards,

Levin



Want to change your life? Find the perfect job with Lycos Jobs.
Career Advice. Job Resources & Recommendations.
Post your resume & find a job match!
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Problem with network bridge when starting domU, Levin Johnson <=