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] [SOLVED] Error: Device 0 (vif) could not be connected. H

> On 17/02/2010 18:24, Pasi Kärkkäinen wrote:
> > On Wed, Feb 17, 2010 at 03:21:12PM +0100, Olivier B. wrote:
> >
> >> Pasi Kärkkäinen a écrit :
> >>
> >>> On Wed, Feb 17, 2010 at 01:49:46PM +0100, Olivier B. wrote:
> >>>
> >>>
> >>>> For example :
> >>>> name = 'athena'
> >>>> kernel = '/boot/vmlinuz-2.6.31.12-dae-xen'
> >>>> ramdisk = '/boot/initrd.img-2.6.31.12-dae-xen'
> >>>> memory = '1024'
> >>>> root = 'root=/dev/mapper/vg--athena-root ro rootflags=data="">> >>>> disk = [ 'drbd:athena-disk,sda,w' ]
> >>>> vif = [ 'mac=02:00:00:00:04:3f' ]
> >>>> extra = 'rootdelay=1 raid=noautodetect'
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>> What if you also specify the bridge on the vif line?
> >>>
> >>> -- Pasi
> >>>
> >>>
> >>>
> >> Same result with "vif = [ 'mac=02:00:00:00:04:3f,bridge=xenbr0' ]" :
> >>
> >>
> > Weird. what if you also specify script=foo and create /etc/xen/scripts/foo,
> > which only has "exit 0" in it, and is executable.
> >
> > Also worth trying without the drbd: disk.. the error is about vif,
> > but good to verify with normal file: or phy: disks aswell. You never know :)
> >
> > -- Pasi
> >
> >
> >> I obtain "Error: Device 0 (vif) could not be connected. Hotplug scripts
> >> not working." after 100 seconds.
> >>
> >> And udev monitor said :
> >> UEVENT[1266416315.932082] add /devices/vbd-11-2048 (xen-backend)
> >> UDEV [1266416315.938359] add /devices/vbd-11-2048 (xen-backend)
> >> UEVENT[1266416315.960950] add /devices/vif-11-0 (xen-backend)
> >> UDEV [1266416315.961748] add /devices/vif-11-0 (xen-backend)
> >> UEVENT[1266416315.969379] add /devices/vif-11-0/net/vif11.0 (net)
> >> UEVENT[1266416315.970659] online /devices/vif-11-0 (xen-backend)
> >> UDEV [1266416315.980741] add /devices/vif-11-0/net/vif11.0 (net)
> >> UDEV [1266416315.982675] online /devices/vif-11-0 (xen-backend)
> >> UEVENT[1266416316.094038] add /devices/console-11-0 (xen-backend)
> >> UDEV [1266416316.095965] add /devices/console-11-0 (xen-backend)
> >>
> >> UEVENT[1266416355.592132] add /kernel/uids/101 (uids)
> >> UDEV [1266416355.592846] add /kernel/uids/101 (uids)
> >> UEVENT[1266416356.623642] remove /kernel/uids/101 (uids)
> >> UDEV [1266416356.625038] remove /kernel/uids/101 (uids)
> >>
> >> UDEV [1266416397.419326] remove /devices/vif-10-0/net/vif10.0 (net)
> >> UDEV [1266416397.439092] remove /devices/vif-10-0 (xen-backend)
> >>
> >> UEVENT[1266416416.855557] remove /devices/console-11-0 (xen-backend)
> >> UDEV [1266416416.858075] remove /devices/console-11-0 (xen-backend)
> >> UEVENT[1266416416.894895] remove /devices/vbd-11-2048 (xen-backend)
> >> UDEV [1266416416.896732] remove /devices/vbd-11-2048 (xen-backend)
> >> UEVENT[1266416416.900803] offline /devices/vif-11-0 (xen-backend)
> >> UEVENT[1266416416.925352] remove /devices/vif-11-0/net/vif11.0 (net)
> >> UEVENT[1266416416.936165] remove /devices/vif-11-0 (xen-backend)
> >>
> >> Olivier
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-users
> >>
> >
> Hi,
>
> so... it's my fault : my .config was different... If I take the same
> .config file it works well, with DRBD too.
> Now I have to found witch kernel parameter is needed for Xen.
>
> I suspect one of this flags :
>
> in the working .config :
> < CONFIG_SYSFS_DEPRECATED=y
> < CONFIG_SYSFS_DEPRECATED_V2=y
> < CONFIG_KALLSYMS_ALL=y
> < # CONFIG_X86_PAT is not set
> < CONFIG_UNUSED_SYMBOLS=y
> < CONFIG_FRAME_POINTER=y
>
> in the not working .config :
> > # CONFIG_SYSFS_DEPRECATED_V2 is not set
> > CONFIG_X86_PAT=y
> > # CONFIG_UNUSED_SYMBOLS is not set
> > # CONFIG_FRAME_POINTER is not set
>
> Any idea ? Anyway I will do some tests to try to identify which one is
> required by Xen.
>

That would be great. By the way, I also suspect certain option in the networking section of the .config must be set to avoid the "Error: Device 0 (vif) could not be connected. Hotplug scripts not working." error.

If I may suggest, I'd would be much appreicated is you could place your .config option findings in a xensource wiki page or email your finding to someone that could....

That would be awesome!

Thanks.

-M



> Thanks,
> Olivier
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


Windows® phone-your Windows stuff, on the go. See more.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users