Comment 10 for bug 1898871

Sorry, I didn't receive a reply to the original question:

Does VMWare provide guidance on editing OVF files outside of booting an image, making a change, and exporting?

What was provided was specific instructions for a single XML stanza. What we are worried about is making a change that isn't supported, while only having limited internal testing available. Having documentation available letting us know best practices and expected values for editing an OVMF _without first booting into VSphere_ is important.

our builds happen in a chroot environment, and are never booted. That's why understanding best practice and having documentation about what's supported and required is very helpful.

for VMHardware, for instance, is there a way to easily look up what is supported for that stanza? then we can make sure that when a version of ESXI is retired, we can properly up-rev the stanza.

As for prioritization, we will try and add this to the queue before EOY for the next release. We'll need community testing of those daily images before being able to backport a change through livecd-rootfs. The testing is important to ensure a wide variety of environments operate properly.