On Tue, Mar 12, 2013 at 08:44:21AM +0100, Lukáš Doktor wrote: > Dne 12.3.2013 06:11, Amos Kong napsal(a): > >Use a experienced reboot timeout 720. > > > >Signed-off-by: Amos Kong <[email protected]> > >--- > > qemu/tests/virtio_console.py | 4 ++-- > > 1 files changed, 2 insertions(+), 2 deletions(-) > > > >diff --git a/qemu/tests/virtio_console.py b/qemu/tests/virtio_console.py > >index 602ca0d..3ca328a 100644 > >--- a/qemu/tests/virtio_console.py > >+++ b/qemu/tests/virtio_console.py > >@@ -1781,7 +1781,7 @@ def run_virtio_console(test, params, env): > > try: > > vm.reboot(session=session, > > method=params.get('virtio_console_method', 'shell'), > >- timeout=360) > >+ timeout=720)
... > > Is this really required? The reboot takes 31s on my laptop (F17&F18guest). Sometimes 240s/360s is too short to reboot a (heavy-load, low-config, random issue) Windows guest. It's safe to use 720s for Windows guests. However, [PATCH 1/2] is necessary. We can only apply this patch when we touch login problem in virtio_console testing. Thanks, Amos _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
