1. ads Dimitri mentioned virtinst isn' recommended.
I use cloud images all day via as Dimitri outlined.
I do so via uvtool, but that also has a s390x issue (bug 1452016), but you can provide
the template I provide there.
From there you can use all you want and cloud-init your way as you need - Dimitri
already added a lot of great links, no need to requote them.
2. that does not mean I won't consider fixing virt-manager if the changes clearly apply
that is a fix worth to help you and others.
Just expect if you hit other things in virtinst that it might not be the most
used/tested/supported solution to achieve what you need.
3. Even if you are only interested in Xenial the SRU process defines to fix in currrent
dev release and from there SRU back.
Among other things that ensures that nobody encounters a regression on an update from
Xenial to something newer.
I'll get back once I got a review on my change, that is blocked on someting unrelated on virt-manager for now.
@Victor - three things:
1. ads Dimitri mentioned virtinst isn' recommended.
I use cloud images all day via as Dimitri outlined.
I do so via uvtool, but that also has a s390x issue (bug 1452016), but you can provide
the template I provide there.
From there you can use all you want and cloud-init your way as you need - Dimitri
already added a lot of great links, no need to requote them.
2. that does not mean I won't consider fixing virt-manager if the changes clearly apply tested/ supported solution to achieve what you need.
that is a fix worth to help you and others.
Just expect if you hit other things in virtinst that it might not be the most
used/
3. Even if you are only interested in Xenial the SRU process defines to fix in currrent
dev release and from there SRU back.
Among other things that ensures that nobody encounters a regression on an update from
Xenial to something newer.
I'll get back once I got a review on my change, that is blocked on someting unrelated on virt-manager for now.