On Sat, Feb 22, 2020 at 05:11:01AM -0600, Eric Blake wrote:
On 2/22/20 4:37 AM, Richard W.M. Jones wrote:
Another thing I've been thinking about for some time is splitting .config_complete into .config_complete + .get_ready (new name TBD). At the moment .config_complete is both the place where we finish processing config, and also the last chance we get to set things up before the server forks. Of course such a change would not be material — .get_ready would always be run immediately after .config_complete — but it cleans up the API a little.
How would it play with --dump-config? Right now, we allow that to run after .config but before .config_complete, precisely so that language bindings can accept the first .config to determine their script name, and then consult the script for any further config help.
I don't believe it affects it at all. Here are a couple of patches which show the general idea and pass all the tests. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/