On 3 August 2016 at 11:09, Andrew Cagney <[email protected]> wrote: > Perhaps it's related to the way the file systems are now created (see > earlier e-mail about clone). The disk images were set up with backing > store: > > swanfedorabase <- east, west .... > > but now there is an extra level vis: > > swanfedorabase <- clone <- east, west, .... > > For instance:
High and I have been exchanging large logs, and eventually noticed domains are becoming wedged, taking minutes to reboot vis: a.virsh road 3:32:16.02/3:23.03: domain failed to boot after 180.1 seconds, waiting 20 seconds for it to power down a.virsh road 3:32:36.03/3:43.04: domain failed to power down after 20.1 seconds, waiting 20 seconds for the power cord to be pulled a.virsh road 3:32:36.05/3:43.06: domain appears to have switched off after 0.2 seconds a.virsh road 3:32:36.05/3:43.06: starting domain a.virsh road 3:32:38.00/3:45.01: waiting 180 seconds for login prompt a.virsh road 3:32:51.07/3:58.08: login prompt appeared after 13.7 seconds a.virsh road 3:32:51.08/3:58.09: waiting 120 seconds for login prompt; 5 seconds for password prompt; 5 seconds for shell prompt a.virsh road 3:32:52.01/3:59.02: We're in after 0.3 seconds! a.runner newoe-25-cat-2 road 3:32:52.04/3:59.05: 'cd' to /testing/pluto/newoe-25-cat-2 b.virsh west 3:32:52.04/3:31.05: starting domain a.runner newoe-25-cat-2 3:32:52.04/3:59.05: stop booting domains after 239.6 seconds It happens ~100 times during Hugh's test run which, using a back of envelope calculation, seems sufficient to explain the multi-hour slow down. While this explains where the slow down is coming from, it doesn't explain why KVM becomes totally wedged :-( Andrew PS: it doesn't seem to be related to clones. _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
