| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug sc
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home