But my questions was issue related image commit with "/opt/qemu/bin/qemu-img commit virtioa.qcow2" after 2nd reboot and it only seems to work on the 1st time/note when it runs and subsequent commit, does not work - see the error below. This behavior is very constant.

So my questions are as below and can you please answer the 2 questions to be clear:

1. Is this behavior present on Pro version and Community version?
2. Is there a solution to do this automatically, maybe via a script on Community edition?

sorry, but this is image preparation issue, or just your EVE CPU can’t handle this image.
It is heaviest qemu node as I know.
Please check your PM messages from me.
and if this will not work, then it is your HW issue, sorry...

One small trick was: After first boot when node crash, need simply stop it and then commit.
Then must be ok.
This heavy XRv9K node is really made by some wanker, sorry. They dont care if we are uing some low end servers. It requires top CPUs to run...
So please read my PM message and try then.

P.S. It is not related to EVE Community or Pro versions. Just need to have serious resource to run them.