On Mon, Feb 13, 2012 at 11:39 AM, Prateek Sharma wrote:
> On Mon, Feb 13, 2012 at 4:53 PM, Stefan Hajnoczi wrote:
>> On Sat, Feb 11, 2012 at 9:57 AM, Prateek Sharma
>> wrote:
>>> $QEMU -cpu core2duo,+vmx -drive file=$VM_PATH,if=virtio,aio=native
>>> -drive file=viotest.img,if=virtio,index=2
>
On 02/13/2012 05:23 AM, Stefan Hajnoczi wrote:
On Sat, Feb 11, 2012 at 9:57 AM, Prateek Sharma wrote:
$QEMU -cpu core2duo,+vmx -drive file=$VM_PATH,if=virtio,aio=native
-drive file=viotest.img,if=virtio,index=2
-drive cache=none is typically used for good performance when the
image is on a
On Mon, Feb 13, 2012 at 4:53 PM, Stefan Hajnoczi wrote:
> On Sat, Feb 11, 2012 at 9:57 AM, Prateek Sharma wrote:
>> $QEMU -cpu core2duo,+vmx -drive file=$VM_PATH,if=virtio,aio=native
>> -drive file=viotest.img,if=virtio,index=2
>
> -drive cache=none is typically used for good performance when t
On Sat, Feb 11, 2012 at 9:57 AM, Prateek Sharma wrote:
> $QEMU -cpu core2duo,+vmx -drive file=$VM_PATH,if=virtio,aio=native
> -drive file=viotest.img,if=virtio,index=2
-drive cache=none is typically used for good performance when the
image is on a local disk. Try that and I think you'll see an
Hello everyone,
I am testing virtio-blk throughput (single thread, using hdparm -tT
). I want to know what is the guest/baremetal sequential read ratio
with the current qemu / qemu-kvm builds.
I have tried with qemu 1.0, 0.15, 0.14.1 , but my guest throughput is
limited to 65 MB/s. Baremetal is
