qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Barak Wasserstrom <wbarak@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>, Pawel Moll <pawel.moll@arm.com>
Subject: Re: [Qemu-devel] Using virtio-net and vhost_net on an ARM machine using qemu-system-arm & KVM
Date: Sun, 12 Jan 2014 23:49:58 +0200	[thread overview]
Message-ID: <CAKUxtu4xs4hfcnQaDvL1tbTkcF2fo+tnBecTW3Ek__Kg8BuUNw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9fEba1VGBzB2ORjbG+JsM-yX7WwcQyvmDn7goeJHfCeQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]

Peter,
Thanks - I got virtio-net-device running now, but performance is terrible.
When i look at the guest's ethernet interface features (ethtool -k eth0) i
see all offload features are disabled.
I'm using a virtual tap on the host (tap0 bridged to eth3).
On the tap i also see all offload features are disabled, while on br0 and
eth3 i see the expected offload features.
Can this explain the terrible performance i'm facing?
If so, how can this be changed?
If not, what else can cause such bad performance?
Do you know if vhost_net can be used on ARM Cortex A15 host/guest, even
though the guest doesn't support PCI & MSIX?

Regards,
Barak

On Sun, Jan 12, 2014 at 11:15 PM, Peter Maydell <peter.maydell@linaro.org>wrote:

> On 9 January 2014 12:25, Barak Wasserstrom <wbarak@gmail.com> wrote:
> > Hi,
> > I would like to utilize virtio-net and vhost_net on an ARM Cortex A15
> > machine using qemu-system-arm & KVM.
> > I have few questions:
> > 1. Do i need to build qemu-system-arm myself, or apt-get install it?
> When i
> > apt-get install it i get "KVM not supported for this target. "kvm"
> > accelerator does not exist. No accelerator found!".
>
> This sounds like either:
>  (1) you're using too old a version of QEMU and need a newer one
>  (2) you configured QEMU without KVM support
>
> Provided you have QEMU 1.6 or later it shouldn't matter whose
> version you're using.
>
> > 2. Do i need to execute qemu-system-arm directly or through virsh? Does
> it
> > matter?
>
> I know nothing about virsh but I don't expect it matters. It's
> probably easier to get things working by running qemu-system-arm
> directly first, before you try to work out how to get virsh to start
> qemu with the correct arguments.
>
> > 3. Must i use a machine that supports PCI controller or not? And if so,
> > which machine supports it? I saw that 'virt' and 'vexpress' don't support
> > it.
>
> No. For KVM to work you need to use an A15 guest CPU; there
> are no A15 boards in QEMU which have a PCI controller. So
> instead you have to use the vexpress-a15 or virt machine's
> virtio-mmio support. Note that generally the command line syntax
> for this is different from that used by x86: you need to create
> virtio-*-device devices, not virtio-* or virtio-*-pci devices, and you
> can't rely on shorthands like if=virtio. So for instance for a block
> device you need
>   -drive if=none,file=root,id=foo -device virtio-blk-device,drive=foo
>
> thanks
> -- PMM
>

[-- Attachment #2: Type: text/html, Size: 3253 bytes --]

  reply	other threads:[~2014-01-12 21:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 12:25 [Qemu-devel] Using virtio-net and vhost_net on an ARM machine using qemu-system-arm & KVM Barak Wasserstrom
2014-01-12 21:15 ` Peter Maydell
2014-01-12 21:49   ` Barak Wasserstrom [this message]
2014-01-12 22:00     ` Peter Maydell
2014-01-13  3:47       ` Ying-Shiuan Pan
2014-01-13 11:24         ` Barak Wasserstrom
2014-01-14  3:37           ` Ying-Shiuan Pan
2014-01-14 11:11             ` Barak Wasserstrom
2014-01-15  2:42               ` Ying-Shiuan Pan
2014-01-16  7:29                 ` Barak Wasserstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKUxtu4xs4hfcnQaDvL1tbTkcF2fo+tnBecTW3Ek__Kg8BuUNw@mail.gmail.com \
    --to=wbarak@gmail.com \
    --cc=pawel.moll@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).