thr3ads.net - Xen users - [Xen-users] fedora core 5 and XEN networking issue [Apr 2006]

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

Fong Vang

2006-Apr-13 17:07 UTC

[Xen-users] fedora core 5 and XEN networking issue

I''ve been using Xen on Fedora Core 4 without any problem.  Recently, I
upgraded (reinstalled from scratch) another Fedora Core 5 system.  I''m
having a difficult time getting a network interface configured for a
domU.  This is my configure file:

   kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
   memory = 1024
   name = "meta"
   vif = [ '''' ]
disk = [ ''phy:xenvg/metaboot,sda1,w'',
''phy:xenvg/metaroot,sda2,w'',
''phy:xenvg/   metausr,sda3,w'',
''phy:xenvg/metavar,sda4,w'',
''phy:xenvg/metaswap,sda5,w'' ]
   vtpm = [ ''instance=1,backend=0'' ]
   root = "/dev/sda2 ro"
   extra = "3"

I''ve also tried this line for the vif:

   vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ]

However, I''m still not able to get eth0 in domU to work.

[root@meta ~]# ifconfig eth0 192.168.1.10 netmask 255.255.255.0
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device
SIOCGIFADDR: No such device
SIOCSIFBROADCAST: No such device

I''m seeing this in xend.log:

[2006-04-13 16:59:22 xend.XendDomainInfo] DEBUG (XendDomainInfo:667)
Storing VM details: {''ssidref'': ''0'',
''uuid'':
''87c2f135-822b-13b6-556f-ebbc93ba8f88'', ''on
_reboot'': ''restart'', ''start_time'':
''1144947562.33'', ''on_poweroff'':
''destroy'', ''name'': ''meta'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'':
''1024'', ''on_crash'':
''restart'', ''image'': "(linux (kernel
/boot/vmlinuz-2.6.16-1.2080_FC5xenU) (root ''/dev/sda2 ro'')
(args 3))",
''maxmem'': ''1024''}
[2006-04-13 16:59:22 xend.XendDomainInfo] DEBUG (XendDomainInfo:692)
Storing domain details: {''console/ring-ref'':
''878415'', ''console/port'':
''2'', ''name'': ''met
a'', ''console/limit'': ''1048576'',
''vm'':
''/vm/87c2f135-822b-13b6-556f-ebbc93ba8f88'',
''domid'': ''4'',
''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'', ''
store/ring-ref'': ''878416'',
''store/port'': ''1''}
[2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices vif.
[2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 0.
[2006-04-13 16:59:22 xend] DEBUG (DevController:403)
hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2006-04-13 16:59:22 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices usb.
[2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices vbd.
[2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 2049.
[2006-04-13 16:59:22 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2049/hotplug-status.
[2006-04-13 16:59:22 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 2050.
[2006-04-13 16:59:22 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2050/hotplug-status.
[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2050/hotplug-status.
[2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2051.
[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2051/hotplug-status.
[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2051/hotplug-status.
[2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2052.
[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2052/hotplug-status.
[2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2053.
[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2053/hotplug-status.
[2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for devices pci.
[2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for
devices ioports.
[2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for devices vtpm.
[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 0.
[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
hotplugStatusCallback /local/domain/0/backend/vtpm/4/0/hotplug-status.
[2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-13 16:59:23 xend] INFO (XendDomain:360) Domain meta (4) unpaused.

xend-hotplug.log shows the following (with -x enabled):

+++ export PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin
+++ PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin
+++ export LANG=POSIX
+++ LANG=POSIX
++++ set
++++ grep ''^LC_''
++++ cut -d= -f1
+++ unset
+++ trap sigerr ERR
+++ log debug online XENBUS_PATH=backend/vif/4/0
+++ local level=debug
+++ shift
+++ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/4/0
++ . /etc/xen/scripts/xen-network-common.sh
+++ ''['' -e /etc/SuSE-release '']''
+++ which ifup
++ findCommand online
++ for arg in ''"$@"''
++ expr index online ++ command=online
++ return
++ ''['' online ''!='' online
'']''
++ case "$command" in
++ evalVariables online
++ for arg in ''"$@"''
++ expr index online = ''>'' 1
++ ip+++ xenstore_read_default backend/vif/4/0/ip ''''
+++ xenstore-read backend/vif/4/0/ip
+++ echo ''''
++ ip++ XENBUS_PATH=backend/vif/4/0
++ vif=vif4.0
+++ xenstore_read_default backend/vif/4/0/vifname ''''
+++ xenstore-read backend/vif/4/0/vifname
+++ echo ''''
++ vifname++ ''['' '''' '']''
+ bridge++ xenstore_read_default backend/vif/4/0/bridge ''''
++ xenstore-read backend/vif/4/0/bridge
+ bridge=xenbr0
+ ''['' -z xenbr0 '']''
+ case "$command" in
+ brctl show
+ grep -q vif4.0
+ brctl addif xenbr0 vif4.0
+ ifconfig vif4.0 up
+ handle_iptable
+ iptables -L -n
+ ''['' '''' ''!=''
'''' '']''
+ frob_iptable
+ ''['' online == online '']''
+ local c=-A
+ iptables -A FORWARD -m physdev --physdev-in vif4.0 -j ACCEPT
+ log debug ''Successful vif-bridge online for vif4.0, bridge
xenbr0.''
+ local level=debug
+ shift
+ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: ''Successful
vif-bridge online for vif4.0, bridge xenbr0.''
+ ''['' online == online '']''
+ success
+ xenstore_write backend/vif/4/0/hotplug-status connected
+ log debug ''Writing backend/vif/4/0/hotplug-status''
''connected to xenstore.''
+ local level=debug
+ shift
+ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: ''Writing
backend/vif/4/0/hotplug-status'' ''connected to
xenstore.''
+ xenstore-write backend/vif/4/0/hotplug-status connected

What am I missing?  Any help is appreciated.

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

Fong Vang

2006-Apr-13 17:46 UTC

head link

[Xen-users] Re: fedora core 5 and XEN networking issue

After searching for the past 1.5 days, I found the solution on the net.

In FC4, this seems to be automatic (at least the way the kernel was
built).  In FC5, the xennet module has to be loaded manually.

On 4/13/06, Fong Vang <sudoyang@gmail.com> wrote:> I''ve been using Xen on Fedora Core 4 without any problem. 
Recently, I
> upgraded (reinstalled from scratch) another Fedora Core 5 system. 
I''m
> having a difficult time getting a network interface configured for a
> domU.  This is my configure file:
>
>    kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
>    memory = 1024
>    name = "meta"
>    vif = [ '''' ]
> disk = [ ''phy:xenvg/metaboot,sda1,w'',
''phy:xenvg/metaroot,sda2,w'',
> ''phy:xenvg/   metausr,sda3,w'',
''phy:xenvg/metavar,sda4,w'',
> ''phy:xenvg/metaswap,sda5,w'' ]
>    vtpm = [ ''instance=1,backend=0'' ]
>    root = "/dev/sda2 ro"
>    extra = "3"
>
> I''ve also tried this line for the vif:
>
>    vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ]
>
> However, I''m still not able to get eth0 in domU to work.
>
> [root@meta ~]# ifconfig eth0 192.168.1.10 netmask 255.255.255.0
> SIOCSIFADDR: No such device
> eth0: unknown interface: No such device
> SIOCSIFNETMASK: No such device
> SIOCGIFADDR: No such device
> SIOCSIFBROADCAST: No such device
>
> I''m seeing this in xend.log:
>
> [2006-04-13 16:59:22 xend.XendDomainInfo] DEBUG (XendDomainInfo:667)
> Storing VM details: {''ssidref'': ''0'',
''uuid'':
> ''87c2f135-822b-13b6-556f-ebbc93ba8f88'', ''on
> _reboot'': ''restart'',
''start_time'': ''1144947562.33'',
''on_poweroff'':
> ''destroy'', ''name'':
''meta'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'':
> ''1024'', ''on_crash'':
> ''restart'', ''image'': "(linux
(kernel
> /boot/vmlinuz-2.6.16-1.2080_FC5xenU) (root ''/dev/sda2
ro'') (args 3))",
> ''maxmem'': ''1024''}
> [2006-04-13 16:59:22 xend.XendDomainInfo] DEBUG (XendDomainInfo:692)
> Storing domain details: {''console/ring-ref'':
''878415'', ''console/port'':
> ''2'', ''name'': ''met
> a'', ''console/limit'':
''1048576'', ''vm'':
> ''/vm/87c2f135-822b-13b6-556f-ebbc93ba8f88'',
''domid'': ''4'',
> ''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'', ''
> store/ring-ref'': ''878416'',
''store/port'': ''1''}
> [2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices
vif.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 0.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:403)
> hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:417) hotplugStatusCallback
1.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices
usb.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices
vbd.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 2049.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2049/hotplug-status.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:417) hotplugStatusCallback
1.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 2050.
> [2006-04-13 16:59:22 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2050/hotplug-status.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2050/hotplug-status.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback
1.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2051.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2051/hotplug-status.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2051/hotplug-status.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback
1.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2052.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2052/hotplug-status.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback
1.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2053.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:403)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/2053/hotplug-status.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback
1.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for devices
pci.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for
> devices ioports.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for devices
vtpm.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 0.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:403)
> hotplugStatusCallback /local/domain/0/backend/vtpm/4/0/hotplug-status.
> [2006-04-13 16:59:23 xend] DEBUG (DevController:417) hotplugStatusCallback
1.
> [2006-04-13 16:59:23 xend] INFO (XendDomain:360) Domain meta (4) unpaused.
>
> xend-hotplug.log shows the following (with -x enabled):
>
> +++ export PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin
> +++ PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin
> +++ export LANG=POSIX
> +++ LANG=POSIX
> ++++ set
> ++++ grep ''^LC_''
> ++++ cut -d= -f1
> +++ unset
> +++ trap sigerr ERR
> +++ log debug online XENBUS_PATH=backend/vif/4/0
> +++ local level=debug
> +++ shift
> +++ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: online
> XENBUS_PATH=backend/vif/4/0
> ++ . /etc/xen/scripts/xen-network-common.sh
> +++ ''['' -e /etc/SuSE-release '']''
> +++ which ifup
> ++ findCommand online
> ++ for arg in ''"$@"''
> ++ expr index online > ++ command=online
> ++ return
> ++ ''['' online ''!='' online
'']''
> ++ case "$command" in
> ++ evalVariables online
> ++ for arg in ''"$@"''
> ++ expr index online = ''>'' 1
> ++ ip> +++ xenstore_read_default backend/vif/4/0/ip ''''
> +++ xenstore-read backend/vif/4/0/ip
> +++ echo ''''
> ++ ip> ++ XENBUS_PATH=backend/vif/4/0
> ++ vif=vif4.0
> +++ xenstore_read_default backend/vif/4/0/vifname ''''
> +++ xenstore-read backend/vif/4/0/vifname
> +++ echo ''''
> ++ vifname> ++ ''['' ''''
'']''
> + bridge> ++ xenstore_read_default backend/vif/4/0/bridge
''''
> ++ xenstore-read backend/vif/4/0/bridge
> + bridge=xenbr0
> + ''['' -z xenbr0 '']''
> + case "$command" in
> + brctl show
> + grep -q vif4.0
> + brctl addif xenbr0 vif4.0
> + ifconfig vif4.0 up
> + handle_iptable
> + iptables -L -n
> + ''['' '''' ''!=''
'''' '']''
> + frob_iptable
> + ''['' online == online '']''
> + local c=-A
> + iptables -A FORWARD -m physdev --physdev-in vif4.0 -j ACCEPT
> + log debug ''Successful vif-bridge online for vif4.0, bridge
xenbr0.''
> + local level=debug
> + shift
> + logger -p daemon.debug -- /etc/xen/scripts/vif-bridge:
''Successful
> vif-bridge online for vif4.0, bridge xenbr0.''
> + ''['' online == online '']''
> + success
> + xenstore_write backend/vif/4/0/hotplug-status connected
> + log debug ''Writing backend/vif/4/0/hotplug-status''
''connected to xenstore.''
> + local level=debug
> + shift
> + logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: ''Writing
> backend/vif/4/0/hotplug-status'' ''connected to
xenstore.''
> + xenstore-write backend/vif/4/0/hotplug-status connected
>
> What am I missing?  Any help is appreciated.
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

James Bulpin

2006-Apr-14 13:40 UTC

head link

Re: [Xen-users] Re: fedora core 5 and XEN networking issue

Yes, the Fedora project chose to compile xennet as a module for FC5 
rather than into the kernel. Adding "alias eth0 xennet" to 
/etc/modprobe.conf should do the trick.

Fong Vang wrote:> After searching for the past 1.5 days, I found the solution on the net.
> 
> In FC4, this seems to be automatic (at least the way the kernel was
> built).  In FC5, the xennet module has to be loaded manually.
> 
> On 4/13/06, Fong Vang <sudoyang@gmail.com> wrote:
> 
>>I''ve been using Xen on Fedora Core 4 without any problem. 
Recently, I
>>upgraded (reinstalled from scratch) another Fedora Core 5 system. 
I''m
>>having a difficult time getting a network interface configured for a
>>domU.  This is my configure file:
>>
>>   kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
>>   memory = 1024
>>   name = "meta"
>>   vif = [ '''' ]
>>disk = [ ''phy:xenvg/metaboot,sda1,w'',
''phy:xenvg/metaroot,sda2,w'',
>>''phy:xenvg/   metausr,sda3,w'',
''phy:xenvg/metavar,sda4,w'',
>>''phy:xenvg/metaswap,sda5,w'' ]
>>   vtpm = [ ''instance=1,backend=0'' ]
>>   root = "/dev/sda2 ro"
>>   extra = "3"
>>
>>I''ve also tried this line for the vif:
>>
>>   vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ]
>>
>>However, I''m still not able to get eth0 in domU to work.
>>
>>[root@meta ~]# ifconfig eth0 192.168.1.10 netmask 255.255.255.0
>>SIOCSIFADDR: No such device
>>eth0: unknown interface: No such device
>>SIOCSIFNETMASK: No such device
>>SIOCGIFADDR: No such device
>>SIOCSIFBROADCAST: No such device
>>
>>I''m seeing this in xend.log:
>>
>>[2006-04-13 16:59:22 xend.XendDomainInfo] DEBUG (XendDomainInfo:667)
>>Storing VM details: {''ssidref'': ''0'',
''uuid'':
>>''87c2f135-822b-13b6-556f-ebbc93ba8f88'', ''on
>>_reboot'': ''restart'',
''start_time'': ''1144947562.33'',
''on_poweroff'':
>>''destroy'', ''name'':
''meta'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'':
>>''1024'', ''on_crash'':
>>''restart'', ''image'': "(linux
(kernel
>>/boot/vmlinuz-2.6.16-1.2080_FC5xenU) (root ''/dev/sda2
ro'') (args 3))",
>>''maxmem'': ''1024''}
>>[2006-04-13 16:59:22 xend.XendDomainInfo] DEBUG (XendDomainInfo:692)
>>Storing domain details: {''console/ring-ref'':
''878415'', ''console/port'':
>>''2'', ''name'': ''met
>>a'', ''console/limit'':
''1048576'', ''vm'':
>>''/vm/87c2f135-822b-13b6-556f-ebbc93ba8f88'',
''domid'': ''4'',
>>''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'', ''
>>store/ring-ref'': ''878416'',
''store/port'': ''1''}
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices
vif.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 0.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:403)
>>hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:417)
hotplugStatusCallback 1.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices
usb.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:132) Waiting for devices
vbd.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 2049.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:403)
>>hotplugStatusCallback
>>/local/domain/0/backend/vbd/4/2049/hotplug-status.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:417)
hotplugStatusCallback 1.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:138) Waiting for 2050.
>>[2006-04-13 16:59:22 xend] DEBUG (DevController:403)
>>hotplugStatusCallback
>>/local/domain/0/backend/vbd/4/2050/hotplug-status.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
>>hotplugStatusCallback
>>/local/domain/0/backend/vbd/4/2050/hotplug-status.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:417)
hotplugStatusCallback 1.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2051.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
>>hotplugStatusCallback
>>/local/domain/0/backend/vbd/4/2051/hotplug-status.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
>>hotplugStatusCallback
>>/local/domain/0/backend/vbd/4/2051/hotplug-status.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:417)
hotplugStatusCallback 1.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2052.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
>>hotplugStatusCallback
>>/local/domain/0/backend/vbd/4/2052/hotplug-status.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:417)
hotplugStatusCallback 1.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 2053.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
>>hotplugStatusCallback
>>/local/domain/0/backend/vbd/4/2053/hotplug-status.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:417)
hotplugStatusCallback 1.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for devices
pci.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for
>>devices ioports.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:132) Waiting for devices
vtpm.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:138) Waiting for 0.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:403)
>>hotplugStatusCallback /local/domain/0/backend/vtpm/4/0/hotplug-status.
>>[2006-04-13 16:59:23 xend] DEBUG (DevController:417)
hotplugStatusCallback 1.
>>[2006-04-13 16:59:23 xend] INFO (XendDomain:360) Domain meta (4)
unpaused.
>>
>>xend-hotplug.log shows the following (with -x enabled):
>>
>>+++ export
PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin
>>+++ PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin
>>+++ export LANG=POSIX
>>+++ LANG=POSIX
>>++++ set
>>++++ grep ''^LC_''
>>++++ cut -d= -f1
>>+++ unset
>>+++ trap sigerr ERR
>>+++ log debug online XENBUS_PATH=backend/vif/4/0
>>+++ local level=debug
>>+++ shift
>>+++ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: online
>>XENBUS_PATH=backend/vif/4/0
>>++ . /etc/xen/scripts/xen-network-common.sh
>>+++ ''['' -e /etc/SuSE-release '']''
>>+++ which ifup
>>++ findCommand online
>>++ for arg in ''"$@"''
>>++ expr index online >>++ command=online
>>++ return
>>++ ''['' online ''!='' online
'']''
>>++ case "$command" in
>>++ evalVariables online
>>++ for arg in ''"$@"''
>>++ expr index online = ''>'' 1
>>++ ip>>+++ xenstore_read_default backend/vif/4/0/ip
''''
>>+++ xenstore-read backend/vif/4/0/ip
>>+++ echo ''''
>>++ ip>>++ XENBUS_PATH=backend/vif/4/0
>>++ vif=vif4.0
>>+++ xenstore_read_default backend/vif/4/0/vifname ''''
>>+++ xenstore-read backend/vif/4/0/vifname
>>+++ echo ''''
>>++ vifname>>++ ''['' ''''
'']''
>>+ bridge>>++ xenstore_read_default backend/vif/4/0/bridge
''''
>>++ xenstore-read backend/vif/4/0/bridge
>>+ bridge=xenbr0
>>+ ''['' -z xenbr0 '']''
>>+ case "$command" in
>>+ brctl show
>>+ grep -q vif4.0
>>+ brctl addif xenbr0 vif4.0
>>+ ifconfig vif4.0 up
>>+ handle_iptable
>>+ iptables -L -n
>>+ ''['' '''' ''!=''
'''' '']''
>>+ frob_iptable
>>+ ''['' online == online '']''
>>+ local c=-A
>>+ iptables -A FORWARD -m physdev --physdev-in vif4.0 -j ACCEPT
>>+ log debug ''Successful vif-bridge online for vif4.0, bridge
xenbr0.''
>>+ local level=debug
>>+ shift
>>+ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge:
''Successful
>>vif-bridge online for vif4.0, bridge xenbr0.''
>>+ ''['' online == online '']''
>>+ success
>>+ xenstore_write backend/vif/4/0/hotplug-status connected
>>+ log debug ''Writing backend/vif/4/0/hotplug-status''
''connected to xenstore.''
>>+ local level=debug
>>+ shift
>>+ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge:
''Writing
>>backend/vif/4/0/hotplug-status'' ''connected to
xenstore.''
>>+ xenstore-write backend/vif/4/0/hotplug-status connected
>>
>>What am I missing?  Any help is appreciated.
>>
> 
> 
> _______________________________________________
> 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

Xen users - Apr 2006 - fedora core 5 and XEN networking issue

[Xen-users] fedora core 5 and XEN networking issue

[Xen-users] Re: fedora core 5 and XEN networking issue

Re: [Xen-users] Re: fedora core 5 and XEN networking issue