[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] no network interface device drivers

On Thu, 2014-01-09 at 15:16 +0100, awg1@xxxxxxx wrote:
> I've just moved my Dom0 from Fedora 19 to Centos 6.5 with the 3.12 kernel 
> (http://wiki.centos.org/HowTos/Xen/Xen4QuickStart).  I have a standard bridge 
> networking setup (external facing bridge to provide internet connectivity for 
> DomUs, and internal bridges for local networks).  From some reason, with the 
> CentOS setup, my DomUs can no longer connect to the external internet.  I've 
> done various trouble shooting exercises including removing and adding back 
> network interfaces, creating new DomUs, checking the logs, changing IPs but 
> no luck.  However I did notice this in the console output of a new machine I 
> was trying to create:
> [    1.246218] Mobile IPv6
> [    1.247110] NET: Registered protocol family 17
> [    1.248009] Registering the dns_resolver key type
> [    1.249084] registered taskstats version 1
> [    1.250029] XENBUS: Device with no driver: device/vbd/51712
> [    1.250986] XENBUS: Device with no driver: device/vif/0
> [    1.251933] XENBUS: Device with no driver: device/vif/1
> [    1.252877] /build/linux-rrsxby/linux-3.2.51/drivers/rtc/hctosys.c: unable 
> to open rtc device (rtc0)
> [    1.254630] Initializing network drop monitor service
> [    1.255851] Freeing unused kernel memory: 576k freed
> [    1.256916] Write protecting the kernel read-only data: 6144k
> [    1.260591] Freeing unused kernel memory: 652k freed
> [    1.261930] Freeing unused kernel memory: 688k freed
> [    1.323063] Initialising Xen virtual ethernet driver.
> From my reading, it seems the network interface is missing a driver
> which would, of course, explain my problems.  I checked the archives
> and the "XENBUS: Device with no driver" issue seems to have occurred
> back with xen 3.1 but I couldn't find much more about it since.
> Does anyone have any suggestions?

That message can be a red-herring, because what it can mean is "driver
module not loaded yet". From your logs it looks like the module is
subsequently loaded (last line) and I would expect this to trigger the
device getting created.

If you have eth0 and eth1 devices inside your guest (corresponding to
device/vif/{0,1}) then this is not your issue.

I'm afraid I don't have any other immediate thoughts.

There was a similar query on the list last night/this morning, you might
want to check the archives and see if there is any overlap.

It'd also be worth asking the CentOS folks and checking their bug
tracker in case this issue is known to them.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.