From owner-freebsd-xen@FreeBSD.ORG  Tue Nov  5 08:43:48 2013
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 012D6F25
 for <freebsd-xen@freebsd.org>; Tue,  5 Nov 2013 08:43:47 +0000 (UTC)
 (envelope-from hilton.day@gmail.com)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com
 [IPv6:2607:f8b0:400d:c01::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id B98292626
 for <freebsd-xen@freebsd.org>; Tue,  5 Nov 2013 08:43:47 +0000 (UTC)
Received: by mail-qc0-f178.google.com with SMTP id x19so4609832qcw.37
 for <freebsd-xen@freebsd.org>; Tue, 05 Nov 2013 00:43:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=X3IiO6Rd6mb2L2JmmV/AqOvOSNbdjwspEj3jGM3spXQ=;
 b=meV6VyA51003i92KDDK45n9+jDVk0vtudITwtu8LR9Br6K0RuelIqzg6OGvbrNPIvp
 ZwhNn27vmds7bzD86X9KbJJ3cN3aKgv4T6D3/bZImCbELILVIk2kmYstZNFYZtREvDpf
 8jgLhXT89TMgqXp3OCatRzZJoxcUPBpm3iWpC42wIH0wKYNL+kk+UAiFyc+rDCgfgjyr
 I9aqXoJ0AeIj7chdf6Nse6PXrqPkD7DJJTBc4UxyMc1xfAWqEXjV0CAdLHowdzYq4BHS
 5PWQaXdqYuGvW5t4z36Jb5ki5xLcTXQAakQ5YfYkRWbpFUWNfLgrIGd5iVYb0x7H1ITX
 6Xmg==
MIME-Version: 1.0
X-Received: by 10.224.51.131 with SMTP id d3mr27991461qag.0.1383641026923;
 Tue, 05 Nov 2013 00:43:46 -0800 (PST)
Received: by 10.49.47.103 with HTTP; Tue, 5 Nov 2013 00:43:46 -0800 (PST)
Date: Tue, 5 Nov 2013 19:43:46 +1100
Message-ID: <CABomu8P88ZfJvO7sPd9-L6Thcaoxj7WgjUKuud3VU40D6h1C9w@mail.gmail.com>
Subject: Paravirt domU and PCI Passthrough
From: Hilton Day <hilton.day@gmail.com>
To: freebsd-xen@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 08:43:48 -0000

Hi - firstly a warning.  While I've been running Xen on Linux for about 6
years, I've only just started to scratch the surface of freeBSD.

I just compiled a (working) paravirt kernel for freeBSD 8.3 (actually for
pfSense firewall), and have succeeded in running it with a couple of
virtual interfaces.  However, I've struck a couple of limitations:

1.  Seems to be no support for the Xen pcifront to enable pci passthrough
to paravirt domUs?
2.  SMP support seems to be broken - I get a kernel panic with more than
one core for the VM.

I've had a look and can't find anything like the Linux kernel option
for CONFIG_XEN_PCIDEV_FRONTEND
to enable pci support in paravirt? (but this could be lack of familiarity
with freeBSD build process/tree/files).

I've succeessfully passed thorugh the same NIC to freeBSD Xen HVM domUs
(running 8.3 and 9.1), but would prefer to get a fully paravirt instance up
and running.

Is PCI Passthrough possible with a freeBSD paravirt domU?  I just set up a
freeBSD 10 BETA2 environment and have kicked off the build process with:

> make buildkernel KERNCONF=XEN

I'm just wondering whether I'm chasing a dead end and should just settle
for a XEN HVM solution?

Thanks for any advice,

Hilton.