pfSense

which driver is it saying doesn't support altq?

I'm using 2 NIC's Realtek RTL8111/8168 PCI Express Gigabit Ethernet. Both are working on PFSense 2.1.5 with traffic shapping but on 2.2 doesn't.

PFSense in both scenaries is running under XenServer 6.2 SP1 (updated). I just start the configuration using traffic shapping wizard but on the final when I'll click to finish I got that message on 2.2.

Yes, that NIC's changed to xm but still working on 2.1.5 and not on 2.2.

Please, can somebody build an unofficial release (2.2.1+) without netfront. I don't have time to create a build environment (sign LA, create SSH-key, ...).
If somebody has already a build environment it should be easy to build without netfront.

Is there something to test or something else to do?
I'm still on 2.1.5 and want to update.

Will be there a real solution in next time or should I add an extra nic to these servers?

I'm installing the next server and need 8+ networks. Because xen can't handle so much NICs I have to use tagging.

1. build an extra image without xn.
2. show me an loader option to disable xn.

I can't work with this. With an extra NIC I loose bandwidth.

There are a lot of posts about pfsense 2.2 and buggy xn implementation.

I think same as Grischa Zengel said!
We need an option to disable xn implementation

2.2.4-RELEASE Now Available

When can we use this?
There are security fixes, which we must have.

Just to step in, until VLAN and ALTQ is supported there really needs to be a way to disable xn.

It's time for changes after 8 month:
https://redmine.pfsense.org/issues/4401#note-10

Please, put this to 2.2.5:
https://svnweb.freebsd.org/base?view=revision&revision=286999

If I read #3670 I will this twice. I'm still on 2.1.5 and ipv6 didn't work with my ISP.

This should be retested. There is a lot of kernel changes and Xen improvements in the FreeBSD kernel in the last 6 years.