thr3ads.net - Xen users - [Xen-users] problem of vif starting the fisrt DomU [Oct 2006]

If this information is useful, please help other people find it:
Share via:

Kali Mero

2006-Oct-27 19:19 UTC

[Xen-users] problem of vif starting the fisrt DomU

Hi, it''s my first post on this forum and my first post also about xen.
I search on internet about this problem and no answer, i am amazed because
it looks common issue.
(for example
http://lists.xensource.com/archives/html/xen-users/2006-06/msg01128.html or
http://www.debian-administration.org/articles/396#comment_24)

When creating a guest Domain, the domain exist during 1minute 40s, and then
i have the following error:
"Error: Device 0 (vif) could not be connected. Hotplug scripts not
working."

At the end of the mail i added xend.log
xend-debug.log give this when starting xend service :
Link veth0 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the
parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.

xend-hotplug.log is empty

i have tested with diferent values of the nloopbacks kernel parameter. and
checked the xen-backend.rules link, moreover if i am right xen should create
by default 7 vethx.
Another point is that when i do "ifconfig" i only see eth0 and lo.

So questions are:
Should i see with ifconfig the vifx.y, or the veth0 ?
Is the message about veth0 at the sart of xend linked to this problem, how
can i solve it ?
Do i need to change the network-bridge script, is it a udev issue ?
My PC is a laptop (compaq presario 3000 serie) can this be linked ?

I thank you in advice for any clue or information. You are my last hope to
make xen work.

Thank you,

Cyril Olivier

[2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:190)
XendDomainInfo.create([''vm'', [''name'',
''ExampleDomain''], [''memory'', 96],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/bck_PAE/vmlinuz-
2.6.16-1.2218_FC6xenU-PAE''], [''ramdisk'',
''/boot/bck_PAE/initrd-
2.6.16-1.2218_FC6xenU-PAE.img''], [''root'',
''/dev/hda1 rw''], [''args'',
''ramdisk_size=32758 selinux=0 quiet'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/vm/images/rootfs.img''], [''dev'',
''hda1''], [''mode'', ''w'']]],
[''device'',
[''vif'']]])
[2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:296)
parseConfig: config is [''vm'', [''name'',
''ExampleDomain''], [''memory'', 96],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/bck_PAE/vmlinuz-
2.6.16-1.2218_FC6xenU-PAE''], [''ramdisk'',
''/boot/bck_PAE/initrd-
2.6.16-1.2218_FC6xenU-PAE.img''], [''root'',
''/dev/hda1 rw''], [''args'',
''ramdisk_size=32758 selinux=0 quiet'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/vm/images/rootfs.img''], [''dev'',
''hda1''], [''mode'', ''w'']]],
[''device'',
[''vif'']]]
[2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:395)
parseConfig: result is {''shadow_memory'': None,
''uuid'': None, ''on_crash'':
None, ''on_reboot'': None, ''localtime'': None,
''image'': [''linux'',
[''kernel'',
''/boot/bck_PAE/vmlinuz-2.6.16-1.2218_FC6xenU-PAE''],
[''ramdisk'',
''/boot/bck_PAE/initrd-2.6.16-1.2218_FC6xenU-PAE.img''],
[''root'', ''/dev/hda1
rw''], [''args'', ''ramdisk_size=32758 selinux=0
quiet'']], ''on_poweroff'': None,
''bootloader_args'': None, ''cpus'': None,
''name'': ''ExampleDomain'',
''backend'':
[], ''vcpus'': 1, ''cpu_weight'': None,
''features'': None, ''vcpu_avail'': None,
''memory'': 96, ''device'':
[(''vbd'', [''vbd'', [''uname'',
''phy:/vm/images/rootfs.img''], [''dev'',
''hda1''], [''mode'', ''w'']]),
(''vif'',
[''vif''])], ''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1253)
XendDomainInfo.construct: None
[2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1285)
XendDomainInfo.initDomain: 2 1.0
[2006-10-27 11:01:04 xend 2203] DEBUG (balloon:127) Balloon: 98748 KiB free;
need 98304; done.
[2006-10-27 11:01:04 xend 2203] INFO (image:136) buildDomain os=linux dom=2
vcpus=1
[2006-10-27 11:01:04 xend 2203] DEBUG (image:191) dom            = 2
[2006-10-27 11:01:04 xend 2203] DEBUG (image:192) image         
/boot/bck_PAE/vmlinuz-2.6.16-1.2218_FC6xenU-PAE
[2006-10-27 11:01:04 xend 2203] DEBUG (image:193) store_evtchn   = 1
[2006-10-27 11:01:04 xend 2203] DEBUG (image:194) console_evtchn = 2
[2006-10-27 11:01:04 xend 2203] DEBUG (image:195) cmdline        root=/dev/hda1
rw ramdisk_size=32758 selinux=0 quiet
[2006-10-27 11:01:04 xend 2203] DEBUG (image:196) ramdisk       
/boot/bck_PAE/initrd-2.6.16-1.2218_FC6xenU-PAE.img
[2006-10-27 11:01:04 xend 2203] DEBUG (image:197) vcpus          = 1
[2006-10-27 11:01:04 xend 2203] DEBUG (image:198) features       [2006-10-27
11:01:04 xend 2203] DEBUG (DevController:110) DevController:
writing {''backend-id'': ''0'',
''virtual-device'': ''769'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/2/769''} to
/local/domain/2/device/vbd/769.
[2006-10-27 11:01:04 xend 2203] DEBUG (DevController:112) DevController:
writing {''domain'': ''ExampleDomain'',
''frontend'':
''/local/domain/2/device/vbd/769'', ''dev'':
''hda1'', ''state'': ''1'',
''params'':
''/vm/images/rootfs.img'', ''mode'':
''w'', ''online'': ''1'',
''frontend-id'': ''2'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/2/769.
[2006-10-27 11:01:05 xend 2203] DEBUG (DevController:110) DevController:
writing {''backend-id'': ''0'',
''mac'': ''00:16:3e:53:79:a7'',
''handle'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vif/2/0''} to
/local/domain/2/device/vif/0.
[2006-10-27 11:01:05 xend 2203] DEBUG (DevController:112) DevController:
writing {''domain'': ''ExampleDomain'',
''handle'': ''0'', ''script'':
''/etc/xen/scripts/vif-bridge'', ''state'':
''1'', ''frontend'':
''/local/domain/2/device/vif/0'', ''mac'':
''00:16:3e:53:79:a7'', ''online'':
''1'',
''frontend-id'': ''2''} to
/local/domain/0/backend/vif/2/0.
[2006-10-27 11:01:05 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:712)
Storing VM details: {''shadow_memory'': ''0'',
''uuid'':
''876dfffe-ac6f-738f-5194-28a47f88f31c'',
''on_reboot'': ''restart'',
''start_time'': ''1161964865.03'',
''on_poweroff'': ''destroy'',
''name'':
''ExampleDomain'', ''xend/restart_count'':
''0'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''96'',
''on_crash'': ''restart'',
''image'': "(linux (kernel
/boot/bck_PAE/vmlinuz-2.6.16-1.2218_FC6xenU-PAE) (ramdisk
/boot/bck_PAE/initrd-2.6.16-1.2218_FC6xenU-PAE.img) (root ''/dev/hda1
rw'')
(args ''ramdisk_size=32758 selinux=0 quiet''))",
''maxmem'': ''96''}
[2006-10-27 11:01:05 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:747)
Storing domain details: {''console/ring-ref'':
''58529'', ''console/port'':
''2'',
''name'': ''ExampleDomain'',
''console/limit'': ''1048576'',
''vm'':
''/vm/876dfffe-ac6f-738f-5194-28a47f88f31c'',
''domid'': ''2'',
''cpu/0/availability'': ''online'',
''memory/target'': ''98304'',
''store/ring-ref'':
''58530'', ''store/port'':
''1''}
[2006-10-27 11:01:05 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:933)
XendDomainInfo.handleShutdownWatch
[2006-10-27 11:01:05 xend 2203] DEBUG (DevController:143) Waiting for
devices vif.
[2006-10-27 11:01:05 xend 2203] DEBUG (DevController:149) Waiting for 0.
[2006-10-27 11:01:05 xend 2203] DEBUG (DevController:464)
hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2006-10-27 11:02:45 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1449)
XendDomainInfo.destroy: domid=2
[2006-10-27 11:02:45 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1457)
XendDomainInfo.destroyDomain(2)


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Cyril Olivier

