Olivier B.
2010-Jan-29 14:31 UTC
[Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi, I tried to upgrade my dom0 kernel from 2.6.31.6-dae-dom0-00751-g60e0545 to 2.6.31.6-dae-dom0-00757-ge65323d ; and domU doesn''t start anymore. I obtain this error message : > root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg > Using config file "/etc/xen/hel.cfg". > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > real 1m41.491s > user 0m0.116s > sys 0m0.056s And the error is triggered after 100 seconds... I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 vanilla pv_ops kernel. In xen-hotplug.log I have only this line : Nothing to flush. And in xend.log I found that : [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for devices vif. [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0. [2010-01-29 15:26:12 6213] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy: domid=5 Is there a bug in last pv_ops dom0 kernel, or have I something to fix in my setup ? Olivier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2010-Feb-01 07:30 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
On Fri, Jan 29, 2010 at 03:31:10PM +0100, Olivier B. wrote:> Hi, > > I tried to upgrade my dom0 kernel from 2.6.31.6-dae-dom0-00751-g60e0545 > to 2.6.31.6-dae-dom0-00757-ge65323d ; and domU doesn''t start anymore. > > I obtain this error message : > > root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg > > Using config file "/etc/xen/hel.cfg". > > Error: Device 0 (vif) could not be connected. Hotplug scripts not > working. > > > > real 1m41.491s > > user 0m0.116s > > sys 0m0.056s > > And the error is triggered after 100 seconds... > > I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 vanilla > pv_ops kernel. > > In xen-hotplug.log I have only this line : Nothing to flush. > > And in xend.log I found that : > [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for devices > vif. > [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0. > [2010-01-29 15:26:12 6213] DEBUG (DevController:629) > hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. > [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) > XendDomainInfo.destroy: domid=5 > > > > Is there a bug in last pv_ops dom0 kernel, or have I something to fix in > my setup ? >Do you have netback driver/module loaded? Do you have udev installed? Start "udevmonitor" before you start the guest.. do you see hotplug events? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier B.
2010-Feb-16 02:11 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Pasi Kärkkäinen a écrit :> On Fri, Jan 29, 2010 at 03:31:10PM +0100, Olivier B. wrote: > >> Hi, >> >> I tried to upgrade my dom0 kernel from 2.6.31.6-dae-dom0-00751-g60e0545 >> to 2.6.31.6-dae-dom0-00757-ge65323d ; and domU doesn''t start anymore. >> >> I obtain this error message : >> >>> root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg >>> Using config file "/etc/xen/hel.cfg". >>> Error: Device 0 (vif) could not be connected. Hotplug scripts not >>> >> working. >> >>> real 1m41.491s >>> user 0m0.116s >>> sys 0m0.056s >>> >> And the error is triggered after 100 seconds... >> >> I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 vanilla >> pv_ops kernel. >> >> In xen-hotplug.log I have only this line : Nothing to flush. >> >> And in xend.log I found that : >> [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for devices >> vif. >> [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0. >> [2010-01-29 15:26:12 6213] DEBUG (DevController:629) >> hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. >> [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) >> XendDomainInfo.destroy: domid=5 >> >> >> >> Is there a bug in last pv_ops dom0 kernel, or have I something to fix in >> my setup ? >> >> > > Do you have netback driver/module loaded? > > Do you have udev installed? Start "udevmonitor" before you start the guest.. > do you see hotplug events? > > -- Pasi > >Sorry, I didn''t your answer before... So if I start "udevadm monitor", I obtain : udevmonitor will print the received events for: UDEV the event which udev sends out after rule processing UEVENT the kernel uevent UEVENT[1266285891.062392] add /devices/vbd-2-2048 (xen-backend) UDEV [1266285891.064356] add /devices/vbd-2-2048 (xen-backend) UEVENT[1266285891.097244] add /devices/vif-2-0 (xen-backend) UDEV [1266285891.098725] add /devices/vif-2-0 (xen-backend) UEVENT[1266285891.116060] add /devices/vif-2-0/net/vif2.0 (net) UEVENT[1266285891.118280] online /devices/vif-2-0 (xen-backend) UDEV [1266285891.125190] add /devices/vif-2-0/net/vif2.0 (net) UDEV [1266285891.127347] online /devices/vif-2-0 (xen-backend) UEVENT[1266285891.288098] add /devices/console-2-0 (xen-backend) UDEV [1266285891.289979] add /devices/console-2-0 (xen-backend) UEVENT[1266285891.347288] change /devices/virtual/block/drbd2 (block) UEVENT[1266285891.375061] add /kernel/uids/65534 (uids) UDEV [1266285891.376787] add /kernel/uids/65534 (uids) UDEV [1266285891.477763] change /devices/virtual/block/drbd2 (block) UEVENT[1266285892.496161] remove /kernel/uids/65534 (uids) UDEV [1266285892.497624] remove /kernel/uids/65534 (uids) then some "noise" (I suppose) : UEVENT[1266285915.289407] add /kernel/uids/101 (uids) UDEV [1266285915.289918] add /kernel/uids/101 (uids) UEVENT[1266285916.320644] remove /kernel/uids/101 (uids) UDEV [1266285916.322143] remove /kernel/uids/101 (uids) UEVENT[1266285975.204011] add /kernel/uids/101 (uids) UDEV [1266285975.204632] add /kernel/uids/101 (uids) UEVENT[1266285976.236637] remove /kernel/uids/101 (uids) UDEV [1266285976.238076] remove /kernel/uids/101 (uids) and after 100 seconds : UEVENT[1266285991.909492] remove /devices/console-2-0 (xen-backend) UDEV [1266285991.911456] remove /devices/console-2-0 (xen-backend) UEVENT[1266285991.945058] remove /devices/vbd-2-2048 (xen-backend) UDEV [1266285991.946743] remove /devices/vbd-2-2048 (xen-backend) UEVENT[1266285991.948761] offline /devices/vif-2-0 (xen-backend) UDEV [1266285991.950257] offline /devices/vif-2-0 (xen-backend) UEVENT[1266285991.976885] remove /devices/vif-2-0/net/vif2.0 (net) UEVENT[1266285991.989443] remove /devices/vif-2-0 (xen-backend) UEVENT[1266285992.076919] change /devices/virtual/block/drbd2 (block) UDEV [1266285992.111812] change /devices/virtual/block/drbd2 (block) I also update my kernel to the 00776-gce7f50d version and have the same problem. For the netback module, I have this entries in my dom0 .config file : > CONFIG_XEN_NETDEV_BACKEND=y _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
headhunter_unit23
2010-Feb-16 10:33 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi Olivier, I had this problem with Xen 2.6.18-r12 on Gentoo 2.6.31-r6 with udev 146-r1 xm create /PATH/TO/MY/VM/CONF gives after a while: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I had to package.mask the gentoo kernel and udev latest versions and force gentoo to install the following versions: - linux-2.6.29-gentoo-r5 - udev-141 before I compile the xen kernel 2.6.18-r12 I found no other solutions than the above; kernel and udev downgrade, which forced me to reinstall the whole server. The first install with Gentoo 2.6.31-r6 with udev 146-r1 versions gave me: * Mounting proc at /proc * Mounting sysfs at /sys * Your kernel is too old to work with this version of udev. * Current udev only supports Linux kernel 2.6.25 and newer. at boot time and that''s what gave me the hint to downgrade the kernel and udev versions. If you don''t need anything inside the latest kernel, then I suggest you downgrade your kernel and go back to the "working" kernel version. Hope this helps, Cheers, headhunter Olivier B.-2 wrote:> > Hi, > > I tried to upgrade my dom0 kernel from 2.6.31.6-dae-dom0-00751-g60e0545 > to 2.6.31.6-dae-dom0-00757-ge65323d ; and domU doesn''t start anymore. > > I obtain this error message : > > root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg > > Using config file "/etc/xen/hel.cfg". > > Error: Device 0 (vif) could not be connected. Hotplug scripts not > working. > > > > real 1m41.491s > > user 0m0.116s > > sys 0m0.056s > > And the error is triggered after 100 seconds... > > I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 vanilla > pv_ops kernel. > > In xen-hotplug.log I have only this line : Nothing to flush. > > And in xend.log I found that : > [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for devices > vif. > [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0. > [2010-01-29 15:26:12 6213] DEBUG (DevController:629) > hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. > [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) > XendDomainInfo.destroy: domid=5 > > > > Is there a bug in last pv_ops dom0 kernel, or have I something to fix in > my setup ? > > Olivier > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://old.nabble.com/Error%3A-Device-0-%28vif%29-could-not-be-connected.-Hotplug-scripts-not-working.-tp27372757p27606273.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2010-Feb-16 12:36 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
On Tue, Feb 16, 2010 at 03:11:16AM +0100, Olivier B. wrote:> Pasi Kärkkäinen a écrit : >> On Fri, Jan 29, 2010 at 03:31:10PM +0100, Olivier B. wrote: >> >>> Hi, >>> >>> I tried to upgrade my dom0 kernel from >>> 2.6.31.6-dae-dom0-00751-g60e0545 to 2.6.31.6-dae-dom0-00757-ge65323d >>> ; and domU doesn''t start anymore. >>> >>> I obtain this error message : >>> >>>> root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg >>>> Using config file "/etc/xen/hel.cfg". >>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not >>>> >>> working. >>> >>>> real 1m41.491s >>>> user 0m0.116s >>>> sys 0m0.056s >>>> >>> And the error is triggered after 100 seconds... >>> >>> I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 >>> vanilla pv_ops kernel. >>> >>> In xen-hotplug.log I have only this line : Nothing to flush. >>> >>> And in xend.log I found that : >>> [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for >>> devices vif. >>> [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0. >>> [2010-01-29 15:26:12 6213] DEBUG (DevController:629) >>> hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. >>> [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) >>> XendDomainInfo.destroy: domid=5 >>> >>> >>> >>> Is there a bug in last pv_ops dom0 kernel, or have I something to fix >>> in my setup ? >>> >>> >> >> Do you have netback driver/module loaded? >> >> Do you have udev installed? Start "udevmonitor" before you start the >> guest.. do you see hotplug events? >> >> -- Pasi >> >> > Sorry, I didn''t your answer before... So if I start "udevadm monitor", I > obtain : > > udevmonitor will print the received events for: > UDEV the event which udev sends out after rule processing > UEVENT the kernel uevent > > UEVENT[1266285891.062392] add /devices/vbd-2-2048 (xen-backend) > UDEV [1266285891.064356] add /devices/vbd-2-2048 (xen-backend) > UEVENT[1266285891.097244] add /devices/vif-2-0 (xen-backend) > UDEV [1266285891.098725] add /devices/vif-2-0 (xen-backend) > UEVENT[1266285891.116060] add /devices/vif-2-0/net/vif2.0 (net) > UEVENT[1266285891.118280] online /devices/vif-2-0 (xen-backend) > UDEV [1266285891.125190] add /devices/vif-2-0/net/vif2.0 (net) > UDEV [1266285891.127347] online /devices/vif-2-0 (xen-backend) > UEVENT[1266285891.288098] add /devices/console-2-0 (xen-backend) > UDEV [1266285891.289979] add /devices/console-2-0 (xen-backend) > UEVENT[1266285891.347288] change /devices/virtual/block/drbd2 (block) > UEVENT[1266285891.375061] add /kernel/uids/65534 (uids) > UDEV [1266285891.376787] add /kernel/uids/65534 (uids) > UDEV [1266285891.477763] change /devices/virtual/block/drbd2 (block) > UEVENT[1266285892.496161] remove /kernel/uids/65534 (uids) > UDEV [1266285892.497624] remove /kernel/uids/65534 (uids) > > then some "noise" (I suppose) : > UEVENT[1266285915.289407] add /kernel/uids/101 (uids) > UDEV [1266285915.289918] add /kernel/uids/101 (uids) > UEVENT[1266285916.320644] remove /kernel/uids/101 (uids) > UDEV [1266285916.322143] remove /kernel/uids/101 (uids) > UEVENT[1266285975.204011] add /kernel/uids/101 (uids) > UDEV [1266285975.204632] add /kernel/uids/101 (uids) > UEVENT[1266285976.236637] remove /kernel/uids/101 (uids) > UDEV [1266285976.238076] remove /kernel/uids/101 (uids) > > and after 100 seconds : > UEVENT[1266285991.909492] remove /devices/console-2-0 (xen-backend) > UDEV [1266285991.911456] remove /devices/console-2-0 (xen-backend) > UEVENT[1266285991.945058] remove /devices/vbd-2-2048 (xen-backend) > UDEV [1266285991.946743] remove /devices/vbd-2-2048 (xen-backend) > UEVENT[1266285991.948761] offline /devices/vif-2-0 (xen-backend) > UDEV [1266285991.950257] offline /devices/vif-2-0 (xen-backend) > UEVENT[1266285991.976885] remove /devices/vif-2-0/net/vif2.0 (net) > UEVENT[1266285991.989443] remove /devices/vif-2-0 (xen-backend) > UEVENT[1266285992.076919] change /devices/virtual/block/drbd2 (block) > UDEV [1266285992.111812] change /devices/virtual/block/drbd2 (block) > > I also update my kernel to the 00776-gce7f50d version and have the same > problem. > > For the netback module, I have this entries in my dom0 .config file : > > CONFIG_XEN_NETDEV_BACKEND=y >Can you paste your /etc/xen/<guest> cfgfile, thanks. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Grant McWilliams
2010-Feb-16 18:28 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > headhunter > >I battled this one problem as well on CentOS 5.4 forever and my solution was to learn to tiptoe around and not lean too hard on it. Sorry I can''t be of more help. I never found a solution. Grant McWilliams Some people, when confronted with a problem, think "I know, I''ll use Windows." Now they have two problems. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Feb-16 22:23 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
On Wed, Feb 17, 2010 at 1:28 AM, Grant McWilliams <grantmasterflash@gmail.com> wrote:> >> Error: Device 0 (vif) could not be connected. Hotplug scripts not working. >> headhunter >> > > I battled this one problem as well on CentOS 5.4 forever and my solution was > to learn to tiptoe around and not lean too hard on it.Really? I don''t know about other distros, but when it comes to RHEL/Centos and Xen 3.1+/3.3/3.4, the cause is usually udev is dead. At least that what happens to me a couple of times. I haven''t find out WHY udev is dead though, and since I haven''t had it in several months I assume one of the updates has fixed it. Another usual cause is putting in a wrong bridge name, but that one gives a clear error message on xend.log so it''s easier to solve. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier B.
2010-Feb-17 12:49 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Olivier B. a écrit :> Pasi Kärkkäinen a écrit : >> On Fri, Jan 29, 2010 at 03:31:10PM +0100, Olivier B. wrote: >> >>> Hi, >>> >>> I tried to upgrade my dom0 kernel from >>> 2.6.31.6-dae-dom0-00751-g60e0545 to >>> 2.6.31.6-dae-dom0-00757-ge65323d ; and domU doesn''t start anymore. >>> >>> I obtain this error message : >>> >>>> root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg >>>> Using config file "/etc/xen/hel.cfg". >>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not >>>> >>> working. >>> >>>> real 1m41.491s >>>> user 0m0.116s >>>> sys 0m0.056s >>>> >>> And the error is triggered after 100 seconds... >>> >>> I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 >>> vanilla pv_ops kernel. >>> >>> In xen-hotplug.log I have only this line : Nothing to flush. >>> >>> And in xend.log I found that : >>> [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for >>> devices vif. >>> [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0. >>> [2010-01-29 15:26:12 6213] DEBUG (DevController:629) >>> hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. >>> [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) >>> XendDomainInfo.destroy: domid=5 >>> >>> >>> >>> Is there a bug in last pv_ops dom0 kernel, or have I something to >>> fix in my setup ? >>> >>> >> >> Do you have netback driver/module loaded? >> >> Do you have udev installed? Start "udevmonitor" before you start the >> guest.. do you see hotplug events? >> >> -- Pasi >> >> > Sorry, I didn''t your answer before... So if I start "udevadm monitor", > I obtain : > > udevmonitor will print the received events for: > UDEV the event which udev sends out after rule processing > UEVENT the kernel uevent > > UEVENT[1266285891.062392] add /devices/vbd-2-2048 (xen-backend) > UDEV [1266285891.064356] add /devices/vbd-2-2048 (xen-backend) > UEVENT[1266285891.097244] add /devices/vif-2-0 (xen-backend) > UDEV [1266285891.098725] add /devices/vif-2-0 (xen-backend) > UEVENT[1266285891.116060] add /devices/vif-2-0/net/vif2.0 (net) > UEVENT[1266285891.118280] online /devices/vif-2-0 (xen-backend) > UDEV [1266285891.125190] add /devices/vif-2-0/net/vif2.0 (net) > UDEV [1266285891.127347] online /devices/vif-2-0 (xen-backend) > UEVENT[1266285891.288098] add /devices/console-2-0 (xen-backend) > UDEV [1266285891.289979] add /devices/console-2-0 (xen-backend) > UEVENT[1266285891.347288] change /devices/virtual/block/drbd2 (block) > UEVENT[1266285891.375061] add /kernel/uids/65534 (uids) > UDEV [1266285891.376787] add /kernel/uids/65534 (uids) > UDEV [1266285891.477763] change /devices/virtual/block/drbd2 (block) > UEVENT[1266285892.496161] remove /kernel/uids/65534 (uids) > UDEV [1266285892.497624] remove /kernel/uids/65534 (uids) > > then some "noise" (I suppose) : > UEVENT[1266285915.289407] add /kernel/uids/101 (uids) > UDEV [1266285915.289918] add /kernel/uids/101 (uids) > UEVENT[1266285916.320644] remove /kernel/uids/101 (uids) > UDEV [1266285916.322143] remove /kernel/uids/101 (uids) > UEVENT[1266285975.204011] add /kernel/uids/101 (uids) > UDEV [1266285975.204632] add /kernel/uids/101 (uids) > UEVENT[1266285976.236637] remove /kernel/uids/101 (uids) > UDEV [1266285976.238076] remove /kernel/uids/101 (uids) > > and after 100 seconds : > UEVENT[1266285991.909492] remove /devices/console-2-0 (xen-backend) > UDEV [1266285991.911456] remove /devices/console-2-0 (xen-backend) > UEVENT[1266285991.945058] remove /devices/vbd-2-2048 (xen-backend) > UDEV [1266285991.946743] remove /devices/vbd-2-2048 (xen-backend) > UEVENT[1266285991.948761] offline /devices/vif-2-0 (xen-backend) > UDEV [1266285991.950257] offline /devices/vif-2-0 (xen-backend) > UEVENT[1266285991.976885] remove /devices/vif-2-0/net/vif2.0 (net) > UEVENT[1266285991.989443] remove /devices/vif-2-0 (xen-backend) > UEVENT[1266285992.076919] change /devices/virtual/block/drbd2 (block) > UDEV [1266285992.111812] change /devices/virtual/block/drbd2 (block) > > I also update my kernel to the 00776-gce7f50d version and have the > same problem. > > For the netback module, I have this entries in my dom0 .config file : > > CONFIG_XEN_NETDEV_BACKEND=y > >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=writeback'' disk = [ ''drbd:athena-disk,sda,w'' ] vif = [ ''mac=02:00:00:00:04:3f'' ] extra = ''rootdelay=1 raid=noautodetect'' on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' Olivier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2010-Feb-17 13:55 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
On Wed, Feb 17, 2010 at 01:49:46PM +0100, Olivier B. wrote:> Olivier B. a écrit : >> Pasi Kärkkäinen a écrit : >>> On Fri, Jan 29, 2010 at 03:31:10PM +0100, Olivier B. wrote: >>> >>>> Hi, >>>> >>>> I tried to upgrade my dom0 kernel from >>>> 2.6.31.6-dae-dom0-00751-g60e0545 to >>>> 2.6.31.6-dae-dom0-00757-ge65323d ; and domU doesn''t start anymore. >>>> >>>> I obtain this error message : >>>> >>>>> root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg >>>>> Using config file "/etc/xen/hel.cfg". >>>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not >>>>> >>>> working. >>>> >>>>> real 1m41.491s >>>>> user 0m0.116s >>>>> sys 0m0.056s >>>>> >>>> And the error is triggered after 100 seconds... >>>> >>>> I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 >>>> vanilla pv_ops kernel. >>>> >>>> In xen-hotplug.log I have only this line : Nothing to flush. >>>> >>>> And in xend.log I found that : >>>> [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for >>>> devices vif. >>>> [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0. >>>> [2010-01-29 15:26:12 6213] DEBUG (DevController:629) >>>> hotplugStatusCallback >>>> /local/domain/0/backend/vif/5/0/hotplug-status. >>>> [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) >>>> XendDomainInfo.destroy: domid=5 >>>> >>>> >>>> >>>> Is there a bug in last pv_ops dom0 kernel, or have I something to >>>> fix in my setup ? >>>> >>>> >>> >>> Do you have netback driver/module loaded? >>> >>> Do you have udev installed? Start "udevmonitor" before you start the >>> guest.. do you see hotplug events? >>> >>> -- Pasi >>> >>> >> Sorry, I didn''t your answer before... So if I start "udevadm monitor", >> I obtain : >> >> udevmonitor will print the received events for: >> UDEV the event which udev sends out after rule processing >> UEVENT the kernel uevent >> >> UEVENT[1266285891.062392] add /devices/vbd-2-2048 (xen-backend) >> UDEV [1266285891.064356] add /devices/vbd-2-2048 (xen-backend) >> UEVENT[1266285891.097244] add /devices/vif-2-0 (xen-backend) >> UDEV [1266285891.098725] add /devices/vif-2-0 (xen-backend) >> UEVENT[1266285891.116060] add /devices/vif-2-0/net/vif2.0 (net) >> UEVENT[1266285891.118280] online /devices/vif-2-0 (xen-backend) >> UDEV [1266285891.125190] add /devices/vif-2-0/net/vif2.0 (net) >> UDEV [1266285891.127347] online /devices/vif-2-0 (xen-backend) >> UEVENT[1266285891.288098] add /devices/console-2-0 (xen-backend) >> UDEV [1266285891.289979] add /devices/console-2-0 (xen-backend) >> UEVENT[1266285891.347288] change /devices/virtual/block/drbd2 (block) >> UEVENT[1266285891.375061] add /kernel/uids/65534 (uids) >> UDEV [1266285891.376787] add /kernel/uids/65534 (uids) >> UDEV [1266285891.477763] change /devices/virtual/block/drbd2 (block) >> UEVENT[1266285892.496161] remove /kernel/uids/65534 (uids) >> UDEV [1266285892.497624] remove /kernel/uids/65534 (uids) >> >> then some "noise" (I suppose) : >> UEVENT[1266285915.289407] add /kernel/uids/101 (uids) >> UDEV [1266285915.289918] add /kernel/uids/101 (uids) >> UEVENT[1266285916.320644] remove /kernel/uids/101 (uids) >> UDEV [1266285916.322143] remove /kernel/uids/101 (uids) >> UEVENT[1266285975.204011] add /kernel/uids/101 (uids) >> UDEV [1266285975.204632] add /kernel/uids/101 (uids) >> UEVENT[1266285976.236637] remove /kernel/uids/101 (uids) >> UDEV [1266285976.238076] remove /kernel/uids/101 (uids) >> >> and after 100 seconds : >> UEVENT[1266285991.909492] remove /devices/console-2-0 (xen-backend) >> UDEV [1266285991.911456] remove /devices/console-2-0 (xen-backend) >> UEVENT[1266285991.945058] remove /devices/vbd-2-2048 (xen-backend) >> UDEV [1266285991.946743] remove /devices/vbd-2-2048 (xen-backend) >> UEVENT[1266285991.948761] offline /devices/vif-2-0 (xen-backend) >> UDEV [1266285991.950257] offline /devices/vif-2-0 (xen-backend) >> UEVENT[1266285991.976885] remove /devices/vif-2-0/net/vif2.0 (net) >> UEVENT[1266285991.989443] remove /devices/vif-2-0 (xen-backend) >> UEVENT[1266285992.076919] change /devices/virtual/block/drbd2 (block) >> UDEV [1266285992.111812] change /devices/virtual/block/drbd2 (block) >> >> I also update my kernel to the 00776-gce7f50d version and have the >> same problem. >> >> For the netback module, I have this entries in my dom0 .config file : >> > CONFIG_XEN_NETDEV_BACKEND=y >> >> > > 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=writeback'' > disk = [ ''drbd:athena-disk,sda,w'' ] > vif = [ ''mac=02:00:00:00:04:3f'' ] > extra = ''rootdelay=1 raid=noautodetect'' > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' >What if you also specify the bridge on the vif line? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier B.
2010-Feb-17 14:21 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
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=writeback'' >> disk = [ ''drbd:athena-disk,sda,w'' ] >> vif = [ ''mac=02:00:00:00:04:3f'' ] >> extra = ''rootdelay=1 raid=noautodetect'' >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart'' >> >> > > 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'' ]" : 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@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2010-Feb-17 17:24 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
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=writeback'' >>> disk = [ ''drbd:athena-disk,sda,w'' ] >>> vif = [ ''mac=02:00:00:00:04:3f'' ] >>> extra = ''rootdelay=1 raid=noautodetect'' >>> on_poweroff = ''destroy'' >>> on_reboot = ''restart'' >>> on_crash = ''restart'' >>> >>> >> >> 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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier B.
2010-Feb-24 10:55 UTC
Re: [Xen-users] [SOLVED] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
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=writeback'' >>>> disk = [ ''drbd:athena-disk,sda,w'' ] >>>> vif = [ ''mac=02:00:00:00:04:3f'' ] >>>> extra = ''rootdelay=1 raid=noautodetect'' >>>> on_poweroff = ''destroy'' >>>> on_reboot = ''restart'' >>>> on_crash = ''restart'' >>>> >>>> >>>> >>> 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@lists.xensource.com >> 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. Thanks, Olivier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Viau
2010-Feb-24 15:00 UTC
RE: [Xen-users] [SOLVED] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> 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=writeback'' > >>>> disk = [ ''drbd:athena-disk,sda,w'' ] > >>>> vif = [ ''mac=02:00:00:00:04:3f'' ] > >>>> extra = ''rootdelay=1 raid=noautodetect'' > >>>> on_poweroff = ''destroy'' > >>>> on_reboot = ''restart'' > >>>> on_crash = ''restart'' > >>>> > >>>> > >>>> > >>> 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@lists.xensource.com > >> 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@lists.xensource.com > http://lists.xensource.com/xen-users_________________________________________________________________ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier B.
2010-Feb-24 15:28 UTC
Re: [Xen-users] [SOLVED] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
On 24/02/2010 16:00, Mike Viau wrote:> 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 > >You''re right, I reduced the list to some network options : > CONFIG_NETFILTER_XT_TARGET_TRACE=m < CONFIG_NETFILTER_XT_MATCH_COMMENT=y < CONFIG_NETFILTER_XT_MATCH_DCCP=y > CONFIG_NETFILTER_XT_MATCH_COMMENT=m > CONFIG_NETFILTER_XT_MATCH_DCCP=m < CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=y > CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m < CONFIG_NETFILTER_XT_MATCH_LIMIT=y < CONFIG_NETFILTER_XT_MATCH_MAC=y > CONFIG_NETFILTER_XT_MATCH_LIMIT=m > CONFIG_NETFILTER_XT_MATCH_MAC=m < CONFIG_NETFILTER_XT_MATCH_POLICY=y > CONFIG_NETFILTER_XT_MATCH_OWNER=m > CONFIG_NETFILTER_XT_MATCH_POLICY=m > CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m < CONFIG_NETFILTER_XT_MATCH_REALM=y > CONFIG_NETFILTER_XT_MATCH_REALM=m < CONFIG_NETFILTER_XT_TARGET_IMQ=m < CONFIG_IMQ=m < CONFIG_IMQ_BEHAVIOR_AB=y < CONFIG_IMQ_NUM_DEVS=16 I''m compiling a version without IMQ options. Olivier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier B.
2010-Feb-24 18:07 UTC
Re: [Xen-users] [SOLVED] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
So, the winner is "CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m". If I don''t compile at all this module, all works fine. Any idea why this module seem to be incompatible with my setup ? Olivier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier B.
2010-Feb-24 18:51 UTC
Re: [Xen-users] [SOLVED] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
On 24/02/2010 19:07, Olivier B. wrote:> So, the winner is "CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m". > If I don''t compile at all this module, all works fine. > > Any idea why this module seem to be incompatible with my setup ? >If I put "xt_physdev" in /etc/modprobe.d/blacklist, it also works. So I suppose it''s a bug in the debian bridge script. If I don''t blacklist the module, I only see this rule in FORWARD : Chain FORWARD (policy ACCEPT 202 packets, 32632 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-in vif5.0 And it doesn''t start. I obtain "Error: Device 0 (vif) could not be connected. Hotplug scripts not working." after 100 seconds. But if I comment this four lines in /etc/xen/scripts/vif-common.sh, FORWARD stay empty, and DomU starts. > iptables "$c" FORWARD -m physdev --physdev-in "$vif" "$@" -j ACCEPT \ > 2>/dev/null && > iptables "$c" FORWARD -m state --state RELATED,ESTABLISHED -m physdev \ > --physdev-out "$vif" -j ACCEPT 2>/dev/null Also, if I let the FORWARD rule and start the DomU, it wait until the 100 seconds timeout _OR_ I flush the FORWARD rules. What is the role of this netfilter rule ? Without that it seems to work well... Olivier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users