Hi Chris, Indeed, the ISO domains are deprecated, and you can use a data domain for uploading iso files (as you've mentioned). To do that, you need to use image-io for uploading images <https://www.ovirt.org/develop/release-management/features/storage/image-upload.html> Here's image-io documentation: http://ovirt.github.io/ovirt-imageio/overview.html. Then you can use the UI (admin portal) or REST API <http://ovirt.github.io/ovirt-engine-api-model/master/#services/image_transfer> for uploading the iso image to the relevant storage domain. *Regards,* *Shani Leviim* On Mon, Jul 26, 2021 at 8:56 PM Chris Adams <cma@cmadams.net> wrote:
I was looking at using direct Linux kernel/initrd booting for a particular automation project, but I'm not sure how to use it. The docs talk about referencing files from an ISO domain, but those are deprecated (and I don't have one). Can the files be in a regular data domain? How would I specify which domain to look in?
The docs also say the alternative is to specify a path "on the host", but I guess that requires the files to be copied to the same path on every host that could boot the VM?
I guess I can instead make a one-off ISO and upload it to a data domain; it just would be easier to use direct boot. -- Chris Adams <cma@cmadams.net> _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IDIDY6ZLZCRMVM...