From: Paolo Bonzini <pbonzini@redhat.com>
To: Naor Shlomo <NaorS@Radware.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
libvirt-users <libvirt-users@redhat.com>
Subject: Re: Multi Queue KVM Support
Date: Tue, 20 Aug 2013 14:12:32 +0200 [thread overview]
Message-ID: <52135D30.1050709@redhat.com> (raw)
In-Reply-To: <58539BF287296F4CB5EC3FF6E0639E07FBDC42@ILMB2.corp.radware.com>
Il 20/08/2013 13:13, Naor Shlomo ha scritto:
> Hi Paolo and thanks for your help.
>
> I upgraded the following (compiled from source)
> qemu : 1.5.2 stable
> libvirt : 1.1.1
>
> but for some reason when I run the version command inside virsh:
>
> Compiled against library: libvirt 1.1.1
> Using library: libvirt 1.1.1
> Using API: QEMU 1.1.1
> Running hypervisor: QEMU 0.12.1
>
> It says that my running Hypervisor is QEMU 0.12.1
>
> Could you please tell me what did I miss, how do I upgrade the hypervisor?
Not sure. Adding the libvirt-users mailing list.
> Thanks,
> Naor
>
> -----Original Message-----
> From: Paolo Bonzini [mailto:paolo.bonzini@gmail.com] On Behalf Of Paolo Bonzini
> Sent: Tuesday, August 20, 2013 12:28 PM
> To: Naor Shlomo
> Cc: kvm@vger.kernel.org
> Subject: Re: Multi Queue KVM Support
>
> Il 20/08/2013 05:21, Naor Shlomo ha scritto:
>> Hi Paolo,
>>
>> The host is running CentOS release 6.3 (Final).
>> I did "yum upgrade libvirt" and "yum upgrade qemu-kvm" a couple of days ago and ended up with these versions.
>>
>> What do you suggest regarding qemu? compile 6.5 or later myself?
>
> RHEL/CentOS 6.5 is not yet out, it's still a few months before it's released.
>
> You can compile QEMU 1.6 from source, or wait for CentOS to have the feature.
>
> Paolo
>
>> I appreciate your help,
>> Naor
>>
>> -----Original Message-----
>> From: Paolo Bonzini [mailto:paolo.bonzini@gmail.com] On Behalf Of
>> Paolo Bonzini
>> Sent: Monday, August 19, 2013 11:22 PM
>> To: Naor Shlomo
>> Cc: kvm@vger.kernel.org
>> Subject: Re: Multi Queue KVM Support
>>
>> Il 19/08/2013 13:29, Naor Shlomo ha scritto:
>>> Hello experts,
>>>
>>> I am trying to use the multi queue support on a Linux guest running Kernel 3.9.7.
>>>
>>> The host's virsh version command reports the following output:
>>> Compiled against library: libvirt 0.10.2 Using library: libvirt
>>> 0.10.2 Using API: QEMU 0.10.2 Running hypervisor: QEMU 0.12.1
>>
>> Is it RHEL or CentOS or Scientific Linux, or something else? If RHEL/CentOS, what release?
>>
>>> The problem is that virtio_has_feature(vdev, VIRTIO_NET_F_MQ) returns FALSE and I don't know why.
>>
>> This version of QEMU is too old. It's possible that 6.5 will have multiqueue, but I'm not entirely sure.
>>
>> Paolo
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in the
>> body of a message to majordomo@vger.kernel.org More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>>
>
prev parent reply other threads:[~2013-08-20 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 11:29 Multi Queue KVM Support Naor Shlomo
2013-08-19 20:22 ` Paolo Bonzini
2013-08-20 3:21 ` Naor Shlomo
2013-08-20 9:27 ` Paolo Bonzini
2013-08-20 11:13 ` Naor Shlomo
2013-08-20 12:12 ` Paolo Bonzini [this message]
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=52135D30.1050709@redhat.com \
--to=pbonzini@redhat.com \
--cc=NaorS@Radware.com \
--cc=kvm@vger.kernel.org \
--cc=libvirt-users@redhat.com \
/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