This way we'll have much more stress by doing more save/load
cycles during boot time. We did see some disk corruption problems
using this value, but the condition is not 100% reproducible.
Signed-off-by: Lucas Meneghel Rodrigues <l...@redhat.com>
---
client/tests/kvm/subtests.cfg.sample | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/client/tests/kvm/subtests.cfg.sample
b/client/tests/kvm/subtests.cfg.sample
index 03ddbe2..55f1b21 100644
--- a/client/tests/kvm/subtests.cfg.sample
+++ b/client/tests/kvm/subtests.cfg.sample
@@ -348,7 +348,7 @@ variants:
- boot_savevm: install setup image_copy unattended_install.cdrom
type = boot_savevm
savevm_delay = 0.3
- savevm_login_delay = 120
+ savevm_login_delay = 5
savevm_timeout = 2000
kill_vm_on_error = yes
kill_vm_gracefully = yes
--
1.7.7.3
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
