From owner-freebsd-virtualization@FreeBSD.ORG Thu Oct 23 23:16:19 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD1254AC; Thu, 23 Oct 2014 23:16:19 +0000 (UTC) Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D16CFDD; Thu, 23 Oct 2014 23:16:19 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id dc16so226326qab.6 for ; Thu, 23 Oct 2014 16:16:18 -0700 (PDT) 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:content-transfer-encoding; bh=ihr/wlPTcDcDR75a6BTtSL34TkdYWFmRPGgluavaf7o=; b=dEApNhrzcL+GaALY6EcHskWnV3Bu2UyTglGLL6OKs4K8Q6Iu0Kl3RwwqeGM5HXR/7o IKAIS4mRKXK0ImKgS2/r4lovQzJLhW22VqkldivXUjkIs8yeqoO3lRyogZ0ih50TD2xS GcUgTHBshxuwBLAskrguGa2nnjsuycb+y5XQaD5FpfMIKakkE8UEPYPkM8SCSUkHaSD1 c/bOnJixq43ntMut/73dMCsBJ9y9VnFtEU8uYYr7KlvgW7xoNiBJJJwVtEVBNforWCEK KhpH0wongjEZT3+FdhGvzktKU941SNM63s/g69O2dLI9SWD86l7bJ2mjdqqJTE9BP410 NaHg== MIME-Version: 1.0 X-Received: by 10.170.60.197 with SMTP id c188mr584737ykc.61.1414106178427; Thu, 23 Oct 2014 16:16:18 -0700 (PDT) Received: by 10.220.150.68 with HTTP; Thu, 23 Oct 2014 16:16:18 -0700 (PDT) In-Reply-To: <54498764.6080404@freebsd.org> References: <1414094284-29055-1-git-send-email-cse.cem@gmail.com> <1414094284-29055-2-git-send-email-cse.cem@gmail.com> <54498764.6080404@freebsd.org> Date: Thu, 23 Oct 2014 19:16:18 -0400 Message-ID: Subject: Re: [PATCH 1/2] bhyve: Support /domain/bootloader configuration for non-FreeBSD guests. From: Conrad Rad To: Peter Grehan Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Conrad Meyer , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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 Oct 2014 23:16:19 -0000 On Thu, Oct 23, 2014 at 6:55 PM, Peter Grehan wrote: >> Also, flip Bhyve /domain/os/type support from HVM to Xen. Bhyve only >> supports paravirtualized guests, and 'xen' is closest to that. > > That's not true: bhyve has enough h/w emulation required to run unmodifi= ed > guests - there are register-level emulations of the local APIC, I/O APIC, > PIT, PIC, RTC, HPET, APCI timer, PCI/PCIe support, and AHCI. > > While virtio devices may be categorised as PV, in reality they're seen b= y a > guest o/s as PCI devices and can be considered HVM. > > The bhyveload/grub-bhyve user-space loaders are an artifact of how bhyve > was initially developed - they will be made redundant when the UEFI work = is > done, at which point bhyve will have a BIOS. Hi Peter, I'm happy to drop the hvm -> xen changes. I'll need to change the domain parsing code to allow hvm domains to set options =E2=80= =94 currently it only allows xen domains to do so. Unless I'm mistaken, the userspace loaders are still needed to boot VMs for now. Will the Bhyve UEFI work be complete before MeetBSD? And is it going into the FreeBSD 10 release branch, or only in 11? Until that code actually materializes, I think it's important to fix libvirt now. This change doesn't break a future Bhyve-that-supports EUFI, and it can even be yanked out later if totally redundant. Until UEFI support materializes, Linux guests are broken in libvirt-bhyve. I'll rework and submit a v2. Thanks, Conrad