-
-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow setting smbios for each VM (optional values) #451
Comments
Duplicates #353, but I'll keep them both for tracking. |
Not sure how I missed that thanks! |
@si458 Thanks for contributing bugs / enhancements! Really appreciated! Typos are sneaky, so a second pair of 👀 is really welcome, as well as any other suggestions regarding terraform API / namings / docs, etc, etc... |
Thanks @bpg |
eventually managed to get it working using ubuntu! built it locally with go then followed part of https://www.infracloud.io/blogs/developing-terraform-custom-provider/ for help where to place file etc! seems to work a treat with creating with ISO, i will try with clone a VM with an nocloud image HINT FOR OTHERS
|
OH NO it doesnt work with cloning?
CONFIG:
|
Oh... thanks! I didn't test this case, which seems quite obvious now 😅 |
@si458 this should be fixed now. |
thanks @bpg! just waiting a new release now 👍 |
Is your feature request related to a problem? Please describe.
when i clone a VM i created using the talos nocloud option, i need to set the smbios to a URL with confirmation already set
https://www.talos.dev/v1.4/talos-guides/install/cloud-platforms/nocloud/#smbios-proxmox
Describe the solution you'd like
to allow myself to set the smbios to certain values
this is already possible via the API GET and POST, values are base64 encoded
https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/qemu/{vmid}/config
Describe alternatives you've considered
create vm and set the smbios manually in the web panel of proxmox
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: