Talk:Bhyve
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
Untitled[edit]
Obviously you haven't studied, perhaps not even read Popek and Goldberg's paper. This might be an easy read for you: https://en.wikipedia.org/wiki/Popek_and_Goldberg_virtualization_requirements. According to their paper, "The virtual machine monitor will be a particular piece of software, which we shall call a control program , that exhibits certain properties.", these properties being "The efficiency property", "The resource control property" and "The equivalence property" all of which bhyve exhibits.
As for Type 1 and Type 2 terms they are originating not from Popek and Goldberg's paper but from John Scott Robin's thesis "Analysis of the Intel Pentium’s Ability to Support a Secure Virtual Machine Monitor":
"A Type I VMM runs directly on the machine hardware. It is an operating system or kernel that has mechanisms to support virtual machines. It must perform scheduling and resource allocation for all virtual machines in the system and requires drivers for hardware peripherals."
"A Type II VMM runs as an application on a host operating system and relies on the host OS for memory management, processor scheduling, resource allocation, and hardware drivers."
---
Please don't go lecturing people about things you clearly don't understand. If you had read what you typed above and had some minimal idea about OS implementations you would have figured out that bhyve is clearly a Type II. Let me clarify that for you, bhyve relies on OS memory management, OS processor scheduling, OS resource allocation and OS hardware drivers (by OS here I mean FreeBSD). Does bhyve have it's own memory management? No. Does bhyve have it's own scheduler? No. Does bhyve have it's own resource manager? No. Does bhyve have it's own drivers for hardware devices? No. It uses everything from the host OS (FreeBSD). So now please change the article back.
Definitions of Type I and II are not universally defined. Vmware Esxi is a Type I hypervisor, yet it still uses Linux so is it running directly on "machine hardware"? Yes, but so is FreeBSD. 178.113.155.49 (talk) 22:56, 29 October 2019 (UTC)
- Esxi uses its own Linux based kernel to run on a bare metal, and then a copy of Linux is used as a primary virtual machine, which is quite the opposite to the role of FreeBSD, which provides all the OS services to Bhyve.