Comment 29 for bug 1643911

After slightly more than three days without crash of which almost exactly a day of pure cpu cycles were spent in libvirt I start to think that this won't trigger the bug as I hoped.

I deployed a new openstack and now have a loop running based on openstack start/stop (using 10x m1.small as I have slightly larger cloudimages ont cirros for now).
So this is more like your case just slightly enhanced by my time measurements - hope to trigger it on my end with this.

In the worst case after the weekend I'll have to fetch cirros and make nano instances to be even more similar.