Jump to content

I am having trouble understa.ding how a type 1 hypervisor is a virtual machine. If it loads before the boot OS, how is it not simply acting as a partition? I have installed a separate OS in a partition and on a Bootable flash drive. I have experience using virtualbox (type2) where you install the OS on top of the boot OS. This makes sense to me bc you run it on allocated system partitions on top of windows. But a type one is installed before your boot OS, which does not seem to be a VM but a separate Bootable OS still using your own hardware. What am I missing?.

Link to comment
https://linustechtips.com/topic/1579952-type-1-hypervisor-question/
Share on other sites

Link to post
Share on other sites

1 hour ago, Wmbailey96 said:

 What am I missing?.

You are missing that a hypervisor is NOT a VM. It is a hypervisor. Like you said yourself. It is essentially an OS that allows you to load other virtual OS's (VM's) onto it.

Link to post
Share on other sites

15 hours ago, Wmbailey96 said:

I am having trouble understa.ding how a type 1 hypervisor is a virtual machine. If it loads before the boot OS, how is it not simply acting as a partition? I have installed a separate OS in a partition and on a Bootable flash drive. I have experience using virtualbox (type2) where you install the OS on top of the boot OS. This makes sense to me bc you run it on allocated system partitions on top of windows. But a type one is installed before your boot OS, which does not seem to be a VM but a separate Bootable OS still using your own hardware. What am I missing?.

You’re over complicating this. 
 

A type 1 hypervisor is simply an operating system which is intended to host VM’s. Proxmox is a type 1 hypervisor. Proxmox runs bare metal. 
 

Proxmox is *basically* just Debian and some fancy webUI features for Linux KVM virtualization. 
 

Once proxmox is installed and up and running, you instal VM’s under proxmox. 
 

A type 2 hypervisor is simply a program you instal on an already running OS… like you can instal virtual box on top of windows. Windows in this instance is not the hypervisor, but you have installed an application under it that is hosting VM’s. Windows is installed bare metal, and within windows you have installed an application (virtual box) which is then hosting VM’s. 

Rig: i7 13700k +Contact Frame - - Asus Z790-P Wifi - - RTX 4080 - - 4x16GB 6000MHz - - Samsung 990 Pro 2TB NVMe Boot + Main Programs - - Crucial P3 2TB NVMe for photo work - - Corsair RM850x - - Sound BlasterX EA-5 - - Corsair XC8 JTC Edition - - Corsair GPU Full Cover GPU Block - - PTM 7950 - - XT45 X-Flow 420 + UT60 280 rads externally mounted - - EK XRES RGB PWM - - Fractal Define S2 - - DellAlienware AW3423DWF 34" -- Logitech Pro X Superlight - - Logitech G710+ - - LTT Northern Lights Deskpad

 

Headphones/amp/dac: Schiit Bifrost Multibit - -  Schiit Lyr 3 - - Fostex TR-X00 - - Sennheiser HD 6xx

 

Homelab/Media Server: Proxmox VE host - - 512 NVMe Samsung 980 RAID Z1 for VM's/Proxmox boot - - Xeon e5 2660 V4- - Supermicro X10SRF-i - - 128 GB ECC 2133 - - 10x8TB WD Red RAID Z2 - - 2x 800 GB SAS SSD’s (1 SLOG, 1 L2Arc) - - 45 HomeLab HL15 15 Drive 4U - - Corsair RM650i - - LSI 9305-16i HBA - - TreuNAS + many other VM’s

 

Unifi UDM Pro in front of full unifi network infrastructure

 

iPhone 17 Pro - - MacBook Air M3

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×