From owner-freebsd-virtualization@FreeBSD.ORG Thu Jan 23 02:48:21 2014 Return-Path: Delivered-To: virtualization@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 ESMTPS id AC2E6F8D; Thu, 23 Jan 2014 02:48:21 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5C72F1123; Thu, 23 Jan 2014 02:48:21 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id e16so1727386qcx.38 for ; Wed, 22 Jan 2014 18:48:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KYhd1uTJb1Xw6/0xvEz/byiLHkC0HhRheCZO5TmoE7c=; b=vd4s32mkwzDRmcpQApmYnphfpLSNBNE8YLkqkNvIiZAic3b598fL5SjnRTBYw0G3hN 5KjPjGcIC62FVSSsk/fRjEwpu/Q5+ITozwa2YL88BeD0G1hqmpRACUmiv9MBi+tkbLeh 9+FcoZd1EXe1tjGbtLpPb2c9LyDacrbbcnd9ufjKlTSvKkwE8dMWs0LcJDSqt3d3XsET XFPFlXUicXjvC30eWHkkZzk6djiAAqxZIRzT4swXGdlYFLwIHWtOL1R8qiK9/gEfZ/St 52G5ohtcGbS5w/ojEE8/8Dmuv4I4Dxu/DXS05fZVWVR5oK73n+tvlPn/0+o6mgU2sf6R Vssg== MIME-Version: 1.0 X-Received: by 10.224.97.7 with SMTP id j7mr7811729qan.81.1390445300523; Wed, 22 Jan 2014 18:48:20 -0800 (PST) Received: by 10.140.87.71 with HTTP; Wed, 22 Jan 2014 18:48:20 -0800 (PST) In-Reply-To: <201401221715.42164.jhb@freebsd.org> References: <201401221715.42164.jhb@freebsd.org> Date: Wed, 22 Jan 2014 18:48:20 -0800 Message-ID: Subject: Re: bhyve and legacy From: Neel Natu To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 02:48:21 -0000 Hi John, On Wed, Jan 22, 2014 at 2:15 PM, John Baldwin wrote: > Is there any interest in supporting more "legacy" setups via bhyve? In > particular, I'd like to take a whack at improving the PCI INTx support, but > that can involve several things such as possibly implementing 8259A support > and a PCI interrupt router vs always assuming that we have APICs. If we do I would love to see PCI INTx support so we can do legacy interrupts for the virtio device models. However, does that require going all the way back to 8259 style interrupts? It should work fine with IOAPIC, no? > want to support a more legacy route, is there interest in supporting a BIOS > interface in the VM? I know that one option is to go grab a BIOS ROM from > something like qemu, but another option is to have the real-mode IDT vector to > stub routines in a very small ROM that traps to the hypervisor to implement > BIOS requests. OTOH, that may turn out to be rather messy. > > Finally, I noticed a comment fly by about removing the need for bhyveload. > One thing I have found useful recently is passing -H to bhyveload. > Specifically, I can build a test kernel outside of the VM on the host and > access it via the host0 filesystem in bhyveload so I can easily test kernels > in the VM while still using the host as my development environment. It would > be nice to retain this ability in some fashion. > Yes, absolutely. best Neel > -- > John Baldwin > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org"