Ciao, mijanek
I tried with your suggestion but it did not work for me.
Testing on CentOS is taking a bit longer: CentOS 6.5 is still using 2.6.x kernels and I've just downloaded CentOS 7 ISO and I'm doing the installation now.
I really want to try with Mellanox OFED package before cross...
After some more testing on Mellanox card, I decided to try with a different card because I noticed that the integrated Intel network card is SR-IOV capable, too.
I simply removed and reloaded the igb module passing max_vfs=7 as modprobe option and the virtual functions appeared.
Of course you...
That's exactly what I have done. It works as expected on CentOS 6.5 and it works on Proxmox, too.
The "trick" to get the VFs exposed is in the options passed when loading mlx4_core module.
It is written in french and it will be difficult for me, but commands are in english! I'll try to use...
After banging my head on CentOS + oVirt, I have to say that it does not work and I am not able to understand why.
I can add the PCI device to the VM using girt-manager but the VM is not going to boot.
If I try to boot the VM using the web interface, the PCI device is automatically removed and...
Here is my dmidecode output:
Base Board Information
Manufacturer: Supermicro
Product Name: H8QG6
Version: 1234567890
Serial Number: WM139S600452
Asset Tag: 1234567890
Features:
Board is a hosting board
Board is...
I know that it's not possible to pass a PCI device to multiple VMs: as far as I can understand this is the reason for the existence of SR-IOV; the same PCI device (usually referred as PF, Physical Function) is exposed to the system as a group of VF (Virtual Function); each VF has its own address...
Probably I misused the word "revert": I was only referring to hostpci0 parameter not to the whole system .
What I mean is: if I need to connect a VF "exported" by Mellanox card when SR-IOV is enabled, I suppose that I need to specify the VF address (e.g. 04:00.1 or 04:01.2) and not the address...
Hi, Tom
thank you for pointing this out.
I've upgraded (I hope, I am more a CentOS user than a Debian one, so I really do not know if I issued the correct commands!) everything.
pveversion output is now:
root@hpc001:~# pveversion -vproxmox-ve-2.6.32: 3.2-132 (running kernel: 3.10.0-3-pve)...
I've just tried with the updated instructions and with kernel 3.10 but it does not work on my side.
If I point to the physical device 04:00.0, the system can only start one single VM accessing the Mellanox card.
If I point to a virtual function (VF) e.g. 04:00.1, the VM cannot start complaining...
Good morning to everyone!
Even if this looks like my very first message, I've been using (and I'm still using) ProxMox since version 1.5 and it is still my preferred virtualization platform.
I'm trying to set up a sort of very private cloud dedicated to HPC; I know that HPC and virtualization...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.