Date: Thu, 23 Oct 2014 15:55:32 -0700 From: Peter Grehan <grehan@freebsd.org> To: Conrad Meyer <cse.cem@gmail.com> Cc: Conrad Meyer <conrad.meyer@isilon.com>, freebsd-virtualization@freebsd.org Subject: Re: [PATCH 1/2] bhyve: Support /domain/bootloader configuration for non-FreeBSD guests. Message-ID: <54498764.6080404@freebsd.org> In-Reply-To: <1414094284-29055-2-git-send-email-cse.cem@gmail.com> References: <1414094284-29055-1-git-send-email-cse.cem@gmail.com> <1414094284-29055-2-git-send-email-cse.cem@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54498764.6080404>