Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD?
I am running into similar issues routing traffic through a pfSense VM running FreeBSD 10.1. There has to be something with the xn driver or related causing it, as re worked flawlessly. Put together a thread here.. https://forum.pfsense.org/index.php?topic=86827.0;all -- Douglas Haber Managing Member Garden State Computing, LLC Tel: (973) 636-7350 www.gardenstatecomputing.com supp...@gardenstatecomputing.com ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD?
--On 17 February 2014 09:46 + Karl Pielorz kpielorz_...@tdx.co.uk wrote: ifconfig xnX -rxcsum -txcsum Does actually fix the problem. Sadly this doesn't. It seems my testing was flawed (unknownly from a VM on another XenServer - which never exhibited the problem). Real users today noticed the issue (trying to connect out from VM's on the same XenServer as the default gateway FreeBSD VM). As replacing that VM with a CentOS PV host fixes the issue, it must be a bug within the FreeBSD PV NIC code somewhere? [I posted a followup post to xs-devel as well, incase anyone else stumbles into the issue and things the rxcsum thing will fix it]. -Karl ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD?
--On 11 February 2014 18:20 +0100 Roger Pau Monné roger@citrix.com wrote: You could try to disable the following: ifconfig xnX -rxcsum -txcsum -tso4 -lro As a follow-up to this, using: ifconfig xnX -rxcsum -txcsum Does actually fix the problem. I finally got a block of time to go through all this stuff again the other day [it's amazing what difference actually having a decent chunk of uninterrupted time makes!] You do need to be careful when setting this - as at one point, it seemed to cause some kind of issue that may have flooded the network (if it did - this would be the second time we've seen a XenServer DomU flood things by jabbering the same packet over, and over). -Karl ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD?
--On 11 February 2014 18:20 +0100 Roger Pau Monné roger@citrix.com wrote: Just to clarify, are you unable to reach a FreeBSD PV DomU from a Windows PV DomU on the same host, or are you unable to route traffic trough a FreeBSD PV DomU (on the same host)? (ie. can you ssh from the Windows PV DomU into the FreeBSD PV DomU?) ssh from the Windows PV host to the FreeBSD PV DomU host appears to work fine. Attempting to 'route' traffic from the Windows PV host 'through' the FreeBSD PV DomU fails - pings go, DNS goes, initial TCP 'setups' go - but stuff dies thereafter (i.e. may be packet size related or something). Move the FreeBSD PV DomU host to the other XenServer - works. Disabled PV NIC in windows, it works. Run up the FreeBSD PV as HVM (i.e. Realtek) - works. Replace FreeBSD with Linux - it works. So FreeBSD PV on same XenServer as Windows, fails. The only combination I've not tested is FreeBSD DomU PV host trying to use the FreeBSD DomU PV other host as a gateway. I've no reason to believe that won't fail (with the same circumstances as above). The Windows PV Host has 1 NIC which is attached to Xen network 'Office Network' (using e.g. 10.0.0.10). The FreeBSD PV Host has 2 NIC's - Interface 0 is attached to Xen network 'Office Network' (using e.g. 10.0.0.1) - Interface 1 is attached to Xen network 'ADSL Network' (using e.g. 192.168.1.10) The FreeBSD DomU PV host gateway can ping / fetch data fine from the ADSL connection itself, fine. It's setup to NAT for the Office Network (standard rc.conf setup). So it looks like it might actually be a FreeBSD/Xen issue? Yes, it looks that way (dunno if netback might also be involved in this) Doh! :( That's annoying ;) I have to look into this, FreeBSD should not panic when trying to boot without XENHVM on a DomU. Ok the panic wasn't reproducible - I don't know what I did to that kernel build, but re-building GENERIC without the Xen options results in a kernel that boots ok in with HVM drivers (i.e. Realtek NIC's) - and using these fixes the problem (as evidenced above). You could try to disable the following: ifconfig xnX -rxcsum -txcsum -tso4 -lro No combination of those made any difference (which I guess is both a good and a bad thing). Anything else you can think of / worth trying? - As I said I'm running the XenServer distribution ISO (with SP1) - I'm not sure if that has support for much debugging stuff built in? -Karl ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD?
--On 10 February 2014 17:29 +0100 Roger Pau Monné roger@citrix.com wrote: That's quite weird... Do you see any messages in the Xen console (xl dmesg)? Can you boot with a hypervisor compiled with debug=y and see if there are any strange messages on the Xen console? Ok, no messages logged anywhere when this goes on - I'm running XenServer 6.2 installed from the distribution ISO (w/SP1 applied) - I don't know/think that's compiled with 'debug=y'? dmesg output for XenServer coming up is 'unremarkable' as far as I can see, and nothing is logged with 'xl dmesg' Also, does replacing the FreeBSD gateway VM with a Linux PV VM solve the issue? (ie. just to check if Linux also shows this behaviour) Ok, that I could do - and just did. I used CentOS 6 - which booted in 'Xen' aware mode (with Xen Virtual ethernet driver) - annoyingly that works *fine* (i.e. no issues). So, Windows 7 PV - FreeBSD 9.x / 10.x PV = Fail (if on same XenServer host) Windows 7 HVM - FreeBSD PV = Works Windows 7 PV - Linux (CentOS 6) PV = Works So it looks like it might actually be a FreeBSD/Xen issue? I just tried booting FreeBSD 10 without the Xen options in the kernel, and it won't boot (it panics). Is there any way of booting 10.x in HVM mode (i.e. with no Xen PV support) - or at least switching 'xn' for 're' as far as nic's go? Are there any 'offload' type features that can be disabled for 'xn' nics in FreeBSD? -Karl ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD?
On 11/02/14 17:33, Karl Pielorz wrote: --On 10 February 2014 17:29 +0100 Roger Pau Monné roger@citrix.com wrote: That's quite weird... Do you see any messages in the Xen console (xl dmesg)? Can you boot with a hypervisor compiled with debug=y and see if there are any strange messages on the Xen console? Ok, no messages logged anywhere when this goes on - I'm running XenServer 6.2 installed from the distribution ISO (w/SP1 applied) - I don't know/think that's compiled with 'debug=y'? dmesg output for XenServer coming up is 'unremarkable' as far as I can see, and nothing is logged with 'xl dmesg' Also, does replacing the FreeBSD gateway VM with a Linux PV VM solve the issue? (ie. just to check if Linux also shows this behaviour) Ok, that I could do - and just did. I used CentOS 6 - which booted in 'Xen' aware mode (with Xen Virtual ethernet driver) - annoyingly that works *fine* (i.e. no issues). So, Windows 7 PV - FreeBSD 9.x / 10.x PV = Fail (if on same XenServer host) Windows 7 HVM - FreeBSD PV = Works Windows 7 PV - Linux (CentOS 6) PV = Works Just to clarify, are you unable to reach a FreeBSD PV DomU from a Windows PV DomU on the same host, or are you unable to route traffic trough a FreeBSD PV DomU (on the same host)? (ie. can you ssh from the Windows PV DomU into the FreeBSD PV DomU?) So it looks like it might actually be a FreeBSD/Xen issue? Yes, it looks that way (dunno if netback might also be involved in this) I just tried booting FreeBSD 10 without the Xen options in the kernel, and it won't boot (it panics). Is there any way of booting 10.x in HVM mode (i.e. with no Xen PV support) - or at least switching 'xn' for 're' as far as nic's go? I have to look into this, FreeBSD should not panic when trying to boot without XENHVM on a DomU. AFAIK there's no way to selectively enable/disable the usage of certain PV interfaces, but I certainly don't recommend switching to an emulated nic to do the routing. Are there any 'offload' type features that can be disabled for 'xn' nics in FreeBSD? You could try to disable the following: ifconfig xnX -rxcsum -txcsum -tso4 -lro Or a mix of those, I'm afraid I'm not that familiar with netfront/netback to provide any more hints. In the past there have been reports of TSO breaking on Xen PV interfaces, but AFAIK this should be fixed already. Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD?
On 08/02/14 16:03, Karl Pielorz wrote: Hi, I've got an 'issue' (more with Xen than FreeBSD) - the upshot is, I need to disable the PV NIC (xn) from a VM running XENHVM kernel. Is this possible? - In an ideal world I'd like to keep the storage drivers etc. - I just need to use the HVM 're' interface, not 'xn' interface... For those who want to know what the issue is - we have a number of VM's on 1 Xen machine (e.g. 'Xen1') all using PV drivers (Windows and FreeBSD VM's). A FreeBSD VM is the 'default' gateway for the others - and it doesn't work :( Packets are either going missing - or getting mangled. If you 'migrate' one of those hosts to another Xen machine in the pool (e.g. Xen2) it works. If you migrate the default gateway VM over to the other Xen machine - all the other VM's on the original XenServer suddenly work (i.e. can see the outside world) - alternatively if you switch from PV drivers to HVM drivers on the affected guests - everything works, regardless of whether the VM's are on Xen1, Xen2 - or the same XenServer as the default gateway VM. Only PV - PV shows the issue, and only when they're both hosted on the same XenServer. Hence wondering about disabling the PV nic on the default gateway, instead of having to do it on all the other VM's... That's quite weird... Do you see any messages in the Xen console (xl dmesg)? Can you boot with a hypervisor compiled with debug=y and see if there are any strange messages on the Xen console? Also, does replacing the FreeBSD gateway VM with a Linux PV VM solve the issue? (ie. just to check if Linux also shows this behaviour) Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
