Dne 12.3.2013 06:11, Amos Kong napsal(a):
Current vm.reboot() uses the default timeout(240), sometimes it's
too short for Windows guest.
Signed-off-by: Amos Kong <[email protected]>
---
qemu/tests/timedrift_with_reboot.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/qemu/tests/timedrift_with_reboot.py
b/qemu/tests/timedrift_with_reboot.py
index b40bb35..037924c 100644
--- a/qemu/tests/timedrift_with_reboot.py
+++ b/qemu/tests/timedrift_with_reboot.py
@@ -47,7 +47,7 @@ def run_timedrift_with_reboot(test, params, env):
# Run current iteration
logging.info("Rebooting: iteration %d of %d...",
(i + 1), reboot_iterations)
- session = vm.reboot(session)
+ session = vm.reboot(session, timeout=timeout)
# Get time after current iteration
(ht1_, gt1_) = utils_test.get_time(session, time_command,
time_filter_re,
time_format)
Oh I see, this is related to Windows guests. My windows XP guest never
rebooted so I based the virtio_console timeout on linux guest.
In case boot timeout is sufficient for reboot I agree with those patches.
Acked-by: Lukáš Doktor <[email protected]>
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
