<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open VSwitch on Sebastian Scheinkman - Red Hat Openshift, Networking, Kubernetes and Cloud Native</title><link>https://sebasblog.com/tags/open-vswitch/</link><description>Recent content in Open VSwitch on Sebastian Scheinkman - Red Hat Openshift, Networking, Kubernetes and Cloud Native</description><generator>Hugo</generator><language>en-us</language><copyright>sebasblog.com</copyright><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sebasblog.com/tags/open-vswitch/index.xml" rel="self" type="application/rss+xml"/><item><title>Testing SR-IOV Switchdev Without a SmartNIC</title><link>https://sebasblog.com/p/switchdev-mock-driver/</link><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><guid>https://sebasblog.com/p/switchdev-mock-driver/</guid><description>&lt;p&gt;Developing SR-IOV switchdev support usually means keeping a hardware lab close by. A policy change can touch PCI device discovery, VF creation, driver binding, representor discovery, OVS configuration, and CNI namespace moves. Unit tests help, but they cannot tell us whether those pieces work together when two pods send traffic.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/SchSeba/switchdev-mock-driver"&gt;&lt;strong&gt;switchdev-mock-driver&lt;/strong&gt;&lt;/a&gt; gives us that integration environment inside QEMU/KVM. It combines genuine emulated PCI SR-IOV devices with a Linux kernel driver that exposes switchdev interfaces and executes supported TC flower rules in guest memory.&lt;/p&gt;</description></item></channel></rss>