)]}'
{"specs/newton/approved/virt-device-role-tagging.rst":[{"author":{"_account_id":16929,"name":"Giridhar Jayavelu","email":"gjayavelu@vmware.com","username":"gjayavelu"},"change_message_id":"2bc323ee4410e42f49e42e0616b423d13d4a26cb","unresolved":false,"context_lines":[{"line_number":163,"context_line":""},{"line_number":164,"context_line":".. code-block:: console"},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"   $ nova flavor-key m1.large set \"pci_passthrough:alias\"\u003d\"a1:2:mygpu\""},{"line_number":167,"context_line":"   $ nova boot \\"},{"line_number":168,"context_line":"       --image mywebappimage \\"},{"line_number":169,"context_line":"       --flavor m1.large \\"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9abb7d3a_bcf1a803","line":166,"updated":"2016-05-31 12:13:23.000000000","message":"one concern about passing tag along with alias information is that there is no granularity as --nic option mentioned above. i.e all pci devices of an alias will be tagged same. This does not provide user an option to use different pci device for different purposes.\n\nWhen booting instance with or without sr-iov devices, we have to pass --nic option, can we leverage the same to generate the pci metadata?","commit_id":"0727dc6f5c379089bbf393af701ad9b89b496175"}]}
