Network start up in Xen 3.0

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Network start up in Xen 3.0

Nicholas Lee
Event-channel device installed.
xen_blk: Initialising virtual block device driver
vbd: probe of vbd-2050 failed with error -22
xen_blk: Timeout connecting to device!
xen_net: Initialising virtual ethernet driver.
vif: probe of vif-1 failed with error -22



I'm thinking that I'm missing something from the domU or dom0 kernel
config so the netbus is not being setup. Either that or a
configuration error due to the my lack of understanding on how 3.0
works.



In domU I have:

#
# XEN
#
# CONFIG_XEN_PRIVILEGED_GUEST is not set
# CONFIG_XEN_PHYSDEV_ACCESS is not set
# CONFIG_XEN_TPMDEV_FRONTEND is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
# CONFIG_XEN_BLKDEV_TAP is not set
# CONFIG_XEN_SHADOW_MODE is not set
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_XEN_X86 is not set
CONFIG_XEN_X86_64=y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y


dom0 I have:
#
# XEN
#
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PHYSDEV_ACCESS=y
CONFIG_XEN_BLKDEV_BACKEND=y
# CONFIG_XEN_BLKDEV_TAP_BE is not set
CONFIG_XEN_NETDEV_BACKEND=y
# CONFIG_XEN_TPMDEV_FRONTEND is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
# CONFIG_XEN_BLKDEV_TAP is not set
# CONFIG_XEN_SHADOW_MODE is not set
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_XEN_X86 is not set
CONFIG_XEN_X86_64=y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y


xen-config is quite simple:

kernel = "/boot/vmlinuz-2.6.12-xenU"
memory = 256
name = "breezy"
vcpus = 2
nics=1
vif = [ "mac=aa:00:00:88:02:40, bridge=xen-br0" ]
disk = [ 'phy:ww/breezy-fs,sda1,w', 'phy:ww/breezy-swap,sda2,w' ]

root = "/dev/sda1 ro"
extra = "4 lockd.udpport=32768 lockd.tcpport=32768"
restart = 'onreboot'

breezy is a ubuntu 32bit userland clean debootstrap to ubuntu-desktop
based system.

At least once the root device didn't initialise for some reason.
destroying and recreating seem to fix that one occasion.

However the network seems to refuse to start in the domU.

System is Sun v20z with SMP base dom0.
changeset:   7227:c344d6944d2f

nic@breezy:~$ /sbin/ifconfig -a
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:272 (272.0 b)  TX bytes:272 (272.0 b)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)



--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: Network start up in Xen 3.0

Ewan Mellor
On Tue, Oct 11, 2005 at 11:40:05PM +1300, Nicholas Lee wrote:

> Event-channel device installed.
> xen_blk: Initialising virtual block device driver
> vbd: probe of vbd-2050 failed with error -22
> xen_blk: Timeout connecting to device!
> xen_net: Initialising virtual ethernet driver.
> vif: probe of vif-1 failed with error -22

If this occurred on a changeset from the last couple of days, I would retry
with the current tree.  We have fixed bugs that would certainly have caused
this behaviour.

Ewan.

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel