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

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_poweroff = 'destroy'
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