Why do you want to use a control file and put the libhugetlbfs as a variant of autotest in kvm? Just keeping the kvm_hugepages variant will not serve the same purpose ? I have been using hugetlbfs variant for a long but yes without pre script(I have done that manually)? Am I missing something here? Rest all looks fine to me except you need somewhere s/enaugh/enough
2009/7/9 Lukáš Doktor <[email protected]>: > This patch adds kvm_hugepage variant. It prepares the host system and start > vm with -mem-path option. It does not clean after itself, because it's > impossible to unmount and free hugepages before all guests are destroyed. > > There is also added autotest.libhugetlbfs test. > > I need to ask you what to do with change of qemu parameter. Newest versions > are using -mempath insted of -mem-path. This is impossible to fix using > current config file. I can see 2 solutions: > 1) direct change in kvm_vm.py (parse output and try another param) > 2) detect qemu capabilities outside and create additional layer (better for > future occurrence) > > Tested by:[email protected] on RHEL5.4 with kvm-83-72.el5 > -- Sudhir Kumar -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
