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: What's the rationale for change d1efaaee441b "xend: Dis-

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] RE: What's the rationale for change d1efaaee441b "xend: Dis-allow device assignment if PoD is enabled."?
From: "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>
Date: Mon, 31 May 2010 14:01:04 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Sun, 30 May 2010 23:02:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C002F3B.8090603@xxxxxxxx>
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: <4C002F3B.8090603@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acr+qQADbWbAldjAQJqKm/8xiYl6RQB3Rsbw
Thread-topic: What's the rationale for change d1efaaee441b "xend: Dis-allow device assignment if PoD is enabled."?
Jeremy Fitzhardinge wrote:
> What's the rationale for changeset d1efaaee441b?  I'm seeing it when
> trying to attach a pci device to a PV domain with xm.  I think the
> check is triggering because the domain is ballooned down a bit, but
> I'm not sure (is there some way to see what the static and dynamic
> memory sizes are for a domain with the tools?).
> 
> As I understand it, PoD only applies to HVM domains.  Should this
> check be made more specific?

Yes, you are right. 
The POD check should be for HVM domain only. 
I submitted a patch in the attachment to fix this issue.

Thanks,
Dongxiao

> 
> Thanks,
>     J

Attachment: device-assign-pod.patch
Description: device-assign-pod.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>