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

[Xen-devel] RE: What's the rationale for change d1efaaee441b "xend: Dis-allow device assignment if PoD is enabled."?


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • 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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.