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

Re: [Xen-devel] Re: [patch] netfront: unregister net device at backend_changed() if network_connect() failed


  • To: Joe Jin <joe.jin@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 20 Nov 2008 08:05:37 +0000
  • Cc: Xen-Devel <Xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 20 Nov 2008 00:05:59 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclK5sVPA98e6bbaEd2YZAAWy6hiGQ==
  • Thread-topic: [Xen-devel] Re: [patch] netfront: unregister net device at backend_changed() if network_connect() failed

On 20/11/08 02:53, "Joe Jin" <joe.jin@xxxxxxxxxx> wrote:

>> In this case, xend shouldn't be creating front and back directories at all.
>> What happens if you make netif's getDeviceDetails() return None for devid if
>> type == 'ioemu'? This should cause DevController.py not to set up the
>> front/back details and netfront.c will never get triggered.
>> 
> 
> The change could not stoped kernel insert xen_vnif driver.
> From xend.log I did not saw xend have tried to create vnif device at all,
> I'm not sure whether virtual device platform "Xen Platform Device" have
> preallocated the interface, then kernel try to load the driver?

If you really return None for devid from getDeviceDetails then it should be
impossible to get further in DevController.py:createDevice(). If you take a
look at the implementation it immediately returns in that case. So something
odd is going on. Perhaps your new patch does not work.

 -- Keir



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


 


Rackspace

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