@sid It seems I have to get my hands dirty and take a deeper look into Terraform / OpenTofu. I am not shure how well the other folks at work partially will have fun working with commandline versus the easy to use XO web GUI.
Tailoring down the CloudInit files used is not really the basic idea behind this. I was rather going the oposite way and install / configure the stuff we usually bake into our templates on the fly while generating the VM via CloudInit.
Thanks a lot for all the responses !
Hi!
The new standard way to import is here: https://xen-orchestra.com/#!/xoa
Let me know if you have any issue. It's still in beta yet, and we got one small issue to fix (it won't fetch the XO username/password, so it's still admin@admin.net / admin)
That's normal. If you boot the replicated VMs, then blocks will be changed. It mean no further delta replication will work on this VM. Force boot it if you lost the original VM and you don't care about delta toward the copy anymore. If you just want to test the VM without doing a new full (breaking the delta chain), boot with a copy. I think I explained that in this video: https://www.youtube.com/watch?v=FfUqIwT8KzI
That's a display glitch.
In case someone ran into the same problem here is how I solved it.
I had a feeling this was http mounts issue. I checked and looks like during update process the .xo-server.toml got deleted. I copied the sample one from the /opt/xen-orchestra/packages/xo-server/sample.config.toml , edited the http.mount and bob's your uncle.
I have a feeling this has something to do with the format of that file change. When I originally built from source the file has a slightly different syntax and it was called .xo-server.yaml. At least according tot he directions I used to build. In any case its all back to normal now.
Thanks you everyone for your help.
Thanks, this way we'll have a way to understand what's wrong with this OVA, if it's something really specific or a VMWare way to make something we didn't expected
