[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1358789308.3279.271.camel@zakaz.uk.xensource.com>
Date: Mon, 21 Jan 2013 17:28:28 +0000
From: Ian Campbell <Ian.Campbell@...rix.com>
To: Yuval Shaia <yuval.shaia@...cle.com>
CC: "xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] Add support for netconsole driver used on bridge device
with VIF attached
On Mon, 2013-01-21 at 17:17 +0000, Yuval Shaia wrote:
> When starting a VM which has virtual interface attached to the same
> bridge (i.e vif = [type=netfront,bridge=xenbr0'] in vm.cfg) which is
> used for netconsole the
> following message appears (after about 60 seconds) and VM creation
> operation fails.
> Error: Device 0 (vif) could not be connected. Hotplug scripts not
> working.
I'm not sure how this can relate netconsole since this happens before
the guest even runs, doesn't it?
> As i see it, netconsole driver requires ndo_poll_controller from the
> device's controlling driver (function __netpoll_setup in
> net/core/netpoll.c), a thing that is not supported currently in
> xen_netback driver which is the driver that runs on dom0 and serve
> VM's virtual interface.
Which domain is using netconsole? Is it dom0 or domU? What parameters do
you give it?
I assume it is the domU but if that's the case I don't see why a netback
rather than netfront patch would be required.
Or is dom0 doing netconsole where the log receiver is a domU?
Ian.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists