You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the error due to the embedded 'format=qcow2' in the create_params_qemu function in create_vm.rb. I suggest making the format another argument, rather than hardcoding it. I would submit a pull request, but I'm not a ruby guy and I have no idea how to even setup an environment for development.
According to the proxmox api viewer at http://pve.proxmox.com/pve-docs/api-viewer/index.html, the "sata" parameter supports a subparameter named "format" of type , but the actual enumeration values are not listed. From reading other things online, I infer the preferred format in this case should be "raw".
The text was updated successfully, but these errors were encountered:
denysvitali
pushed a commit
to denysvitali/vagrant-proxmox
that referenced
this issue
Sep 11, 2017
You may want to check out my branch, specifically the version 0.12+.
I've fixed the issue, you may need to add proxmox.qemu_storage = 'raw' once you have installed the new gem with vagrant plugin install vagrant-proxmox-0.0.12.gem
When attempting to create a VM against Proxmox 4.3 and Proxmox is configured with a ZFS filesystem the create operation fails with the message:
Here is an excerpt from my Vagrantfile
I believe the error due to the embedded 'format=qcow2' in the create_params_qemu function in create_vm.rb. I suggest making the format another argument, rather than hardcoding it. I would submit a pull request, but I'm not a ruby guy and I have no idea how to even setup an environment for development.
According to the proxmox api viewer at http://pve.proxmox.com/pve-docs/api-viewer/index.html, the "sata" parameter supports a subparameter named "format" of type , but the actual enumeration values are not listed. From reading other things online, I infer the preferred format in this case should be "raw".
The text was updated successfully, but these errors were encountered: