-
Notifications
You must be signed in to change notification settings - Fork 35
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
cloud-init support #29
Comments
Thanks, I will take a closer look at it. |
You can use VirtualBox builtin provider as a reference I guess.. my Ruby foo is not that great so it's hard to say where to look exactly.. feel free to ask for testing and for cloud-init-related help. Roughly it's enough to add the following to QEMU call:
The ISO MUST have
Then |
Few more on how to get that working if/when support will be implemented:
Vagrant should be able to spin the VM up and to ssh into as Usually cloud-init output is visible on the VM console (serial console in this case). E.g. below is the output from my packer when everything is good. You can see the
If anything is wrong with the CD image you'll see some datasource-related error at early cloud-init stage. Feel free to contact me if need any help! |
It'd be great to have
cloud-init
experimental feature supported in the QEMU provider. Though it meansdisks
feature is required too (as cloud-init works this way for non-cloud VMs).This way it's possible to use e.g. Ubuntu and Debian cloud images unmodified.
Links:
The text was updated successfully, but these errors were encountered: