From owner-freebsd-virtualization@FreeBSD.ORG  Thu Oct 23 22:56:53 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id EDE72E6C
 for <freebsd-virtualization@freebsd.org>; Thu, 23 Oct 2014 22:56:53 +0000 (UTC)
Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12])
 by mx1.freebsd.org (Postfix) with ESMTP id AEDFEE1D
 for <freebsd-virtualization@freebsd.org>; Thu, 23 Oct 2014 22:56:53 +0000 (UTC)
Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57])
 by alto.onthenet.com.au (Postfix) with ESMTP id 3871E12790;
 Fri, 24 Oct 2014 08:55:36 +1000 (EST)
Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210])
 by dommail.onthenet.com.au (MOS 4.4.4-GA)
 with ESMTP id BZF00611 (AUTH peterg@ptree32.com.au);
 Fri, 24 Oct 2014 08:55:34 +1000
Message-ID: <54498764.6080404@freebsd.org>
Date: Thu, 23 Oct 2014 15:55:32 -0700
From: Peter Grehan <grehan@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Conrad Meyer <cse.cem@gmail.com>
Subject: Re: [PATCH 1/2] bhyve: Support /domain/bootloader configuration for
 non-FreeBSD guests.
References: <1414094284-29055-1-git-send-email-cse.cem@gmail.com>
 <1414094284-29055-2-git-send-email-cse.cem@gmail.com>
In-Reply-To: <1414094284-29055-2-git-send-email-cse.cem@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Conrad Meyer <conrad.meyer@isilon.com>, 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."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Oct 2014 22:56:54 -0000

Hi Conrad,

> 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 
unmodified 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 
by 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.

later,

Peter.