From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-2?Q?Luk=E1=B9_Doktor?= Subject: Re: [KVM_AUTOTEST] add kvm hugepage variant and test Date: Fri, 10 Jul 2009 08:48:26 +0200 Message-ID: <4A56E43A.5060609@redhat.com> References: <4A55B759.5080302@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: KVM list , Jason Wang To: sudhir kumar Return-path: Received: from mx2.redhat.com ([66.187.237.31]:48655 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750743AbZGJGsc (ORCPT ); Fri, 10 Jul 2009 02:48:32 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: - kvm_hugepages variant enables us to test if (host) kvm use of=20 hugepages works - libhugetlbfs test inside of guest prove, that (guest) system is able=20 to handle hugepages (independently of whether guest uses hugepages).=20 This function is necessarily eg. if you want to run Oracle server insid= e=20 the guest. So basically this are 2 independent things, but somehow connected. If=20 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=E1=B9 Doktor: >> This patch adds kvm_hugepage variant. It prepares the host system an= d 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 destr= oyed. >> >> There is also added autotest.libhugetlbfs test. >> >> I need to ask you what to do with change of qemu parameter. Newest v= ersions >> are using -mempath insted of -mem-path. This is impossible to fix us= ing >> 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 (bet= ter for >> future occurrence) >> >> Tested by:ldoktor@redhat.com on RHEL5.4 with kvm-83-72.el5 >> > > >