Date: Tue, 29 May 2018 08:18:14 +0000 From: bugzilla-noreply@freebsd.org To: xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Message-ID: <bug-188261-23905-dJOR4e646v@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-188261-23905@https.bugs.freebsd.org/bugzilla/> References: <bug-188261-23905@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #34 from karl@pielorz.com --- (In reply to Eitan Adler from comment #33) Hi - this issue still exists, I've just re-tested in 10.4 and 11.1. I'm not able to test 12.x at the moment, but I have no reason to believe it's been fixed in current or anything. It affects anything working with 'low level' packets - so NAT, OpenVPN, DHCP et'al. - e.g. with OpenVPN it seems packet coalescing 'behind the scenes' e= nds up presenting way over 1500 byte packets to OpenVPN - which it point blank refuses to handle. Workaround we're using here is to set 'hw.xen.disable_pv_nics=3D1' in /boot/loader.conf on FreeBSD with a small mod to 'qemu-dm-wrapper' on the X= en Server, and a custom field added to affected VM's in XenCenter that the wra= pper 'keys off' - this turns xn0 into vtnet0 for these hosts - these do work with the above applications, and are still live-migratable (and appear to be bet= ter performance than re0 NIC's). -Karl --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-188261-23905-dJOR4e646v>