Re: [ovirt-users] Configuring the SRIOV virsh device

Hi Michael, I’m going to include some screen shots - as I’ve got it all setup exactly how you mention below.. but the config on the Hypervisor is still bridged config. All the UCS port profiles are correct as we use this config on standalone KVM/QEMU hosts. See in-line for pics at the appropriate step . Cheers David *From:* Michael Burman [mailto:mburman@redhat.com] *Sent:* Wednesday, March 09, 2016 19:47 *To:* David LeVene <David.LeVene(a)blackboard.com&gt; *Cc:* users(a)ovirt.org; Dan Kenigsberg <danken(a)redhat.com&gt; *Subject:* Re: [ovirt-users] Configuring the SRIOV virsh device Hi again David) In order to achieve such xml ^^ (the one you describing) you should first of all prepare a proper 'Port Profile' on your UCS manager side. - In your/from your example you should have 2 Port Profiles([1], [2]) configured in your cisco side(see - http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/vm_fex/kvm/...) [1] profile-ame1-test1 [2] profile-ame1-prep1 - This port profiles should associate with your service profiles(blades) - If you have those port profiles on your ucs side and they well configured, then you should follow the steps i suggested in the previous e-mail --> 1) Run for example: engine-config -s CustomDeviceProperties="{type=interface;prop={ifacemacspoof=^(true|false)$;queues=[1-9][0-9]*;vmfex=^[a-zA-Z0-9_.-]{2,32}$;SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}, *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}}" --cver=3.5 - Restart your ovirt-engine service - with --cver=3.5 you can specify your cluster version level. ^^ - If you don't want that it will overwrite your current attributes, you have to send them all as well(like on my example above). ^^ We are using 3.6.3, with the applied patch from https://gerrit.ovirt.org/#/c/54237 # engine-config -g CustomDeviceProperties CustomDeviceProperties: version: 3.0 CustomDeviceProperties: version: 3.1 CustomDeviceProperties: version: 3.2 CustomDeviceProperties: version: 3.3 CustomDeviceProperties: {type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}, *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4 CustomDeviceProperties: {type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}, *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.5 CustomDeviceProperties: {type=interface;prop={ifacemacspoof=^(true|false)$;queues=[1-9][0-9]*;vmfex=^[a-zA-Z0-9_.-]{2,32}$;SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}, *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.6 2) Install vdsm-hook-vmfex-dev on your server(if you don't using vdsm version 3.6, the vmfex hook isn't installed by default) # rpm -qa | grep -i vmfex vdsm-hook-vmfex-dev-4.17.23-1.el7.noarch vdsm-hook-vmfex-4.17.23-0.el7.centos.noarch 3) In ovirt engine you can verify that host have the hooks installed under 'Hosts' main tab - > 'Host Hooks' sub tab You should see there: a) before_device_migrate_destination b) before_device_create c) before_nic_hotplug 4) Create new network and edit the vNIC profile. Choose from the CustomDeviceProperties the 'vmfex' key(like in your example) and in the right field enter your Port Profile id/name(the one that is configured on your UCS side) - 'Networks' main tab(create network) >> 'vNIC Profiles' sub tab(edit the profile and add the 'vmfex' key), so it would look like: vmfex = profile-ame1-test1 and/or vmfex = profile-ame1-prep1 5) Go to 'Setup Networks' sub tab under 'Hosts' main tab --> attach the network with the vmfex profile to NIC on host(drag it), it should be the additional NIC, not the one that the management network attached to. 6) Create VM or use exist one, create/add new vNIC to the VM with the vmfex profile 7) Run VM Note - only Test hosts 2 & 3 are currently configured with this network - so I expect Host 1 to fail. If your port profile configured properly you should see the proper xml, like you described above ^^ --> Good luck and kind regards, Michael B On Wed, Mar 9, 2016 at 8:49 AM, David LeVene <David.LeVene(a)blackboard.com&gt; wrote: Hey All, Still trying to work through this VMFEX stuff, and I know what I want the file to look like at the end.. but not sure how to achieve it from the doco written here http://www.ovirt.org/develop/developer-guide/vdsm/hook/vmfex/ and http://www.ovirt.org/develop/release-management/features/network/ucs-inte... Currently my device looks like this # virsh -r net-dumpxml vdsm-SRIOV <network> <name>vdsm-SRIOV</name> <forward mode='bridge'/> <bridge name='SRIOV'/> </network> I want it looking like this, then the networking will be as it should be! A port group would be a vNIC Profile from the looks of things… <name>vdsm-SRIOV</name> <forward dev='enp6s0f1' mode='passthrough'> ß defined as a passthrough device, not a bridge <interface dev='enp6s0f1'/> <interface dev='enp6s0f2'/> <interface dev='enp6s0f3'/> <interface dev='enp6s0f4'/> < .. list of interfaces available to it which would need to be manually inputted as a hook> </forward> <portgroup name='ame1-test1'> <virtualport type='802.1Qbh'> <parameters profileid='profile-ame1-test1'/> </virtualport> </portgroup> <portgroup name='ame1-prep1'> <virtualport type='802.1Qbh'> <parameters profileid='profile-ame1-prep1'/> </virtualport> </portgroup> </network> Cheers David This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Michael Burman RedHat Israel, RHEV-M QE Network Team Mobile: 054-5355725 IRC: mburman This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error.