Use get_block and other framework functions in cdrom test. Also
don't fail the whole test when tray-status reporting is not supported
by qemu and other cleanups.
Signed-off-by: Lukáš Doktor ldok...@redhat.com
---
client/tests/kvm/tests/cdrom.py | 118
I forgot add pull request link:
https://github.com/autotest/autotest/pull/368
Dne 30.5.2012 16:43, Lukáš Doktor napsal(a):
Use get_block and other framework functions in cdrom test. Also
don't fail the whole test when tray-status reporting is not supported
by qemu and other cleanups.
Signed
* fix another issues with symlinks and abs-paths
* detect the right cdrom device
* fix issue with locked cdrom (workaround not needed)
* improve comments and code-style (pylint)
Signed-off-by: Lukáš Doktor ldok...@redhat.com
---
client/tests/kvm/tests/cdrom.py | 151
fixes incorrect bus name for virtio_scsi cdroms.
Signed-off-by: Lukáš Doktor ldok...@redhat.com
---
client/virt/kvm_vm.py | 18 ++
1 files changed, 6 insertions(+), 12 deletions(-)
diff --git a/client/virt/kvm_vm.py b/client/virt/kvm_vm.py
index 19d016f..6bc1ae6 100644
fixes missing bus and port for usb2 cdroms.
Signed-off-by: Lukáš Doktor ldok...@redhat.com
---
client/virt/guest-hw.cfg.sample |2 ++
client/virt/kvm_vm.py | 12 +---
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/client/virt/guest-hw.cfg.sample b/client
Hi,
it caused problems so I had to modify it a bit. It's already fixed and
applied in upstream.
Regards,
Lukáš
Dne 12.3.2012 04:34, lei yang napsal(a):
Howerver, you did the opposite thing or you did it two times
commit 6e4b5cffe999714357116884fcc4eb27fae41260
Author: Lucas Meneghel
Yes, as I mentioned before, I wanted to put subtests.cfg after the other
imports, but it caused a lot of trouble. So I find another solution
without changing the import order.
Dne 12.3.2012 08:49, lei yang napsal(a):
On Mon, Mar 12, 2012 at 3:15 PM, Lukáš Doktorldok...@redhat.com wrote:
Hi,
Dne 3.11.2011 07:04, Suqin napsal(a):
On 09/23/2011 12:29 AM, Lukas Doktor wrote:
basic structure:
* similar to general client/tests/cgroup/ test (imports from the
cgroup_common.py)
* uses classes for better handling
* improved logging and error handling
* checks/repair the guests
I thought about that. But pci_add is not much stable and it's not
supported in QMP (as far as I read) with a note that this way is buggy
and should be rewritten completely. So I placed it here to let it
develop and then I can move it into utils.
Regards,
Lukáš
Dne 10.10.2011 12:26, Jiri
Dne 7.10.2011 20:24, Lukas Doktor napsal(a):
This is a patchset with four new tests to KVM specific cgroup testing. Also I
made some modifications into (general) cgroup_common library which makes cgroup
testing better readable and more safe to execute. Please find the details in
each patch.
Hi,
vm.screendump() doesn't have parameter 'debug'.
So you should either add debug parameter to kvm_vm.py or remove this
parameter (and perhaps add debug=False into kvm_vm.py).
Regards,
Lukáš
Dne 24.9.2011 01:27, Lucas Meneghel Rodrigues napsal(a):
In order to ease work with other
Dne 26.9.2011 15:10, Lucas Meneghel Rodrigues napsal(a):
On 09/26/2011 09:27 AM, Lukáš Doktor wrote:
Hi,
vm.screendump() doesn't have parameter 'debug'.
My fault, the screendump method on both qmp and human monitors does
take this parameter, and since the implementation on virt_env_process
Dne 23.9.2011 15:36, Lucas Meneghel Rodrigues napsal(a):
On 09/22/2011 01:29 PM, Lukas Doktor wrote:
Hi guys,
Do you remember the discussion about cgroup testing in autotest vs.
LTP? I hope there won't be any doubts about this one as ground_test
(+ first 2 subtests) are strictly focused on
Thanks, this patch works well.
Acked-by: Lukas Doktor ldok...@redhat.com
Dne 26.8.2011 10:31, Jiří Župka napsal(a):
This patch contain two tests.
1) Try kill guest when guest netwok is under loading.
2) Try kill guest after multiple adding and removing network drivers.
Signed-off-by: Jiří
Hi Jiří,
Do you have any further plans with this test? I'm not convinced that
netperf only as a stress is necessarily. You can use netcat or simple
python udp send/recv (flood attack ;-) ).
Dne 17.8.2011 16:17, Jiří Župka napsal(a):
This patch contain two tests.
1) Try kill guest when guest
#SNIP
+ pwd = item.mk_cgroup()
+ if pwd == None:
+ logging.error(test_memory: Can't create cgroup)
+ return -1
+
+ logging.debug(test_memory: Memory filling test)
+
+ f = open('/proc/meminfo','r')
Not clean way how to do this.. It is better to use regular expression.
But this is absolutely no
Reviewed, looks sane.
Lukáš
Dne 2.8.2011 05:39, Amos Kong napsal(a):
This test uses 'hdparm' to set disk device to low/high
performance status, and compare the reading speed.
The emulated device should pass all the tests.
Signed-off-by: Feng Yangfy...@redhat.com
Signed-off-by: Amos
Dne 23.11.2010 03:30, Amos Kong napsal(a):
- Jiří Župkajzu...@redhat.com wrote:
---
After loading your this patch, virtio_console also could not work with older
python.
Something are not fixed, such as:
return True if self.failed 0 else False
PASSif result[0] else FAIL
...
Dne 2.9.2010 04:58, Lucas Meneghel Rodrigues napsal(a):
From: Lukáš Doktorldok...@redhat.com
1) Starts VMs with the specified number of virtio console devices
2) Start smoke test
3) Start loopback test
4) Start performance test
This test uses an auxiliary script, console_switch.py, that is
Hi Amit,
Dne 23.8.2010 09:53, Amit Shah napsal(a):
On (Fri) Aug 20 2010 [16:12:51], Lukáš Doktor wrote:
Dne 20.8.2010 15:40, Lukas Doktor napsal(a):
Hi,
This patch adds new test for virtio_console. It supports booth, serialport and
console, virtio_console types and it contains three tests
Dne 20.8.2010 15:40, Lukas Doktor napsal(a):
Hi,
This patch adds new test for virtio_console. It supports booth, serialport and
console, virtio_console types and it contains three tests:
1) smoke
2) loopback
3) perf
Before any tests are executed it starts the machine with required number of
Hello ppl,
as we promised there is a new version with modifications you wanted us
to do. It's complete package based on the newest GIT version.
[Changelog]
- new structure (tests_base.cfg, ...)
- improved log
- function get_stat() raise an error when access death VM
- get_stat() splitted into
Dne 29.11.2009 17:17, Dor Laor napsal(a):
On 11/26/2009 12:11 PM, Lukáš Doktor wrote:
Hello Dor,
Thank you for your review. I have few questions about your comments:
--- snip ---
+ stat += Guests memsh = {
+ for vm in lvms:
+ if vm.is_dead():
+ logging.info(Trying to get
this in separate option in the
configuration file?
Best regards,
Lukáš Doktor
--
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
, I never doubted ksm for that. Actually it is good idea to
test...
We were asked to do so (be paranoid, everything could happened). We can
make this voluntary in the config.
Once again thanks, I'm looking forward to your replay.
Best regards,
Lukáš Doktor
--
To unsubscribe from this list
I'm sorry but thunderbird apparently crippled the path. Resending as the
attachment.
diff --git a/client/tests/kvm/allocator.c b/client/tests/kvm/allocator.c
new file mode 100644
index 000..89e8ce4
--- /dev/null
+++ b/client/tests/kvm/allocator.c
@@ -0,0 +1,571 @@
+/*
+ * KSM test program.
+
I'm sorry but thunderbird apparently crippled the path. Resending as the
attachment.
diff --git a/client/tests/kvm/kvm.py b/client/tests/kvm/kvm.py
index 4930e80..b9839df 100644
--- a/client/tests/kvm/kvm.py
+++ b/client/tests/kvm/kvm.py
@@ -53,6 +53,8 @@ class kvm(test.test):
This patch adds KSM test. We faced many difficulties which weren't
solvable by regular ways so please take a look and comment.
--
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
allocator.c is a program, which allocates pages in the memory and allow
us to fill or test those pages. It's controlled using sockets.
Signed-off-by: Lukáš Doktor ldok...@redhat.com
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/tests/kvm/allocator.c | 571
previous machines and let the actual machine finish the work.
Signed-off-by: Lukáš Doktor ldok...@redhat.com
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/tests/kvm/kvm.py |2 +
client/tests/kvm/kvm_tests.cfg.sample | 17 +
client/tests/kvm/kvm_tests.py | 548
Hello Ryan,
see below...
Dne 29.7.2009 16:41, Ryan Harper napsal(a):
* Lucas Meneghel Rodriguesl...@redhat.com [2009-07-28 22:40]:
This patch adds a small setup script to set up huge memory
pages during the kvm tests execution. Also, added hugepage setup to the
fc8_quick sample.
This adds an explanation of the 64 constant in vmsm equation.
diff --git a/client/tests/kvm/scripts/hugepage.py
b/client/tests/kvm/scripts/hugepage.py
index dc36da4..3828533 100644
--- a/client/tests/kvm/scripts/hugepage.py
+++ b/client/tests/kvm/scripts/hugepage.py
@@ -57,6 +57,7 @@ class
):
+self.set_hugepages()
+self.mount_hugepage_fs()
+
+
+if __name__ == __main__:
+if len(sys.argv) 2:
+huge_page = HugePage()
+else:
+huge_page = HugePage(sys.argv[1])
+
+huge_page.setup()
Acked-by: Lukáš Doktor ldok...@redhat.com
--
To unsubscribe from this list
Hello Lucas,
I like your patch but I'm not entirely convinced about it necessity.
Stable version of KVM should have this fixed and unstable ones are for
developers, who are skilled enough to fix this using kvm_test.cfg.
On the other hand keep this patch somewhere. Eventually if qemu started
Yes, this looks more pythonish and actually better than my version. I'm
missing only one thing, extra_params += -mem-path /mnt/hugepage down
in configuration (see below).
This cause problem with predefined mount point, because it needs to be
the same in extra_params and python script.
Dne
Well, thank you for notifications, I'll keep them in my mind.
Also the problem with mempath vs. mem-path is solved. It was just a
misspell in one version of KVM.
* fixed patch attached
Dne 20.7.2009 14:58, Lucas Meneghel Rodrigues napsal(a):
On Fri, 2009-07-10 at 12:01 +0200, Lukáš Doktor
true
regards,
Lukáš Doktor
In any case, the proposed solution does not allow the user to use
pre_command in the most straightforward way:
pre_command = command
because that would get translated into:
command true
So the user must append to the command, which makes little sense.
There could
I'm sorry this patch has a bug. hugepage variant doesn't allocate enough
memory with stress_boot (stress_boot uses different method to define VMS).
Attached the fixed patch.
Dne 9.7.2009 11:24, Lukáš Doktor napsal(a):
This patch adds kvm_hugepage variant. It prepares the host system and
start
(better
for future occurrence)
Dne 9.7.2009 11:24, Lukáš Doktor napsal(a):
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
After discussion I split the patches.
this patch adds autotest.libhugetlbfs test which tests hugepage support
inside of kvm guest.
Tested by:ldok...@redhat.com on RHEL5.4 with kvm-83-72.el5
Dne 9.7.2009 11:24, Lukáš Doktor napsal(a):
This patch adds kvm_hugepage variant. It prepares
:
pre_command += echo A
pre_command += echo B
pre_command += echo C
framework params.get(pre_command):
echo A echo B echo C
framework process_command execute on the host:
echo A echo B echo C true
regards,
Lukáš Doktor
diff -Narup kvm-autotest/client/tests/kvm/kvm_preprocessing.py
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
Set English environment before test executions.
This is critical because we are parsing outputs of commands, which are
localized!
Tested by: ldok...@redhat.com on RHEL5.4 with kvm-83-72.el5
--- orig/client/tests/kvm/control 2009-07-08 13:18:07.0 +0200
+++
Hi Michael,
actually it's necessarily. qemu-kvm only put this message into the
output and continue booting the guest without hugepage support. Autotest
than runs all the test. Later in the output is no mention about this.
You have to predict that this happend and look at debug output of all
44 matches
Mail list logo