Open Stack

I think it can be used as a capability of the host.

How do you think If regarding it as one type of the "HostSate", and return
it in the nova.scheduler.host_manager.HostManager:get_all_host_states
method ?


2014-03-26 11:09 GMT+08:00 Gouzongmei <gouzongmei at huawei.com>:

>  Hi, Yang, Yi y
>
>
>
> Agree with you,  IOMMU and SR-IOV need to be checked beforehand.
>
>
>
> I think it should be checked before booting a instance with the pci
> flavor, that means when the flavor contains some normal pci cards or SR-IOV
> cards. Just like when you find there are pci_requests in the instance
> system_metadata.
>
>
>
> The details are out of my current knows.
>
>
>
> Hope can help you.
>
> *From:* Yang, Yi Y [mailto:yi.y.yang at intel.com]
> *Sent:* Wednesday, March 26, 2014 10:51 AM
> *To:* openstack-dev at lists.openstack.org
> *Subject:* [openstack-dev] SR-IOV and IOMMU check
>
>
>
> Hi, all
>
>
>
> Currently openstack can support SR-IOV device pass-through (at least there
> are some patches for this), but the prerequisite to this is both IOMMU and
> SR-IOV must be enabled correctly, it seems there is not a robust way to
> check this in openstack, I have implemented a way to do this and hope it
> can be committed into upstream, this can help find the issue beforehand,
> instead of letting kvm report the issue "no IOMMU found" until the VM is
> started. I didn't find an appropriate place to put into this, do you think
> this is necessary? Where can it be put into? Welcome your advice and thank
> you in advance.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140326/f8c57591/attachment.html>