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

[Xen-devel] Errors on net and block drivers - my summary


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Murillo Bernardes <mfb@xxxxxxxxxx>
  • Date: Tue, 22 Nov 2005 18:47:32 -0200
  • Delivery-date: Tue, 22 Nov 2005 20:47:44 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi

Here is some errors I collected last days on net and block drivers.

1. Frontend directories are not been removed from store on 
{network,block}-detach. Makes xm {network,block}-list show closed devices.

2. Attach a block device after detach that does not work and does not report 
failure - Bug #420.

3. Frontend devices are not been unregistered on {network,block}-detach. 
Causes Bug #420.

4. If a domain die/crash/whatever all backend devices still on dom0.

5. xm {network,block}-{attach,dettach} does not check if operation was 
sucessfull on frontend. (ie. attach more than 3 vif fails, but xm 
network-attach does not report failure)

6. Attach more than 3 vif makes domU kernel OOPS. (probably 
drivers/xen/xenbus/xenbus_probe.c:307-308)

Time to go. Tomorrow I will work on this errors again, and probably file bug 
reports for all of them.

Thanks

-- 
Murillo Fernandes Bernardes
IBM Linux Technology Center

_______________________________________________
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®.