On Thu, Mar 27, 2014 at 2:12 PM, Andreas Färber <afaer...@suse.de> wrote: >> Before this patch, the libqtest API could theoretically support multiple >> simultaneous instances of QTestState. This patch kills that option, >> doesn't it? > > Ouch, I thought I had looked out for that... > >> >> If yes: fine with me, we don't need it anyway. > > We do. Migration and ivshmem are examples that need two machines - might > explain why my ivshmem-test was behaving unexpectedly. > > Apart from reverting, what are our options?
Argh, I wasn't aware some tests run with two separate instances. We can implement more elaborate error handling, for example an atexit(3)-style atabort mechanism. This way, each instance can get its callback. Stefan