2013/2/5 Or Gerlitz :
> On 05/02/2013 12:32, Mathis GAVILLON wrote:
>>
>> I've just finished to install qemu 1.3.1 and all is working well. IRQ
>> error has disappeared and an IB interface is know available in the virtual
>> machine.
>
>
> nice! could you say again what distribution provided you wi
On 05/02/2013 12:32, Mathis GAVILLON wrote:
I've just finished to install qemu 1.3.1 and all is working well. IRQ
error has disappeared and an IB interface is know available in the virtual
machine.
nice! could you say again what distribution provided you with the
"problematic" kvm-qemu and wh
403.html
>
> And they're in the current development tree which is stabilizing for the
> 1.4.0 release. Thanks,
>
> Alex
>
>>
>> From: Mathis GAVILLON [jbibo...@gmail.com]
>> Sent: 04 February 2013 11:42
>> To: Ja
On 04/02/2013 17:24, Alex Williamson wrote:
These are available in the qemu 1.3.1 stable release
http://lists.gnu.org/archive/html/qemu-devel/2013-01/msg05403.html
And they're in the current development tree which is stabilizing for the
1.4.0 release
thanks Alex!
Mathis, does this helps?
Or
the current development tree which is stabilizing for the
1.4.0 release. Thanks,
Alex
>
> From: Mathis GAVILLON [jbibo...@gmail.com]
> Sent: 04 February 2013 11:42
> To: Jack Morgenstein
> Cc: Or Gerlitz
> Subject: Re: Fwd: Error messa
ex, what stable branch/release would you recommend to use?
Or.
From: Mathis GAVILLON [jbibo...@gmail.com]
Sent: 04 February 2013 11:42
To: Jack Morgenstein
Cc: Or Gerlitz
Subject: Re: Fwd: Error message when trying to use Infiniband virtual functions
i
On Tuesday 29 January 2013 17:18, Mathis GAVILLON wrote:
> Support for interrupt remapping should be now available (kernel has
> been recompiled with but is there any way to check if it's available
> ?).
> I tried to do what you say in step 2 (num_vfs=1 and probe_vf=0) but it
> doesn't change anyth
Support for interrupt remapping should be now available (kernel has
been recompiled with but is there any way to check if it's available
?).
I tried to do what you say in step 2 (num_vfs=1 and probe_vf=0) but it
doesn't change anything. I also tried num_vfs=2 and probe_vf=1 but
nothing is better.
N
On Tuesday 29 January 2013 15:15, Mathis GAVILLON wrote:
> In fact, one boxe wasn't check in IOMMU submenu (Support for Interrupt
> Remapping (EXPERIMENTAL)). I've recompiled the kernel of the host and
> guest (is it necessary for this last one ?). But the error message is
> already present. Just b
On Tuesday 29 January 2013 15:15, Mathis GAVILLON wrote:
> In fact, one boxe wasn't check in IOMMU submenu (Support for Interrupt
> Remapping (EXPERIMENTAL)). I've recompiled the kernel of the host and
> guest (is it necessary for this last one ?)
Yes, it is necessary. Without that checked, I not
I forgot : my CPU is an Intel(R) Xeon(R) CPU E5-2660 and
"intel_iommu=on" was already added in kernel command line .
Thanks
Mathis
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.ker
Which VF did you map to the guest O/S?
In your configuration, both HCAs will have the PF and the
first VF running on the hypervisor,
and the remaining VFs available for binding to guests.
You have:
mlx4_core :05:00.0: Enabling SR-IOV with 3 VFs <== PF
pci :05:00.1: [15b3:1002] type 00 clas
The version of firmware I gave you was wrong (I've two cards
(ConnectX2 and ConnectX3, I only use ConnectX 3) in my computer and I
took the bad one). The firmware installed on my ConnectX3 Infiniband
Card is 2.11.500.
KVM is 1.2.2-1 version.
I tried to load the driver with options you gave me but t
13 matches
Mail list logo
