Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Feature Request: Support for PCI Passthrough Devices #765

Closed
dcode opened this issue May 15, 2019 · 10 comments
Closed

Feature Request: Support for PCI Passthrough Devices #765

dcode opened this issue May 15, 2019 · 10 comments
Labels
enhancement Type: Enhancement

Comments

@dcode
Copy link

dcode commented May 15, 2019

Terraform Version

0.11.13

vSphere Provider Version

1.11.0

Affected Resource(s)

(probably)

  • vsphere_virtual_machine
  • vsphere_host
  • vsphere_host_pcipassthru (proposed new resource)

Terraform Configuration Files

N/A

Debug Output

N/A

Panic Output

N/A

Expected Behavior

Ability to associate a PCI device ID (which is a host resource) to a VM as a PCI passthrough object. This has to happen prior to power on. It also requires reserving all the VM memory.

Actual Behavior

After I run terraform apply I have to shutdown the VM and manually add the PCI device in vCenter.

Steps to Reproduce

Try to find in the documentation how to do a PCI passthrough in the vsphere provider and feel sad when you realize it doesn't exist.

Important Factoids

Obviously this isn't a super common use case, but it's something I need. In my case, I'm passing through a hardware NIC due to latency/performance reasons. The OpenStack provider features (linked in references) was developed for this same use case: latency.

References

@dcode dcode changed the title Support for PCI Passthrough Devices Feature Request: Support for PCI Passthrough Devices May 15, 2019
@bill-rich bill-rich added the enhancement Type: Enhancement label May 22, 2019
@dcode
Copy link
Author

dcode commented May 23, 2019

Additional note, it would be handy to be able to do a lookup on (vendor_id and device_id) OR system_id. Which is to say, lookup attributes of any available device of a specific device type (e.g. Intel X710 NIC, or nvidia GPU) or just select based on the bus address. This is what inherently happens in openstack because you associate a device whitelist with a vm flavor.

@sumitmaggo
Copy link
Contributor

@dcode Is there any update on this enhancement as to when will this be implemented?
Do you have any workaround as to how to add PCI device to VM through Terraform?

@dcode
Copy link
Author

dcode commented May 27, 2019

@sumitmaggo, I don't have a work around short of powering off the VM and adding it manually. I'm not a terraform developer. I filed this because I need this functionality.

@stobias123
Copy link

working on some new stuff with GRID gpus - PCI support would be greatly appreciated.

@mike-sol
Copy link

This would be very useful indeed, hope it can be added soon.

@hashibot
Copy link

This issue has been open 180 days with no activity. If this issue is reproducible with the latest version of the provider and with Terraform 0.12, please comment. Otherwise this issue will be closed in 30 days.

@hashibot hashibot added the stale Status: Stale label May 20, 2020
@onedr0p
Copy link

onedr0p commented May 20, 2020

Bump

@ghost ghost removed the stale Status: Stale label May 20, 2020
@bill-rich
Copy link
Contributor

This feature was added in #1099.

@ghost
Copy link

ghost commented Jul 9, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

1 similar comment
@ghost
Copy link

ghost commented Jul 9, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Jul 9, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
enhancement Type: Enhancement
Projects
None yet
Development

No branches or pull requests

7 participants