pfSense Gold Subscription

Author Topic: IMPORTANT: Xen/KVM networking will not work using default hypervisor settings!  (Read 38708 times)

0 Members and 1 Guest are viewing this topic.

Offline cmb

  • Hero Member
  • *****
  • Posts: 11230
  • Karma: +893/-7
    • View Profile
    • Chris Buechler
Should hit 10-STABLE in a week, after which it'll be in 2.3.

Offline claytondf

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Nice topic.
It is used XenServer 6.5 and pfSense 2.2.4 and had problems with slowness.
Thanks users  johnkeates and tdslot !!!  ;D ;D

Clayton

Offline mortenchristensen

  • Newbie
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Should hit 10-STABLE in a week, after which it'll be in 2.3.

Ane news on this ?

Offline cmb

  • Hero Member
  • *****
  • Posts: 11230
  • Karma: +893/-7
    • View Profile
    • Chris Buechler
Should hit 10-STABLE in a week, after which it'll be in 2.3.

Ane news on this ?

It was MFCed in October, so it's been in 2.3 for a while.

Offline slabity

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
It was MFCed in October, so it's been in 2.3 for a while.

I have installed the latest 2.3 beta and still require turning off the checksums on my Xen 4.4 system. Is that normal?

Offline johnkeates

  • Hero Member
  • *****
  • Posts: 647
  • Karma: +52/-1
    • View Profile
It was MFCed in October, so it's been in 2.3 for a while.

I have installed the latest 2.3 beta and still require turning off the checksums on my Xen 4.4 system. Is that normal?

Yes, it is normal. Unless verified otherwise, it will be needed with virtio.

Offline qtlnx

  • Newbie
  • *
  • Posts: 19
  • Karma: +0/-4
    • View Profile
Still present in last nightly build. Is there a definitive answer on when it is going to be resolved?

Offline johnkeates

  • Hero Member
  • *****
  • Posts: 647
  • Karma: +52/-1
    • View Profile
Still present in last nightly build. Is there a definitive answer on when it is going to be resolved?

I believe this depends on FreeBSD having the fix and not pfSense itself.


Offline seedickcode

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
 :o Arg - Lost a whole day tracking this down.  It started with a debian install behind the new pfsense failing at the mirror selection.  In the end it wasn't until I slapped on that extra -v in the TCP dump that I finally discovered it.  I have a weird unrouted /32 on the WAN, so figured it must have been something with that - but ping worked everywhere.  Figured it was DNS (initial symptom).   

Anyway, long story short, pfSense is in a virtual environment, and using VirtIO networking.  Disabled the hardware checksum, and bang - all working. 
(fliptable).

Offline Fmslick

  • Jr. Member
  • **
  • Posts: 74
  • Karma: +2/-1
  • ﴾͡๏̯͡๏﴿ O'RLY?
    • View Profile
    • Fmslick.com
Hi to All,

I just installed PFSense 2.2 on Xenserver 6.5 . So I got the same problem as described. And I want to share with my configuration fix for this problem.

Sorry if will be off topic I didn't find best place for this.  :)

Find your PFsense VM network VIF UUID's:
Code: [Select]
[root@xen ~]# xe vif-list vm-name-label="RT-OPN-01"
uuid ( RO)            : 08fa59ac-14e5-f087-39bc-5cc2888cd5f8
         vm-uuid ( RO): 0128bdba-df81-d729-ddbc-c60575e02624
          device ( RO): 1
    network-uuid ( RO): 7af0dc44-dc05-44f2-3741-883acb937747


uuid ( RO)            : 799fa8f4-561d-1b66-4359-18000c1c179f
         vm-uuid ( RO): 0128bdba-df81-d729-ddbc-c60575e02624
          device ( RO): 0
    network-uuid ( RO): 106ad80e-9522-77fd-3cc6-4b2b6fc03ecc

Then modify those VIF UUID's with this settings:
Code: [Select]
xe vif-param-set uuid=08fa59ac-14e5-f087-39bc-5cc2888cd5f8 other-config:ethtool-tx="off"
xe vif-param-set uuid=799fa8f4-561d-1b66-4359-18000c1c179f other-config:ethtool-tx="off"

And Shutdown VM and start again. Not restart PFSense from console.

This fixed my issue, thanks m8  ;D
We all start same where

Offline webdawg

  • Full Member
  • ***
  • Posts: 114
  • Karma: +3/-1
    • View Profile
Does this still need to be done in 2.3?

Offline johnkeates

  • Hero Member
  • *****
  • Posts: 647
  • Karma: +52/-1
    • View Profile
As far as I know, this has been fixed in FreeBSD 10.2 upstream.

Offline webdawg

  • Full Member
  • ***
  • Posts: 114
  • Karma: +3/-1
    • View Profile
I have 2.3 running in HVM mode with HVM nics and hd's and besides not going above 100mbit (11-13 Megabytes a second) in any direction that is the only problem I can find.

I did not add any tunables.

Offline johnkeates

  • Hero Member
  • *****
  • Posts: 647
  • Karma: +52/-1
    • View Profile
I have 2.3 running in HVM mode with HVM nics and hd's and besides not going above 100mbit (11-13 Megabytes a second) in any direction that is the only problem I can find.

I did not add any tunables.

It's a VirtIO/PV-only bug ;-) HVM always worked.