From owner-freebsd-xen@FreeBSD.ORG Sat Feb 8 15:08:30 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 2D532EE1 for ; Sat, 8 Feb 2014 15:08:30 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id DB9A91313 for ; Sat, 8 Feb 2014 15:08:29 +0000 (UTC) Received: from study64.tdx.co.uk (study64.tdx.co.uk [62.13.130.231]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s18F3Rmi066102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 8 Feb 2014 15:03:28 GMT Date: Sat, 08 Feb 2014 15:03:27 +0000 From: Karl Pielorz To: freebsd-xen@freebsd.org Subject: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD? Message-ID: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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: Sat, 08 Feb 2014 15:08:30 -0000 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... -Karl