PfSense virtio networking under KVM
-
The download link isn't available any more.
can anybody upload the driver.
thanks
-
Same here.
I will love to get a hand on these drivers.
-
i386: http://www.multiupload.com/4TL8NFJRLN
amd64: http://www.multiupload.com/UGFE0L4MKB -
rapidshare isn't serious man!
-
I guess you can use the other six services to download.
-
Apparently this mod breaks traffic shaper, the interfaces are not available under traffic shaper. I wonder if there is an easy way to fix itā¦
-
Try adding it to the list at line 3520 of /etc/inc/interfaces.inc
It may not really be altq capable, but you can try.
-
Will the virtio driver be included in the final release of PfSense 2.0?
It's mentioned in this thread that it's included since 2.0 but I won't get it working only by installing it manually.
"We have added this driver to 2.0. Ā Please test a new snapshot and it should be present sometime tomorrow."
-
Hello,
i would bump this topic and ask, are there now virtio drivers in the latest pfSense 2.0 RCx?
Regards, Valle
-
can you please make a statement and tell us if in the final pfsense 2.0 will be virtio drivers for kvm?
Thanx for answer.
Valshare
-
after a view tests, i can say that the actual virtio driver didnĀ“t work correkt. More than 3 network interfaces didnĀ“t work correct (routing)
-
thanks for that information. did you also test the virtio disk driver?
-
hi,
no i didnĀ“t test die virtio disc driver because of the trouble with the virtio net drivers. I think its better to wait for the offical, when there ever will be released.
I have tested successfull the network e1000 and iscsi disc drivers with pfsense.
-
any news about that ?
are the virtio drivers included in the 2.0 final release ? -
Hello!
Running pfSense-2.0-RELEASE-i386
Same problem here :)
On E1000 with KVM I'm getting 250-300Mbit/s
This isn't enough for internal routing (for example when using pfSense to route traffic between 192.168.x.x and 10.x.x.x).
I'm just curious about that.Okay. Some tests.
Q1: why I have to exit shell and go into shell again (press 8ā¦) to see new command (iperf) available after adding in packages?
Q2: reaching about 240-250Mbit/s DebianVM+virtio-net -> pfSenseVM+e1000 and pfSenseVM+e1000 -> DebianVM+virtio-net
Q3: there is no problem to reach about 900Mbit/s from DebianVM+virtio-net to the client.
Q4: timeouts on IDE drive attached in pfSenseVM. No such thing when using virtio-storage in DebianVM.
Both VM placed on the same storage - software mdadm RAID1 with 2 drives.
-
maybe this could help:
http://people.freebsd.org/~kuriyama/virtio/
-
@TooMeek, thanx for the tests. Do you have testet the drivers that WetWilly has postet?
Regards, Valle
-
I tried the drivers that WetWilly has posted, but I can't see any virtio network interface in pfSense.
How can I catch the log of loading /boo/loader.conf? -
well, the driver I posted is for freebsd 8.2 and 9.0
If I'm not mistaken pfSense 2. is based upon 8.1, so the driver most likely need (alot) tweaking.
-
Is inclusion of virtio drivers in pfSense planned in the near future?
I need a permanent virtual router solution to do inter vnet routing on KVM host using no NAT, firewall rules as needed, and OpenOSPFd (to distribute vnets to main hardware firewall/router dynamically) Ā and first installed pfSense (2.0.1). It was functionally up to the task of course, but as it lacks virtio (and possible other KVM related optimizations) the performance was horrendous.
I gave it 1 CPU-core (Xeon E3 1220 3.1GHz) and 512MB RAM but it actually idled at around 50-60% CPU usage on the KVM host even though the actual usage in pfSense VM was about 100% idle under a couple of hundred connections and maybe around 1-20mbit/s traffic. This indicates a massive performance hit in the emulated VM-interface alone.
Testing routing performance with iperf I couldn't get more than about 450mbit/s and then the CPU was completely maxed out making the web interface unusable during the test.Because of this I instead installed Debian Wheezy, activated forwarding and installed quagga for OSPF using virtio both for disk and network interfaces and this machine idles at 0-0.1% CPU usage on KVM host and during iperf tests the routing performance was a full 944mbit/s, which is as good as it possibly can get without jumbo frames etc, using only 13-16% CPU power on the KVM host which is very good.
Internal guest to guest performance using virtio and Debian guests was 19.5 gbit/s with iperf, so the performance is potentially extremely good. I don't know if FreeBSD can reach those speeds on a KVM host at all, but pfSense should at least be able to idle at around 0% host CPU usage and do plain routing at gigabit speeds without any problems to be an alternative for VM appliances in KVM based hypervisors.
As I have networked power monitoring on the power receptacles I could actually see the power usage decrease by several watts by replacing the pfSense VM with Debian because of the high idle CPU usage.