From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:32958) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzRXY-0000hB-8c for qemu-devel@nongnu.org; Thu, 09 Aug 2012 08:08:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SzRXT-0004bC-W6 for qemu-devel@nongnu.org; Thu, 09 Aug 2012 08:08:36 -0400 Received: from mail.profihost.ag ([85.158.179.208]:34144) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzRXT-0004aw-Lu for qemu-devel@nongnu.org; Thu, 09 Aug 2012 08:08:31 -0400 Message-ID: <5023A83D.9070509@profihost.ag> Date: Thu, 09 Aug 2012 14:08:29 +0200 From: Stefan Priebe - Profihost AG MIME-Version: 1.0 References: <502283FA.2080506@profihost.ag> <5022912B.2000607@redhat.com> <50235527.4090804@profihost.ag> <50236059.7060801@redhat.com> <4A799203-5BFF-4DE9-9B85-459096EBEC22@profihost.ag> <50236484.2090702@redhat.com> <502369C7.7000300@profihost.ag> <50238E2A.1050203@profihost.ag> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] virtio-scsi vs. virtio-blk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Paolo Bonzini , qemu-devel 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 > 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 >