All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lukáš Doktor" <ldoktor@redhat.com>
To: Lukas Doktor <ldoktor@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org,
	kvm-autotest@redhat.com, akong@redhat.com, lmr@redhat.com,
	jzupka@redhat.com
Subject: Re: [kvm-autotest] cgroup-kvm: Four new BlkioThrottle tests
Date: Fri, 07 Oct 2011 20:43:24 +0200	[thread overview]
Message-ID: <4E8F484C.1050706@redhat.com> (raw)
In-Reply-To: <1318011850-17580-1-git-send-email-ldoktor@redhat.com>

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.
>
> Also please beware of qemu-kvm bugs which occurred for me (qemu-kvm 0.15.0 F17) which led to qemu SEGFAULTS or even to dysfunction (qemu-kvm 0.14 F15). I'll fill in Bugzilla on Monday.
>
> This was also sent as a github pull request, so if you feel like commenting on the pull request, be my guest:
> https://github.com/autotest/autotest/pull/33
>
> Best regards,
> Lukáš
Already one minor change, please follow the patches on github...

diff --git a/client/tests/kvm/tests/cgroup.py 
b/client/tests/kvm/tests/cgroup.py
index 7f00a6b..7407e29 100644
--- a/client/tests/kvm/tests/cgroup.py
+++ b/client/tests/kvm/tests/cgroup.py
@@ -409,7 +409,13 @@ def run_cgroup(test, params, env):
                  raise error.TestError("Corrupt class, aren't you 
trying to run
                                        "parent _TestBlkioThrottle() 
function?")

-            (self.files, self.devices) = add_scsi_drive(self.vm)
+            if get_device_driver() == "ide":
+                logging.warn("The main disk for this VM is ide wich 
doesn't "
+                             "support hot-plug. Using virtio_blk instead")
+                (self.files, self.devices) = add_scsi_drive(self.vm,
+                                                            
driver="virtio")
+            else:
+                (self.files, self.devices) = add_scsi_drive(self.vm)
              try:
                  dev = utils.system_output("ls -l %s" % 
self.files).split()[4:6]
                  dev[0] = dev[0][:-1]    # Remove tailing ','


  parent reply	other threads:[~2011-10-07 18:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 18:24 [kvm-autotest] cgroup-kvm: Four new BlkioThrottle tests Lukas Doktor
2011-10-07 18:24 ` [PATCH 1/4] [kvm-autotest] cgroup-kvm: add_*_drive / rm_drive Lukas Doktor
2011-10-10 10:26   ` Jiri Zupka
2011-10-10 10:37     ` Lukáš Doktor
2011-10-11 17:13       ` Lucas Meneghel Rodrigues
2011-10-07 18:24 ` [PATCH 2/4] [autotest] cgroup: cleanup and structural changes Lukas Doktor
2011-10-07 18:24 ` [PATCH 3/4] [autotest] cgroup: {set,get}_property functions unification, bugfixies Lukas Doktor
2011-10-07 18:24 ` [PATCH 4/4] [kvm-autotest] cgroup-kvm: New subtest: TestBlkioThrottle* Lukas Doktor
2011-10-07 18:43 ` Lukáš Doktor [this message]
2011-10-11 20:30 ` [kvm-autotest] cgroup-kvm: Four new BlkioThrottle tests Lucas Meneghel Rodrigues

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E8F484C.1050706@redhat.com \
    --to=ldoktor@redhat.com \
    --cc=akong@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=jzupka@redhat.com \
    --cc=kvm-autotest@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.