On Tue, 08/26 14:50, Stefan Hajnoczi wrote:
On Thu, Jun 05, 2014 at 04:47:46PM +0800, Fam Zheng wrote:
+def setUp(self):
+qemu_img('create', '-f', iotests.imgfmt, test_img, 1G)
+#self.vm = iotests.VM().add_drive(test_img, bps=1024,bps_max=1)
Commented out lines should
On Wed, Aug 27, 2014 at 02:19:44PM +0800, Fam Zheng wrote:
On Tue, 08/26 14:50, Stefan Hajnoczi wrote:
On Thu, Jun 05, 2014 at 04:47:46PM +0800, Fam Zheng wrote:
+result = self.vm.qmp(block_set_io_throttle, conv_keys=False,
**limits)
+self.assert_qmp(result, 'return',
On Thu, Jun 05, 2014 at 04:47:46PM +0800, Fam Zheng wrote:
+def setUp(self):
+qemu_img('create', '-f', iotests.imgfmt, test_img, 1G)
+#self.vm = iotests.VM().add_drive(test_img, bps=1024,bps_max=1)
Commented out lines should be dropped
+self.vm =
This case utilizes qemu-io command aio_{read,write} -a -q to verify
the effectiveness of IO throttling options.
The -a option will cause qemu-io requests to be accounted.
It's implemented by driving the vm timer from qtest protocol, so the
throttling timers are signaled with determinied time
