Hi,
Ive build a Dom0 4.1.2 running on CentOS 6.3.
The system boots fine and I network activity.
Im trying to boot a domU but am getting the above error then after it
has counted down waiting I get
XENBUS: Timeout connecting to device: device/vif/0 (local state 1,
remote state 1)
My bridge exists
Brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.001aa01663d7 no eth0
my domu config is
# -*- mode: python; -*-
kernel = "/boot/vmlinuz-2.6.18.8-xen"
memory = 1024
name = "srvmanager"
vif = [''bridge=xenbr0'' ]
disk
[''phy:/dev/XEN/srvmanager,hda1,w'',''phy:/dev/XEN/srvmanagerswap,sda2,w'']
root = "/dev/hda1 ro"
extra = "3 xencons=tty"
vcpus = 2
ifconfig -a shows (with domu running)
eth0 Link encap:Ethernet HWaddr 00:1A:A0:16:63:D7
inet6 addr: fe80::21a:a0ff:fe16:63d7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15281 errors:0 dropped:16 overruns:0 frame:0
TX packets:453 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1307318 (1.2 MiB) TX bytes:69446 (67.8 KiB)
Interrupt:16 Memory:f8000000-f8012800
eth1 Link encap:Ethernet HWaddr 00:1A:A0:16:63:D9
BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Memory:f4000000-f4012800
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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:144 (144.0 b) TX bytes:144 (144.0 b)
xenbr0 Link encap:Ethernet HWaddr 00:1A:A0:16:63:D7
inet addr:172.20.1.73 Bcast:172.20.255.255 Mask:255.255.0.0
inet6 addr: fe80::21a:a0ff:fe16:63d7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15019 errors:0 dropped:5772 overruns:0 frame:0
TX packets:439 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1020104 (996.1 KiB) TX bytes:66034 (64.4 KiB)
Any ideas ?
Thanks
Ian
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
On Tue, 2012-07-17 at 15:49 +0100, Ian Tobin wrote:> XENBUS: Timeout connecting to device: device/vif/0 (local state 1, > remote state 1)> ifconfig –a shows (with domu running)There doesn't seem to be any vifX.Y in there -- perhaps you don't have the netback driver loaded or compiled into your kernel?> kernel = "/boot/vmlinuz-2.6.18.8-xen"Why so ancient? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Ian, How would I tell this? I selected all options when compiling as static. The kernel for DomU is just a test, ive tried kernels up to 3.4.5 and still not working. BTW ive rebuilt the main host twice with the same problem. Thanks Ian -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: 17 July 2012 15:59 To: Ian Tobin Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: On Tue, 2012-07-17 at 15:49 +0100, Ian Tobin wrote:> XENBUS: Timeout connecting to device: device/vif/0 (local state 1, > remote state 1)> ifconfig –a shows (with domu running)There doesn't seem to be any vifX.Y in there -- perhaps you don't have the netback driver loaded or compiled into your kernel?> kernel = "/boot/vmlinuz-2.6.18.8-xen"Why so ancient? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Attaching your .cofig would be a good start. On a modern kernel /sys/bus/xen-backend should contain "vif", YMMV under other kernels, but there ought to be some indication under /sys that netback exists. On Tue, 2012-07-17 at 16:01 +0100, Ian Tobin wrote:> Ian, > > How would I tell this? I selected all options when compiling as static. > > The kernel for DomU is just a test, ive tried kernels up to 3.4.5 and still not working. > > BTW ive rebuilt the main host twice with the same problem. > > Thanks > > Ian > > -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: 17 July 2012 15:59 > To: Ian Tobin > Cc: xen-users@lists.xen.org > Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: > > On Tue, 2012-07-17 at 15:49 +0100, Ian Tobin wrote: > > XENBUS: Timeout connecting to device: device/vif/0 (local state 1, > > remote state 1) > > > ifconfig –a shows (with domu running) > > There doesn't seem to be any vifX.Y in there -- perhaps you don't have the netback driver loaded or compiled into your kernel? > > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > > Why so ancient? > > Ian. > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Ok will attach it shortly Thanks Tidyhosts UK - Server & Web Specialists W: www.tidyhosts.com E: enquiries@tidyhosts.com T: 0871 910 6732 This email and its attachments are scanned by TidyHosts UK. All emails and attachments should also be scanned by the recipient. TidyHosts UK accept no responsibility for any damage caused by any virus attached to this email. This email is confidential and is intended only for the addressee(s). On 17 Jul 2012, at 16:11, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:> Attaching your .cofig would be a good start. > > On a modern kernel /sys/bus/xen-backend should contain "vif", YMMV under > other kernels, but there ought to be some indication under /sys that > netback exists. > > On Tue, 2012-07-17 at 16:01 +0100, Ian Tobin wrote: >> Ian, >> >> How would I tell this? I selected all options when compiling as static. >> >> The kernel for DomU is just a test, ive tried kernels up to 3.4.5 and still not working. >> >> BTW ive rebuilt the main host twice with the same problem. >> >> Thanks >> >> Ian >> >> -----Original Message----- >> From: Ian Campbell [mailto:Ian.Campbell@citrix.com] >> Sent: 17 July 2012 15:59 >> To: Ian Tobin >> Cc: xen-users@lists.xen.org >> Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: >> >> On Tue, 2012-07-17 at 15:49 +0100, Ian Tobin wrote: >>> XENBUS: Timeout connecting to device: device/vif/0 (local state 1, >>> remote state 1) >> >>> ifconfig –a shows (with domu running) >> >> There doesn't seem to be any vifX.Y in there -- perhaps you don't have the netback driver loaded or compiled into your kernel? >> >>> kernel = "/boot/vmlinuz-2.6.18.8-xen" >> >> Why so ancient? >> >> Ian. >> >> >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Ian, See attached Thanks Ian -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: 17 July 2012 16:11 To: Ian Tobin Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: Attaching your .cofig would be a good start. On a modern kernel /sys/bus/xen-backend should contain "vif", YMMV under other kernels, but there ought to be some indication under /sys that netback exists. On Tue, 2012-07-17 at 16:01 +0100, Ian Tobin wrote:> Ian, > > How would I tell this? I selected all options when compiling as static. > > The kernel for DomU is just a test, ive tried kernels up to 3.4.5 and still not working. > > BTW ive rebuilt the main host twice with the same problem. > > Thanks > > Ian > > -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: 17 July 2012 15:59 > To: Ian Tobin > Cc: xen-users@lists.xen.org > Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: > > On Tue, 2012-07-17 at 15:49 +0100, Ian Tobin wrote: > > XENBUS: Timeout connecting to device: device/vif/0 (local state 1, > > remote state 1) > > > ifconfig –a shows (with domu running) > > There doesn't seem to be any vifX.Y in there -- perhaps you don't have the netback driver loaded or compiled into your kernel? > > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > > Why so ancient? > > Ian. > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
---- On a modern kernel /sys/bus/xen-backend should contain "vif", YMMV under other kernels, but there ought to be some indication under /sys that netback exists.------ Interestingly I cant see anything relating to this in that directory -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: 17 July 2012 16:11 To: Ian Tobin Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: Attaching your .cofig would be a good start. On a modern kernel /sys/bus/xen-backend should contain "vif", YMMV under other kernels, but there ought to be some indication under /sys that netback exists. On Tue, 2012-07-17 at 16:01 +0100, Ian Tobin wrote:> Ian, > > How would I tell this? I selected all options when compiling as static. > > The kernel for DomU is just a test, ive tried kernels up to 3.4.5 and still not working. > > BTW ive rebuilt the main host twice with the same problem. > > Thanks > > Ian > > -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: 17 July 2012 15:59 > To: Ian Tobin > Cc: xen-users@lists.xen.org > Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: > > On Tue, 2012-07-17 at 15:49 +0100, Ian Tobin wrote: > > XENBUS: Timeout connecting to device: device/vif/0 (local state 1, > > remote state 1) > > > ifconfig –a shows (with domu running) > > There doesn't seem to be any vifX.Y in there -- perhaps you don't have the netback driver loaded or compiled into your kernel? > > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > > Why so ancient? > > Ian. > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, 2012-07-17 at 18:50 +0100, Ian Tobin wrote:> ---- On a modern kernel /sys/bus/xen-backend should contain "vif", YMMV under other kernels, but there ought to be some indication under /sys that netback exists.------ > > Interestingly I cant see anything relating to this in that directory >From your config: # CONFIG_XEN_NETDEV_BACKEND is not set You could''ve checked this yourself when I asked. Ian.
Ian, I had set that but realised I had set it in the wrong place and noticed before you replied doh! Ive manually edited the config file and have recompiled which is now working so thanks for pointing that out. Just out of interest, where is that option in the GUI? Thanks Ian -----Original Message----- From: Ian Campbell [mailto:Ian.Campbell@citrix.com] Sent: 17 July 2012 21:18 To: Ian Tobin Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: On Tue, 2012-07-17 at 18:50 +0100, Ian Tobin wrote:> ---- On a modern kernel /sys/bus/xen-backend should contain "vif",YMMV under other kernels, but there ought to be some indication under /sys that netback exists.------> > Interestingly I cant see anything relating to this in that directory >From your config: # CONFIG_XEN_NETDEV_BACKEND is not set You could''ve checked this yourself when I asked. Ian.
On Tue, 2012-07-17 at 21:30 +0100, Ian Tobin wrote:> Ian, > > I had set that but realised I had set it in the wrong place and noticed > before you replied doh! > > Ive manually edited the config file and have recompiled which is now > working so thanks for pointing that out. > > Just out of interest, where is that option in the GUI?I''ve no idea. At least in the text UI you can press ''/'' and entry a name (or part of one) and it''ll tell you some details, including the path through the menus to find it. Ian.> > Thanks > > Ian > > -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: 17 July 2012 21:18 > To: Ian Tobin > Cc: xen-users@lists.xen.org > Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: > > On Tue, 2012-07-17 at 18:50 +0100, Ian Tobin wrote: > > ---- On a modern kernel /sys/bus/xen-backend should contain "vif", > YMMV under other kernels, but there ought to be some indication under > /sys that netback exists.------ > > > > Interestingly I cant see anything relating to this in that directory > > > > From your config: > # CONFIG_XEN_NETDEV_BACKEND is not set > > You could''ve checked this yourself when I asked. > > Ian. > > > >
Ok I''ll make some notes. On Debian it seems to be enabled by default so not had this issue before. Thanks Ian On 17 Jul 2012, at 21:54, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:> On Tue, 2012-07-17 at 21:30 +0100, Ian Tobin wrote: >> Ian, >> >> I had set that but realised I had set it in the wrong place and noticed >> before you replied doh! >> >> Ive manually edited the config file and have recompiled which is now >> working so thanks for pointing that out. >> >> Just out of interest, where is that option in the GUI? > > I''ve no idea. > > At least in the text UI you can press ''/'' and entry a name (or part of > one) and it''ll tell you some details, including the path through the > menus to find it. > > Ian. > >> >> Thanks >> >> Ian >> >> -----Original Message----- >> From: Ian Campbell [mailto:Ian.Campbell@citrix.com] >> Sent: 17 July 2012 21:18 >> To: Ian Tobin >> Cc: xen-users@lists.xen.org >> Subject: Re: [Xen-users] XENBUS: Waiting for devices to initialise: >> >> On Tue, 2012-07-17 at 18:50 +0100, Ian Tobin wrote: >>> ---- On a modern kernel /sys/bus/xen-backend should contain "vif", >> YMMV under other kernels, but there ought to be some indication under >> /sys that netback exists.------ >>> >>> Interestingly I cant see anything relating to this in that directory >>> >> >> From your config: >> # CONFIG_XEN_NETDEV_BACKEND is not set >> >> You could''ve checked this yourself when I asked. >> >> Ian. >> >> >> >> > > >