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

Re: [Xen-users] Debian Etch: Error: Device 0 (vif) could not be connecte

To: "Dan Goscomb" <dgoscomb@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Debian Etch: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
From: "trilok nuwal" <tc.nuwal@xxxxxxxxx>
Date: Fri, 24 Aug 2007 19:54:21 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 24 Aug 2007 07:24:59 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=KPpcn7j+XuZ0AblXJlpmeER4dzgF4VqE8JHyovIR88jsFwsGvkzTj18Igj4mXbP2YhGiCuUgqoUWCARt9ir/eI3Vra5kFFeO+6lNM6hVEudtCGd5le939XnxCe/BK8OwHNM2C9O6OgD/brXBgy9N9zK97xwTCCx7Brqx+08KA+w=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=dFXCwRGQ3Ax54QqdKItKAksYsA2DawzbuUIJiYbb3gopitpEfXlM6yXrXy3wHluNnIsusSQD326J1iULh54fpOeOyeFc0jy7PfwmPCPchElahBWjLlYJtYx0S0U0fjoZ4JdX0CuobMuT+nNlg7J09BBEygYDF8KCSdVjlQ7Lu60=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1187965364.18416.51.camel@dang-desktop>
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>
References: <1187964622.18416.46.camel@dang-desktop> <f58fc26d0708240715o46b060deg1578fa46490b4556@xxxxxxxxxxxxxx> <f58fc26d0708240715x1460bf46lfbdcf3e9b3f3c67d@xxxxxxxxxxxxxx> <1187965364.18416.51.camel@dang-desktop>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

you shoud put in yr config file then try.

vif  = [ 'bridge=xenbr2' ]



On 8/24/07, Dan Goscomb <dgoscomb@xxxxxxxxxxxxx> wrote:
Hi

The bridges work for some DomU... as I said... the bridge is
automatically created:

vps2:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr2          8000.feffffffffff       no              vif0.2
                                                        peth2
                                                        vif15.0
                                                        vif2.0
                                                        vif4.0
                                                        vif11.0
                                                        vif6.0
                                                         vif13.0
                                                        vif14.0


Config file of one of the DomU:

kernel  = '/boot/vmlinuz-2.6.18-4-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.18-4-xen-amd64 '
memory  = '128'
root    = '/dev/sda1 ro'
disk    = [ 'phy:vg0/domu-disk,sda1,w', 'phy:vg0/domu-swap,sda2,w' ]
name    = 'domu'
vif  = [ 'ip=<IP_ADDRESS>' ]
>on_reboot   = 'restart'
on_crash    = 'restart'


Cheers

Dan


On Fri, 2007-08-24 at 19:45 +0530, trilok nuwal wrote:
> better post the config file as well as #ifconfig output in dom0.
>
> On 8/24/07, trilok nuwal <tc.nuwal@xxxxxxxxx > wrote:
>         Did you created bridges in dom0 whtever u r exporting to domU.
>
>
>
>
>         On 8/24/07, Dan Goscomb <dgoscomb@xxxxxxxxxxxxx> wrote:
>                 Hi All
>
>                 We have an issue whereby after X number (where X can
>                 change) DomU are
>                 booted, subsequent ones fail with the error message in
>                 the title.
>
>                 Is this a known issue? I have been unable to work out
>                 why that error
>                 message is appearing...
>
>                 Any hints would be appreciated!
>
>                 Cheers
>
>                 Dan
>
>
>                 _______________________________________________
>                 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