I can't seem to get a virtio network card to work with my FreeNAS virtual machine.
I'm running libvirtd and qemu, configuring things via virt-manager. My host OS is Pop_OS 18.04, so basically Ubuntu 18.04.
I've successfully loaded the virtio modules in FreeNAS. But when I switch the NIC to virtio, I can't figure out how to make FreeNAS associate the device with the driver. I end up with the attached screenshot. As you can see, the Red Hat, Inc. Virtio network device is listed. And at the top, the last two lines of the grep output are from when I had the NIC set to virtio, they say "no driver attached".
If I run ifconfig, it just lists the 'lo' network.
Once I switch back to the 'rtl8139' device model for the NIC, it works just fine.
While drafting this post, I hit upon the idea of adding a second NIC for the virtio NIC, that let me ssh into the vm and copy out the output.
So, here's info I was able to gather:
I also checked ui/network/interfaces/add to see if I could find another NIC listed. It just had the re0 'rtl8139' device available, which was already configured. No sign of something for the virtio device.
FYI, I'm hoping the virtio network will give me more bandwidth. :) Not sure if it will, or not, when I can't test. :\
FreeNAS Version: FreeNAS-11.2-U4.1
16GB of RAM.
Since it's virtualized, is there a need for what kind of motherboard/cpu/etc?
Thanks in advance for any help. I hope I've included enough information. I did spend a good few hours, over multiple days, searching on the topic, both here, and via Google. This is the closest I could get.
I'm running libvirtd and qemu, configuring things via virt-manager. My host OS is Pop_OS 18.04, so basically Ubuntu 18.04.
I've successfully loaded the virtio modules in FreeNAS. But when I switch the NIC to virtio, I can't figure out how to make FreeNAS associate the device with the driver. I end up with the attached screenshot. As you can see, the Red Hat, Inc. Virtio network device is listed. And at the top, the last two lines of the grep output are from when I had the NIC set to virtio, they say "no driver attached".
If I run ifconfig, it just lists the 'lo' network.
Once I switch back to the 'rtl8139' device model for the NIC, it works just fine.
While drafting this post, I hit upon the idea of adding a second NIC for the virtio NIC, that let me ssh into the vm and copy out the output.
So, here's info I was able to gather:
Code:
root@xunlaichest[~]# ifconfig re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE> ether 52:54:00:7e:50:8e hwaddr 52:54:00:7e:50:8e inet 192.168.122.214 netmask 0xffffff00 broadcast 192.168.122.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (100baseTX <full-duplex>) status: active lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> groups: lo root@xunlaichest[~]# grep -i ethernet /var/log/messages Jun 9 15:18:23 xunlaichest re0: Ethernet address: 52:54:00:7e:50:8e Jun 9 16:57:04 xunlaichest pci4: <network, ethernet> at device 0.0 (no driver attached) Jun 9 17:13:37 xunlaichest pci4: <network, ethernet> at device 0.0 (no driver attached) Jun 9 17:28:23 xunlaichest re0: Ethernet address: 52:54:00:7e:50:8e Jun 9 17:40:52 xunlaichest pci4: <network, ethernet> at device 0.0 (no driver attached) Jun 9 17:40:52 xunlaichest re0: Ethernet address: 52:54:00:7e:50:8e root@xunlaichest[~]# lspci | grep -i virt 00:01.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) 01:00.0 Communication controller: Red Hat, Inc. Virtio console (rev 01) 03:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon (rev 01) 04:00.0 Ethernet controller: Red Hat, Inc. Virtio network device (rev 01) root@xunlaichest[~]# kldload virtio kldload: can't load virtio: module already loaded or in kernel root@xunlaichest[~]# kldload vtnet kldload: can't load vtnet: module already loaded or in kernel
I also checked ui/network/interfaces/add to see if I could find another NIC listed. It just had the re0 'rtl8139' device available, which was already configured. No sign of something for the virtio device.
FYI, I'm hoping the virtio network will give me more bandwidth. :) Not sure if it will, or not, when I can't test. :\
FreeNAS Version: FreeNAS-11.2-U4.1
16GB of RAM.
Since it's virtualized, is there a need for what kind of motherboard/cpu/etc?
Thanks in advance for any help. I hope I've included enough information. I did spend a good few hours, over multiple days, searching on the topic, both here, and via Google. This is the closest I could get.
Attachments
Last edited: