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: [PATCH 0/2] passthrough: make management of PCI D-states

To: Kouya Shimura <kouya@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 0/2] passthrough: make management of PCI D-states by guest optional
From: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>
Date: Thu, 23 Apr 2009 14:48:29 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Wed, 22 Apr 2009 22:49:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7kfxhrfcmv.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <7kfxhrfcmv.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 6 Mar 2009 14:23:20 +0900
Kouya Shimura <kouya@xxxxxxxxxxxxxx> wrote:

> Hi,
> 
> Using D3hot state of PCI devices in xen is not mature yet.
> I met domain destruction/creation troubles in some PCI cards since the
> PCI config registers can't be read with D3hot state. xend.log is attached.
> 
> This patch set makes the management of PCI D-states by guest optional.
> 
> The default is "pci_power_mgmt=0" which disables the guest OS from
> managing D-states because it would be better to avoid the trouble than
> advantage of low power consumption.
> 
> Thanks,
> Kouya
> 
> From xend.log:
> 
> [2009-03-04 09:49:24 4356] ERROR (XendDomainInfo:2584) 
> XendDomainInfo.destroy: domain destruction failed.
> Traceback (most recent call last):
>   File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 2578, in destroy
>     do_FLR(self.domid)
>   File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 314, in do_FLR
>     raise VmError("pci: failed to locate device and "+
> VmError: pci: failed to locate device and parse it's resources - ord() 
> expected a character, but string of length 0 found
> ...[snip]...
> [2009-03-04 10:31:24 4343] ERROR (XendDomainInfo:2445) 
> XendDomainInfo.initDomain: exception occurred
> Traceback (most recent call last):
>   File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 2437, in 
> _initDomain
>     self._createDevices()
>   File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 2049, in 
> _createDevices
>     devid = self._createDevice(devclass, config)
>   File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 2016, in 
> _createDevice
>     return self.getDeviceController(deviceClass).createDevice(devConfig)
>   File "/usr/lib64/python/xen/xend/server/DevController.py", line 67, in 
> createDevice
>     self.setupDevice(config)
>   File "/usr/lib64/python/xen/xend/server/pciif.py", line 399, in setupDevice
>     raise VmError("pci: failed to locate device and "+
> VmError: pci: failed to locate device and parse it's resources - ord() 
> expected a character, but string of length 0 found

Hi, Shimura-san

In my environment, I can't draw above error.

So could you test the following patches?

http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00829.html

I think your D-state problem is resolved with these patches.

Thanks,
--
Yuji Shimada


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

<Prev in Thread] Current Thread [Next in Thread>