-
Notifications
You must be signed in to change notification settings - Fork 70
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
Support and document how to create blank libvirt VMs #1748
Comments
@JunqiZhang0 Do you have the cycles to check this out and see if we support this use case? |
@ukalifon Hey Udi, is it something very urgent? Is it OK that I take look at it tomorrow? |
It can wait until tomorrow, thanks a lot ! |
@ukalifon So I tested yesterday, it seems linchpin can't do blank VM, but I can try adding this function by adding a ifesle statement, if you define the parameter blank_VM, linchpin will skip the VM turn on phase. What do you think? |
We can consider passing it in cloud_config like this:
This will keep the use case simple, so that blank_VM won't be required as an additional parameter. In any ways the user will still need to create a blank qcow2 image in advance and save it somewhere on the filesystem, then pass it like I did: I agree that blank_VM should completely skip the turning on of the VM. Thanks a lot for supporting this case! |
I am trying to use linchpin to create VMs with a blank harddisk. The VMs won't boot, except when a user will plug in a live cd. As a disk image, I am passing a url to a blank qcow image (that I prepared ahead of time with qemu-img create):
image_src: file:https:///tmp/blank-disk-132gb.qcow2
Linchpin still tried to run cloud-init, and to work around that I added:
But now it's failing on the ansible task waiting for the machine to get an IP... How can I create a blank VM and not even turn it on?
The text was updated successfully, but these errors were encountered: