thr3ads.net - Xen users - [Xen-users] Error: Device 0 (vif) could not be connected. Could not find bridge.... [Jun 2007]

If this information is useful, please help other people find it:
Share via:

Levin Johnson

2007-Jun-11 01:53 UTC

[Xen-users] Error: Device 0 (vif) could not be connected. Could not find bridge....

[Please cc me for the reply since I am not on the list]

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 used "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

                                                            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:2090 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2301 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:1467230 (1.3 MiB)  TX bytes:377124 (368.2 KiB)

eth1      Link encap:Ethernet  HWaddr 00:13:CE:67:E4:31

          inet6 addr: fe80::213:ceff:fe67:e431/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:220 errors:0 dropped:34 overruns:0 frame:0

          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:263858 (257.6 KiB)  TX bytes:588 (588.0 b)

          Interrupt:18 Base address:0xc000 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:686 errors:0 dropped:0 overruns:0 frame:0

          TX packets:686 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:107785 (105.2 KiB)  TX bytes:107785 (105.2 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:2088 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1476466 (1.4 MiB)  TX bytes:388212 (379.1 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:2301 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2091 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:377124 (368.2 KiB)  TX bytes:1467300 (1.3 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:41 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:3276 (3.1 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 &amp; Recommendations.

Post your resume &amp; find a job match!


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

trilok nuwal

2007-Jun-13 07:17 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could not be connected. Could not find bridge....

U can do two thing, just comment out vif line
and specify the ramdisk it to config file.

Thanks,
Trilok

On 6/11/07, Levin Johnson <levin.johnson@lycos.com>
wrote:>
> [Please cc me for the reply since I am not on the list]
>
> 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 used "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
> 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:2090 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2301 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1467230 (1.3 MiB) TX bytes:377124 (368.2 KiB)
>
> eth1 Link encap:Ethernet HWaddr 00:13:CE:67:E4:31
> inet6 addr: fe80::213:ceff:fe67:e431/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:220 errors:0 dropped:34 overruns:0 frame:0
> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:263858 (257.6 KiB) TX bytes:588 (588.0 b)
> Interrupt:18 Base address:0xc000 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:686 errors:0 dropped:0 overruns:0 frame:0
> TX packets:686 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:107785 (105.2 KiB) TX bytes:107785 (105.2 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:2088 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2304 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1476466 (1.4 MiB) TX bytes:388212 (379.1 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:2301 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2091 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:377124 (368.2 KiB) TX bytes:1467300 (1.3 MiB)
>
> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:41 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:3276 (3.1 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!*<http://www.careerbuilder.com/?lr=cblycos&siteid=lycoshp7>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Xen users - Jun 2007 - Error: Device 0 (vif) could not be connected. Could not find bridge....

[Xen-users] Error: Device 0 (vif) could not be connected. Could not find bridge....

Re: [Xen-users] Error: Device 0 (vif) could not be connected. Could not find bridge....