2006-Oct-27 20:25 UTC

head link

[Xen-users] Re: problem of vif starting the fisrt DomU

I have followed this link:
http://lists.xensource.com/archives/html/xen-devel/2005-12/msg00212.html
I saw it just after sending the first mail

[root@CatarNux udev]# udevinfo -V
udevinfo, version 095

[root@CatarNux ~]# udevmonitor
udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]

UEVENT[1161978472.581630] add@/devices/xen-backend/vbd-5-769
UDEV  [1161978472.581630] add@/devices/xen-backend/vbd-5-769
UEVENT[1161978472.598913] add@/devices/xen-backend/vif-5-0
UDEV  [1161978472.598913] add@/devices/xen-backend/vif-5-0

I don''t have any "online" event.
So does it mean the problem come from udev ?

Thank you in advance,

Cyrille Olivier

udevmonitor --env
[root@CatarNux ~]# udevmonitor --env
udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]

UEVENT[1161979210.946535] add@/devices/xen-backend/vbd-7-769
UDEV  [1161979210.946535] add@/devices/xen-backend/vbd-7-769
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/xen-backend/vbd-7-769
SUBSYSTEM=xen-backend
SEQNUM=763
PHYSDEVBUS=xen-backend
XENBUS_TYPE=vbd
XENBUS_PATH=backend/vbd/7/769
XENBUS_BASE_PATH=backend
UDEVD_EVENT=1

