From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: xen crash related to pci passthrough Date: Thu, 27 May 2010 14:02:20 -0700 Message-ID: <4BFEDDDC.3060904@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen-devel , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 05/27/2010 01:02 PM, Keir Fraser wrote: > On 27/05/2010 20:51, "Jeremy Fitzhardinge" wrote: > > >> 3. attach device to PV domU >> dom0# xl pci-attach f13pv64 0000:03:00.0 >> 4. unbind from pciback >> dom0# echo 0000:03:00.0 > /sys/bus/pci/drivers/pciback/unbind >> 5. rmmod driver in domU >> domU# rmmod e1000e >> 6. Crash! >> >> The device in question is an Intel 82574L ethernet controller, using >> msi-x interrupts. >> > What happens if you pci-detach before unbinding from pciback? Not that Xen > should crash of course, but a crash resulting from a mistake in detach > ordring in dom0 would be less worrying than some alternatives. > Doing things in a more sensible order (rmmod in domU, detach, unbind) seems to work OK. I was deliberately seeing what would happen if I tried pulling the device out from under a domain. J