WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: PCI-passthrough: After VM shutdown and start again, devi

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: [Xen-devel] Re: PCI-passthrough: After VM shutdown and start again, device has been assigned to another domain! Over-writting the ownership, but beware.
From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Date: Mon, 20 Sep 2010 22:32:46 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 20 Sep 2010 13:33:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100920201612.GA26085@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Eikelenboom IT services
References: <1882966220.20100914163633@xxxxxxxxxxxxxx> <20100920201612.GA26085@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Monday, September 20, 2010, 10:16:12 PM, you wrote:

> On Tue, Sep 14, 2010 at 04:36:33PM +0200, Sander Eikelenboom wrote:
>> Hello Konrad,
>> 
>> When i shutdown a VM with a pci device passed through, and after shutdown 
>> start it again, i get:
>> [  519.646961] pciback 0000:02:00.0: device has been assigned to another 
>> domain! Over-writting the ownership, but beware.
>> 
>> Which i don't get the first time, could this mean not everything is cleaned 
>> up ok after the shutdown ?

> Right. It means that somehow the frontend device didn't move to Closing' state
> for the specific device (look for 'state-X'). It should have been set by the 
> Xen
> tools to the appropiate value. Are you using 'xl' or the old 'xm'? Is this 
> the first
> time this has showed up?

I'm still using 'xm' in an attempt to not change really everything i do at once 
:-)

For what i recall, i have seen it before, but didn't pay to much attention to 
it.
Where do i have to look for the "state-X" ? Then I will check it out again.

>> 
>> --
>> Sander


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