Re: [Qemu-devel] virtio-scsi vs. virtio-blk

[Stefan Priebe - Profihost AG]

sorry guys i mixed qemu vs. qemu-kvm. Network is now working fine.

but still virtio-scsi vs. virtio-blk:

virtio-scsi:
rand 4k:
  write: io=822448KB, bw=82228KB/s, iops=20557, runt= 10002msec
  read : io=950920KB, bw=94694KB/s, iops=23673, runt= 10042msec
seq:
  write: io=2436MB, bw=231312KB/s, iops=56, runt= 10784msec
  read : io=3248MB, bw=313799KB/s, iops=76, runt= 10599msec

virtio-blk:
rand 4k:
  write: io=896472KB, bw=89051KB/s, iops=22262, runt= 10067msec
  read : io=1710MB, bw=175073KB/s, iops=43768, runt= 10002msec
seq:
  write: io=4008MB, bw=391285KB/s, iops=95, runt= 10489msec
  read : io=5748MB, bw=570178KB/s, iops=139, runt= 10323msec

Stefan

Am 09.08.2012 13:04, schrieb Stefan Hajnoczi:
> On Thu, Aug 9, 2012 at 11:17 AM, Stefan Priebe - Profihost AG
> <address@hidden> wrote:
> > That looks better - thanks for the hint. But now network isn't working at
> > all ;-(
>
> You need to have commit 26b9b5fe17cc1b6be2e8bf8b9d16094f420bb8ad
> ("virtio: fix vhost handling").  Pull the latest qemu.git/master
> changes if you don't have it.
>
> Besides that recent vhost-net fix I'm not sure what the problem could
> be.  Your command-line looks sane.  Can you share errors messages or
> details on the failure?
>
> With tap the most common problem is permissions since the QEMU process
> needs to have access to the /dev/tap* device.
>
> Stefan