Hi all, I have been testing out KVM on the ARM a15 board, using virtio-net I have used the originals patches from here :http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg02467.html . (Please note, I only tested virtio-net) For the guest configuration ( kernel menuconfig ) I added : Device-driver -> Network device support -> Virtio-net Virtio-drivers -> Virtio-balloon Virtio-drivers -> Platform bus driver for memory mapped virtio devices Virtio-drivers -> Memory mapped virtio devices parameter parsing Block-devices -> Virtio-block Device-drivers -> Character-devices -> Virtio-console I modified vexpress.c ( patch 12 ), to add a virt-mmio in place of the network adapter, and the ethernet card is deleted from the dtb. And this is the QEMU command line : qemu-system-arm -enable-kvm -kernel kernel.bin -dtb ca15.dtb -M vexpress-a15 -cpu cortex-a15 -nographic -append "console=ttyAMA0,38400 virtio_mmio.device=1M@0x4e000000:74:0" -m 512M -device virtio-net,transport=virtio-mmio.0,netdev=net0 -netdev type=tap,id=net0 The performance is really better with virtio-net than lan9118 : I tested using the wget command : FROM HOST : 7.86 MBytes/s FROM KVM GUEST WITH VIRTIO-NET : 3.56 MBytes/s FROM KVM GUEST WITH LAN9118 : 0.19 MBytes/s We are now working on the issues quoted in the email above, and on cleaning up the patches: 1. On creation of back-end we need to resolve somehow if props were explicitly set by user. 2. Back-end device can't be initialized if there are no free bus created by transport, so you can't specify -device virtio-blk,transport=virtio-pci.0,... -device virtio-pci,id=virtio-pci.0 3. Implement virtio-xxx-devices such that they just create virtio-pci and virtio-xxx devices during initialization. 4. Refactor all remaining back-ends since I just tried blk, net, serial and balloon. 5. Refactor s390 Fred _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
