From 8b5888441e28bf3760d7e390f1a0ba2bb12d8af8 Mon Sep 17 00:00:00 2001 From: charlenechien Date: Sat, 28 Mar 2026 10:45:51 +0800 Subject: [PATCH] Document virtio config and bridge setup In Linux driver binding, once a device ID matches one supported by a driver, the driver is bound and its probe() is invoked. If a device is already bound, subsequent binding attempts skip it. With CONFIG_VIRTIO_NET=y, virtio_net binds to the virtio device first, preventing vwifi from binding later. Document how to disable the virtio_net driver so the virtio device can bind to vwifi. Include the expected CONFIG setting in .config and provide menuconfig navigation steps. Also document how to bring up the bridge device (br0) required for the networking setup, enabling traffic flow between the host and virtual machines via virtio-backed interfaces. --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 24435c2..9c3c2d8 100644 --- a/README.md +++ b/README.md @@ -652,7 +652,10 @@ Enter the top directory of the Linux kernel source and use the following command ```shell $ make menuconfig ``` -The default kernel configuration will work for our testing environment, so just click `save` and we get `.config` on the top directory. +To allow virtio device to be bound to vwifi driver, please ensure the virtio network driver is disabled before you click `save`. By excluding the virtio network driver, you should spot `CONFIG_VIRTIO_NET=n` in the `.config` file on the top directory. +``` +Device Drivers ---> Network device support ---> Virtio network driver ---> no +``` Before building the kernel, please ensure that all the needed packages or libraries have been installed in your machine. @@ -750,6 +753,11 @@ $ sudo ip link set tap1 master br0 $ sudo ip link set tap2 master br0 ``` +Start `bridge` device: +```shell +$ sudo ip link set br0 up +``` + ### Start VM with Qemu Once we have our kernel image and rootfs, we can start running `Qemu`: