From owner-freebsd-xen@FreeBSD.ORG Mon Feb 10 16:31:15 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6876B9D4 for ; Mon, 10 Feb 2014 16:31:15 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9FBD41D66 for ; Mon, 10 Feb 2014 16:31:14 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.95,818,1384300800"; d="scan'208";a="99525348" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 10 Feb 2014 16:30:01 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Mon, 10 Feb 2014 11:30:00 -0500 Message-ID: <52F8FE87.1010705@citrix.com> Date: Mon, 10 Feb 2014 17:29:59 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD? References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 16:31:15 -0000 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.