Different Types of Virtualization

preview_player
Показать описание
In this video I discuss different forms of virtualization (mostly type 1, type 2 hypervisors and containers)

₿💰💵💲Help Support the Channel by Donating Crypto💲💵💰₿

Monero
45F2bNHVcRzXVBsvZ5giyvKGAgm6LFhMsjUUVPTEtdgJJ5SNyxzSNUmFSBR5qCCWLpjiUjYMkmZoX9b3cChNjvxR7kvh436

Wownero
WW3AbGBJtdSJEhRhRZYiPEUdyPZqVQaUFb4XmvafJ7SaiXmEuzV14Zw7UZGVxNJvF1jVDQd8UXxyXV6T5v4bYPV82WayFzwkc

Bitcoin
3MMKHXPQrGHEsmdHaAGD59FWhKFGeUsAxV

Ethereum
0xeA4DA3F9BAb091Eb86921CA6E41712438f4E5079

Litecoin
MBfrxLJMuw26hbVi2MjCVDFkkExz8rYvUF

Dash
Xh9PXPEy5RoLJgFDGYCDjrbXdjshMaYerz

Zcash
t1aWtU5SBpxuUWBSwDKy4gTkT2T1ZwtFvrr

Chainlink
0x0f7f21D267d2C9dbae17fd8c20012eFEA3678F14

Bitcoin Cash
qz2st00dtu9e79zrq5wshsgaxsjw299n7c69th8ryp

Etherum Classic
0xeA641e59913960f578ad39A6B4d02051A5556BfC

USD Coin
0x0B045f743A693b225630862a3464B52fefE79FdB

and be sure to click that notification bell so you know when new videos are released.
Рекомендации по теме
Комментарии
Автор

I run all my software within my turning complete Minecraft Redstone computer. it is always safe to do so, not many viruses have gotten through my actual system yet.

__-kdoz
Автор

I like how he just gets straight to the point

sobot_
Автор

Mental Outlaw, the man carrying me through my cybersecurity degree.

spectraljake
Автор

For those still not clear on the container-based virtualization (CBV) and hypervisor-based virtualization (HBV).
CBV like Docker virtualize the OS. It captures system/kernel calls, like opening file handles, making network sockets, making new threads etc. and translates these system calls to the native host's system calls. There is no separate guest OS running for the guest application. The application runs directly on the host OS, but it can't access other files and folders because it is namespace-isolated. The "/" directory for the guest application might be "/home/username/appname/" for you.

HBV like VirtualBox, QEMU, VMware and more virtualize the hardware instead of the OS. So you do in fact run a guest OS on top of your host OS. System calls are not translated for the guest app, it talks directly to the guest OS. It is when the guest OS tries to fulfil the system call by talking to hardware, is when the hypervisor comes into play. When the guest OS for example wants to read sector X of your HDD, it translates that to what location in the actual, physical HDD it belongs to, and then the corresponding file is requested by the hypervisor from the host OS (for type-2, in type-1 the hypervisor is also the host OS so it simply reads the corresponding sector itself), gets the file, read the right location, and return it back to the guest OS, which returns it to the guest app. You can see why this might be slow.

(CBV and HBV are not actual abbreviations, I just made them up for my own convenience.)

VivekYadav-dsoz
Автор

Perfect timing with the Windows 11 leak

zekiz
Автор

the matrix is the only kind of virtualization

Eduardo-sbkp
Автор

During my school days virtualization was so annoying. Making whole VM network was a pain.. but I'm time I start to see pros and cons of it. Nowadays I can't live without for example proxmox. This tech became so convinient ...

grabarzponury
Автор

One thing that I noticed is that VirtualBox works pretty good inside Windows even in a low end machine, but on Linux for whatever reason it's incredible slow, at least for me. Then I tried Qemu + KVM and boom, loading and installation times got really fast. Unfortunately the graphics virtualization just sucks unless you do a PCI passthrought. But honestly on Linux the best virtualization experience is going to be with Qemu with virt-manager.

estevaomendes
Автор

Hypervisers Type 1 0:00
Xen & Qubes OS 2:00
Type1 vs 2 vs 1.5 3:43
Type 2 4:50
Docker 7:23

Gzussss
Автор

An episode on Qubes would be really cool

josephmauck
Автор

kvm is actually for type-1 virtual machines. Installing it effectively turns the "host" operating system into a type-1 hypervisor, since all hypervisors do need basic OS features. The difference is that you still have complete access to the underlying components since they are just a linux OS, so you can trat it as if it is a type-2 virtualizer if you want to.

joesmith
Автор

containers are not related to virtualization at all, they are native applications running natively on the host hardware, even using the same kernel, they are just as separated from all the other components of the system (security-wise) as possible.

they can have similar limits (like RAM, CPU, etc.), and serve similar purposes like virtualization, but they are not the same kind. not at all.

semmu
Автор

So, I feel the need to be pedantic. VirtualBox's BIOS is GPLv2, and easily visible in the source tree, in src/VBox/Devices/PC/BIOS (for BIOS) or src/VBox/Devices/EFI/Firmware (for EFI).

rallias
Автор

I feel like that 10 minute explanation was exactly what I needed I got so much information it was unreal. I was looking at type one hypervisors and wanted to know a little more about them.. Yeah this put a lot of information into perspective and I highly recommend this video for learning more about virtualization.

acejinwoo
Автор

gpu passthrough with qemu-kvm is the best thing ever

onlyVetements
Автор

PCI-e passthrough is a pain to deal with sometimes, but whenever it works it's amazing. I tried to pass a quad gigabit nic from Proxmox to a VM, but the card was on the same IOMMU group as the internal NIC so it passed in both and I lost access to the Proxmox web gui, later I found out that it's impossible to seperate them because of the electrical wiring on the motherboard itself. Fun times.

MrSpecialR
Автор

Can you do QEMU tutorial? All the ones I'm finding are bad and the documentation is not beginner friendly.

MrFlox
Автор

Bit of a clarification: As far as the type 1 hypervisor for VMware goes, that'd be ESXI. Vsphere is the configuration manager.

watawata
Автор

i like your comment about security through obscurity!

Zahna
Автор

This might be helpful for the SEC+ cert I'm currently studying for thanks!

sethbingo