Description of problem: When you choose "Other OS" in the UI, you still get an option to configure cloud-init, but when you launch the VM it doesn't really do anything How reproducible: Always Steps to Reproduce: 1. Create a VM, with Other OS type 2. Set cloud-init properties 3. Run the VM (either via run or run-once. If using run-once set the cloud-init properties there). Actual results: Nothing happens with regards to cloud-init Expected results: When the option exist in the UI then it should pass it to the VM. So we should either decide to block it also for "Other OS", or pass it to the VM. Additional info: Didn't test other OS types.
I would suggest to pass the data to the vm (maybe ad a warning that you need cloud-init inside the vm), because other systems may rely on this function, e.g. *BSD variants. By not allowing this you would raise a high barrier for autoconfiguration of other vm os types.
basically there is no reason to use "Other OS", even for *BSD i would choose "Linux" but i agree we can send cloud init to "Other" as well, specially that we display the UI for the user..
(In reply to Omer Frenkel from comment #2) > basically there is no reason to use "Other OS", even for *BSD i would choose > "Linux" > but i agree we can send cloud init to "Other" as well, specially that we > display the UI for the user.. I'm okay with either "protecting" the user, and just not showing that in the UI for non-linux OS, or just show and send it, but I prefer the former.
the cloud init should be enable for non windows os for now
Verified in ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch (beta2). The config drive CD with cloud-init data is attached for all VMs with OS type different than Windows, i.e., currently for Debian, FreeBSD, Linux, OtherOS, RHEL, SUSE and Ubuntu.
oVirt 3.5 has been released and should include the fix for this issue.