UEVENT[1161979210.963339] add@/devices/xen-backend/vif-7-0
UDEV  [1161979210.963339] add@/devices/xen-backend/vif-7-0
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/xen-backend/vif-7-0
SUBSYSTEM=xen-backend
SEQNUM=764
PHYSDEVBUS=xen-backend
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/7/0
XENBUS_BASE_PATH=backend
UDEVD_EVENT=1



On 10/27/06, Kali Mero <calimeral@gmail.com>
wrote:>
> Hi, it''s my first post on this forum and my first post also about
xen.
> I search on internet about this problem and no answer, i am amazed because
> it looks common issue.
> (for example
> http://lists.xensource.com/archives/html/xen-users/2006-06/msg01128.htmlor
> http://www.debian-administration.org/articles/396#comment_24)
>
> When creating a guest Domain, the domain exist during 1minute 40s, and
> then i have the following error:
> "Error: Device 0 (vif) could not be connected. Hotplug scripts not
> working."
>
> At the end of the mail i added xend.log
> xend-debug.log give this when starting xend service :
> Link veth0 is missing.
> This may be because you have reached the limit of the number of interfaces
> that the loopback driver supports.  If the loopback driver is a module,
> you
> may raise this limit by passing it as a parameter (nloopbacks=<N>);
if the
> driver is compiled statically into the kernel, then you may set the
> parameter
> using loopback.nloopbacks=<N> on the domain 0 kernel command line.
>
> xend-hotplug.log is empty
>
> i have tested with diferent values of the nloopbacks kernel parameter. and
> checked the xen-backend.rules link, moreover if i am right xen should
> create by default 7 vethx.
> Another point is that when i do "ifconfig" i only see eth0 and
lo.
>
> So questions are:
> Should i see with ifconfig the vifx.y, or the veth0 ?
> Is the message about veth0 at the sart of xend linked to this problem, how
> can i solve it ?
> Do i need to change the network-bridge script, is it a udev issue ?
> My PC is a laptop (compaq presario 3000 serie) can this be linked ?
>
> I thank you in advice for any clue or information. You are my last hope to
> make xen work.
>
> Thank you,
>
> Cyril Olivier
>
> [2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:190)
> XendDomainInfo.create([''vm'', [''name'',
''ExampleDomain''], [''memory'', 96],
> [''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/bck_PAE/vmlinuz-
> 2.6.16-1.2218_FC6xenU-PAE''], [''ramdisk'',
''/boot/bck_PAE/initrd-
> 2.6.16-1.2218_FC6xenU-PAE.img''], [''root'',
''/dev/hda1 rw''], [''args'',
> ''ramdisk_size=32758 selinux=0 quiet'']]],
[''device'', [''vbd'',
[''uname'',
> ''phy:/vm/images/rootfs.img''], [''dev'',
''hda1''], [''mode'', ''w'']]],
[''device'',
> [''vif'']]])
> [2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:296)
> parseConfig: config is [''vm'', [''name'',
''ExampleDomain''], [''memory'', 96],
> [''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/bck_PAE/vmlinuz-
> 2.6.16-1.2218_FC6xenU-PAE''], [''ramdisk'',
''/boot/bck_PAE/initrd-
> 2.6.16-1.2218_FC6xenU-PAE.img''], [''root'',
''/dev/hda1 rw''], [''args'',
> ''ramdisk_size=32758 selinux=0 quiet'']]],
[''device'', [''vbd'',
[''uname'',
> ''phy:/vm/images/rootfs.img''], [''dev'',
''hda1''], [''mode'', ''w'']]],
[''device'',
> [''vif'']]]
> [2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:395)
> parseConfig: result is {''shadow_memory'': None,
''uuid'': None, ''on_crash'':
> None, ''on_reboot'': None, ''localtime'':
None, ''image'': [''linux'',
[''kernel'',
> ''/boot/bck_PAE/vmlinuz-2.6.16-1.2218_FC6xenU-PAE''],
[''ramdisk'',
> ''/boot/bck_PAE/initrd-2.6.16-1.2218_FC6xenU-PAE.img''],
[''root'', ''/dev/hda1
> rw''], [''args'', ''ramdisk_size=32758
selinux=0 quiet'']], ''on_poweroff'': None,
> ''bootloader_args'': None, ''cpus'': None,
''name'': ''ExampleDomain'',
''backend'':
> [], ''vcpus'': 1, ''cpu_weight'': None,
''features'': None, ''vcpu_avail'': None,
> ''memory'': 96, ''device'':
[(''vbd'', [''vbd'', [''uname'',
> ''phy:/vm/images/rootfs.img''], [''dev'',
''hda1''], [''mode'', ''w'']]),
(''vif'',
> [''vif''])], ''bootloader'': None,
''cpu'': None, ''maxmem'': None}
> [2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1253)
> XendDomainInfo.construct: None
> [2006-10-27 11:01:04 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1285)
> XendDomainInfo.initDomain: 2 1.0
> [2006-10-27 11:01:04 xend 2203] DEBUG (balloon:127) Balloon: 98748 KiB
> free; need 98304; done.
> [2006-10-27 11:01:04 xend 2203] INFO (image:136) buildDomain os=linux
> dom=2 vcpus=1
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:191) dom            = 2
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:192) image          >
/boot/bck_PAE/vmlinuz-2.6.16-1.2218_FC6xenU-PAE
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:193) store_evtchn   = 1
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:194) console_evtchn = 2
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:195) cmdline        >
root=/dev/hda1 rw ramdisk_size=32758 selinux=0 quiet
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:196) ramdisk        >
/boot/bck_PAE/initrd-2.6.16-1.2218_FC6xenU-PAE.img
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:197) vcpus          = 1
> [2006-10-27 11:01:04 xend 2203] DEBUG (image:198) features       >
[2006-10-27 11:01:04 xend 2203] DEBUG (DevController:110) DevController:
> writing {''backend-id'': ''0'',
''virtual-device'': ''769'',
''device-type'': ''disk'',
> ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/2/769''} to
> /local/domain/2/device/vbd/769.
> [2006-10-27 11:01:04 xend 2203] DEBUG (DevController:112) DevController:
> writing {''domain'': ''ExampleDomain'',
''frontend'':
> ''/local/domain/2/device/vbd/769'',
''dev'': ''hda1'', ''state'':
''1'', ''params'':
> ''/vm/images/rootfs.img'', ''mode'':
''w'', ''online'': ''1'',
''frontend-id'': ''2'',
> ''type'': ''phy''} to
/local/domain/0/backend/vbd/2/769.
> [2006-10-27 11:01:05 xend 2203] DEBUG (DevController:110) DevController:
> writing {''backend-id'': ''0'',
''mac'': ''00:16:3e:53:79:a7'',
''handle'': ''0'',
> ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/2/0''} to
> /local/domain/2/device/vif/0.
> [2006-10-27 11:01:05 xend 2203] DEBUG (DevController:112) DevController:
> writing {''domain'': ''ExampleDomain'',
''handle'': ''0'', ''script'':
> ''/etc/xen/scripts/vif-bridge'', ''state'':
''1'', ''frontend'':
> ''/local/domain/2/device/vif/0'', ''mac'':
''00:16:3e:53:79:a7'', ''online'':
''1'',
> ''frontend-id'': ''2''} to
/local/domain/0/backend/vif/2/0.
> [2006-10-27 11:01:05 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:712)
> Storing VM details: {''shadow_memory'':
''0'', ''uuid'':
> ''876dfffe-ac6f-738f-5194-28a47f88f31c'',
''on_reboot'': ''restart'',
> ''start_time'': ''1161964865.03'',
''on_poweroff'': ''destroy'',
''name'':
> ''ExampleDomain'', ''xend/restart_count'':
''0'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
> ''memory'': ''96'',
''on_crash'': ''restart'',
''image'': "(linux (kernel
> /boot/bck_PAE/vmlinuz-2.6.16-1.2218_FC6xenU-PAE) (ramdisk
> /boot/bck_PAE/initrd-2.6.16-1.2218_FC6xenU-PAE.img) (root
''/dev/hda1 rw'')
> (args ''ramdisk_size=32758 selinux=0 quiet''))",
''maxmem'': ''96''}
> [2006-10-27 11:01:05 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:747)
> Storing domain details: {''console/ring-ref'':
''58529'', ''console/port'':
''2'',
> ''name'': ''ExampleDomain'',
''console/limit'': ''1048576'',
''vm'':
> ''/vm/876dfffe-ac6f-738f-5194-28a47f88f31c'',
''domid'': ''2'',
> ''cpu/0/availability'': ''online'',
''memory/target'': ''98304'',
''store/ring-ref'':
> ''58530'', ''store/port'':
''1''}
> [2006-10-27 11:01:05 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:933)
> XendDomainInfo.handleShutdownWatch
> [2006-10-27 11:01:05 xend 2203] DEBUG (DevController:143) Waiting for
> devices vif.
> [2006-10-27 11:01:05 xend 2203] DEBUG (DevController:149) Waiting for 0.
> [2006-10-27 11:01:05 xend 2203] DEBUG (DevController:464)
> hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
> [2006-10-27 11:02:45 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1449)
> XendDomainInfo.destroy: domid=2
> [2006-10-27 11:02:45 xend.XendDomainInfo 2203] DEBUG (XendDomainInfo:1457)
> XendDomainInfo.destroyDomain(2)
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Cyril Olivier

2006-Oct-27 23:05 UTC

head link

[Xen-users] Re: problem of vif starting the fisrt DomU

<file:///C:/_Perso/xend.log>One last point. I have activate the hotplug
traces.
In the hotplug log i can see:
+ logger -p daemon.err -- /etc/xen/scripts/block: ''Device
/vm/images/rootfs.img is mounted in the privileged domain,
and so cannot be mounted by a guest.''
I am not sure it is relevant because this file is not mount in my system.

Regards,

Cyril Olivier





_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Oct 2006 - problem of vif starting the fisrt DomU

[Xen-users] problem of vif starting the fisrt DomU

[Xen-users] Re: problem of vif starting the fisrt DomU

[Xen-users] Re: problem of vif starting the fisrt DomU