On Tue, 5 Mar 2019, 21:51 Cole Robinson, <[email protected]> wrote:
> > > Another piece to consider: the script is generated in a predictable path > ~/.cache/virt-manager/fedora.ks for example. It's not likely to happen > but two virt-install runs could overwrite each others scripts here. I'd > expect the generated filename to be sometime like tmpfile output. > > It wasn't clear to me how to actually ask libosinfo to write to a > different pathname though, and we would likely need to extend the initrd > inject logic to handle file rename before injection or something like > that. But it's worth considering > Worth knowing for us - we rebuild quite large sets of VMs in parallel using virt-install with a homebrewed unattended install. Ours sidesteps possible collisions as each script uses a directory based on the pid to assemble the relevant files. Peter > > Thanks, > Cole >
_______________________________________________ virt-tools-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-tools-list
