On 08/01/2014 05:33, Stefan Hajnoczi wrote:
On Mon, Jan 06, 2014 at 04:50:41PM +0100, Loic Dachary wrote:
On 06/01/2014 03:23, Stefan Hajnoczi wrote:
On Mon, Dec 30, 2013 at 01:33:34AM +0100, Loic Dachary wrote:
diff --git a/tests/qemu-iotests/common.rc b/tests/qemu-iotests/common.rc
Suppress rbd progress messages with --no-progress so they are not
confused with an error output when comparing test results ( progress is
displayed on stderr ).
Signed-off-by: Loic Dachary l...@dachary.org
---
tests/qemu-iotests/common.rc | 2 +-
1 file changed, 1 insertion(+), 1 deletion
On 06/01/2014 03:23, Stefan Hajnoczi wrote:
On Mon, Dec 30, 2013 at 01:33:34AM +0100, Loic Dachary wrote:
diff --git a/tests/qemu-iotests/common.rc b/tests/qemu-iotests/common.rc
index 28ba0d9..af66bbd 100644
--- a/tests/qemu-iotests/common.rc
+++ b/tests/qemu-iotests/common.rc
@@ -189,7
Stash the rbd stderr and stdout because it also contains human readable
progress messages : Removing image: 3% complete... in addition to
potential error messages.
Display the stashed output if rbd exits on error.
Signed-off-by: Loic Dachary l...@dachary.org
---
tests/qemu-iotests/common.rc | 6
according to your suggestion.
Cheers
On 30/12/2013 01:39, Benoît Canet wrote:
Le Monday 30 Dec 2013 à 01:33:34 (+0100), Loic Dachary a écrit :
Stash the rbd stderr and stdout because it also contains human readable
progress messages : Removing image: 3% complete... in addition to
potential error
Hi Stefan,
This is excellent ! Thank you very much :-)
Cheers
On 03/13/2013 04:21 PM, Stefan Hajnoczi wrote:
On Thu, Feb 21, 2013 at 9:11 AM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Mon, Feb 18, 2013 at 7:19 PM, Loic Dachary l...@dachary.org wrote:
I recently tried to figure out
Hi Stefan,
Thanks a lot, I'm looking forward to it ;-)
Cheers
On 02/21/2013 09:11 AM, Stefan Hajnoczi wrote:
On Mon, Feb 18, 2013 at 7:19 PM, Loic Dachary l...@dachary.org wrote:
I recently tried to figure out the best and easiest ways to increase block
I/O performances with qemu. Not being
Hi,
I recently tried to figure out the best and easiest ways to increase block I/O
performances with qemu. Not being a qemu expert, I expected to find a few
optimization tricks. Much to my surprise, it appears that there are many
significant improvements being worked on. This is excellent news
