Although 52f94e55 is a laudable idea, the pattern "boot=on\|off" is nowhere to be found on RHEL 5 monitor output, making RHEL5 virtio guests to not boot. So, in addition of verifying the pattern, we should also verify if we passed image_boot_image1 = yes or similar in the config file, and if so, then set boot=on for that particular image.
Signed-off-by: Lucas Meneghel Rodrigues <[email protected]> --- client/virt/kvm_vm.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/client/virt/kvm_vm.py b/client/virt/kvm_vm.py index 4589475..566924d 100644 --- a/client/virt/kvm_vm.py +++ b/client/virt/kvm_vm.py @@ -550,7 +550,7 @@ class VM(virt_vm.BaseVM): cmd += _add_option("werror", werror) cmd += _add_option("serial", serial) cmd += _add_option("snapshot", snapshot, bool) - if has_option(help, "boot=on\|off"): + if has_option(help, "boot=on\|off") or boot in ['yes', 'on', True]: cmd += _add_option("boot", boot, bool) cmd += _add_option("id", name) cmd += _add_option("readonly", readonly, bool) -- 1.7.11.4 _______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
