From owner-freebsd-virtualization@FreeBSD.ORG Thu Jan 23 01:16:53 2014 Return-Path: Delivered-To: virtualization@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 38002DC7 for ; Thu, 23 Jan 2014 01:16:53 +0000 (UTC) Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0A148191A for ; Thu, 23 Jan 2014 01:16:52 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id bj1so1169275pad.11 for ; Wed, 22 Jan 2014 17:16:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=gpKhbHumBj6iJnucSHvkOR2HTX0B0OMq0hTWv5imvXA=; b=LEaipaqzbV6Wjcs9S7AkguUlp7LW5bZcIO67xHytqB49fiKkB0fHWspkx2dP7BE1uS UVa5fdSqQMJGrMMIz2mSsqKN74HFKNPjbdEN3jF2Ng74CSGauqdiImobpOtoLJKEs59F ci7KZHHvKwxPutHtZ0/tq7OJKRrA3FkN3UgVVwHEk7+AFMwqeVl4+dfG9bHcDaagikXT pfXhB0nzIhO+JCMctINKNjvKOQZq5LY2UU23I8ddOCRbQZpW/8Vikyvul6nb+qk7CaZP 7l+41YVQNFDjOAZqpg9olwQvggYKciC73/kRXL1/A/xIshLNhIFu02rtxpLqXMw39k02 qMeA== X-Gm-Message-State: ALoCoQmZ/jfzkxGjTHQ2UkiWoSdfrKjb/dnFTBRLIXjhsGE/MaHo8/lBGMqCsWAe/HVxI6Vp11gY X-Received: by 10.66.243.103 with SMTP id wx7mr4838143pac.107.1390439806254; Wed, 22 Jan 2014 17:16:46 -0800 (PST) Received: from [172.16.172.183] (209-6-121-211.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.121.211]) by mx.google.com with ESMTPSA id de3sm29088219pbb.33.2014.01.22.17.16.43 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jan 2014 17:16:45 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: bhyve and legacy From: Tycho Nightingale In-Reply-To: <201401221715.42164.jhb@freebsd.org> Date: Wed, 22 Jan 2014 19:54:47 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <22CF9C41-3320-4E98-A475-A6372799024B@pluribusnetworks.com> References: <201401221715.42164.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1510) Cc: 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 01:16:53 -0000 Hi, Interest? Yes! Matter of fact, I have some scraps of 8259 support = lying around here if you are keen to have a starting point. Now with respect to bhyveload, while it certainly does have some = FreeBSD-specific uses, it is a bit of a barrier to supporting = non-FreeBSD guests and furthermore supporting them well e.g. reboot = without bhyve exiting. If 'true' support existed for booting from an = iso, then with a quick 'mkisofs' you could achieve the same kernel-to-VM = turnaround without bhyveload. Tycho On Jan 22, 2014, at 5:15 PM, John Baldwin wrote: > Is there any interest in supporting more "legacy" setups via bhyve? = In=20 > particular, I'd like to take a whack at improving the PCI INTx = support, but=20 > that can involve several things such as possibly implementing 8259A = support=20 > and a PCI interrupt router vs always assuming that we have APICs. If = we do=20 > want to support a more legacy route, is there interest in supporting a = BIOS=20 > interface in the VM? I know that one option is to go grab a BIOS ROM = from=20 > something like qemu, but another option is to have the real-mode IDT = vector to=20 > stub routines in a very small ROM that traps to the hypervisor to = implement=20 > BIOS requests. OTOH, that may turn out to be rather messy. >=20 > Finally, I noticed a comment fly by about removing the need for = bhyveload. =20 > One thing I have found useful recently is passing -H to bhyveload. =20 > Specifically, I can build a test kernel outside of the VM on the host = and=20 > access it via the host0 filesystem in bhyveload so I can easily test = kernels=20 > in the VM while still using the host as my development environment. = It would=20 > be nice to retain this ability in some fashion. >=20 > --=20 > 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"