- kvm_hugepages variant enables us to test if (host) kvm use of
hugepages works
- libhugetlbfs test inside of guest prove, that (guest) system is able
to handle hugepages (independently of whether guest uses hugepages).
This function is necessarily eg. if you want to run Oracle server inside
the guest.
So basically this are 2 independent things, but somehow connected. If
you want I can split the patches.
Dne 10.7.2009 06:38, sudhir kumar napsal(a):
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<ldoktor@xxxxxxxxxx>:
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:ldoktor@xxxxxxxxxx on RHEL5.4 with kvm-83-72.el5
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
