Category: technical

Part 2: How to install macOS Big Sur 11.4 using VirtualBox on Windows

Note:

You might replace your “Big Sur” with your own virtual Machine

This code is for:

https://youtu.be/tJgNCyhqdBo

DOWNLOAD Here Code

Code for VirtualBox 6.x Intel CPU

cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage.exe modifyvm "Big Sur" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

Code for Virtualbox 6.x AMD CPU 

cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage.exe modifyvm "Big Sur" --cpu-profile "Intel Core i7-6700K" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "Big Sur" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

Docker[Containers] vs Hypervisor[Virtual Machines]

Virtualization Technologies

Docker vs Hypervisor — Containers vs Virtual Machines

Wednesday, April 21, 2021

Category \ TechnologyDocker [Containers]Hypervisor [Virtual Machines]
Docker vs. Virtual Machines  
OS Support and ArchitectureNo Guest OS, Docker containers hosted on a single physical server with a host OS, which shares among them. Sharing the host OS between containers makes them light and increases the boot time. Docker containers are considered suitable to run multiple applications over a single OS kernel.Host OS and the Guest OS inside each VM. Guest OS can be any OS, like Linux or Windows, irrespective of host OS.
   
SecurityProviding root access to applications and running them with administrative premises is not recommended in the case of Docker containers because containers share the host kernel. The container technology has access to the kernel subsystems; as a result, a single infected application can hack the entire host system.Virtual machines are stand-alone with their kernel and security features. Applications needing more privileges and security run on virtual machines. 
   
PortabilityDocker containers packages are self-contained and can run applications in any environment, and since they do not need a guest OS, they can be easily ported across different platforms. Also, containers being lightweight [MBs] can be started and stopped in very less time compared to virtual machinesVMs are huge in size [GBs] because each include standalone OS. Not easy moved to a different platform without incurring compatibility issues.
   
   
     
Category \ TechnologyDocker [Containers]Hypervisor [Virtual Machines]
Docker vs. Virtual Machines  
PerformanceThe lightweight architecture of Docker containers is less resource-intensive than virtual machines. Most times one application per Container.VMs are more resource-intensive than Docker containers as the virtual machines need to load the entire OS to start. One OS in each VM, and usually many apps running in this OS.
   
Boot-TimeBoots in a few seconds.It takes a few minutes for VMs to boot.
   
Runs onDockers make use of the execution engine.VMs make use of the hypervisor.
   
Memory EfficiencyNo space is needed to virtualize, hence less memory.Requires entire OS to be loaded before starting the surface, so less efficient, more memory.
   
IsolationProne to adversities as no provisions for isolation systems.Interference possibility is minimum because of the efficient isolation mechanism.
   
DeploymentDeploying is easy as only a single image, containerized can be used across all platforms.Deployment is comparatively lengthy as separate instances are responsible for execution
   
UsageDocker has a complex usage mechanism consisting of both third party and docker managed tools.Tools are easy to use and simpler to work with.
   
Reuse of Resources and LibrariesDocker Containers can reuse Resources and Libraries from other Containers, taking less disk space.No reuse between VMs, Redundant copies exist, demanding more disk space.

Usually, Organizations are making use of the hybrid approach mostly as the choice between virtual machines and Docker containers depends upon the kind of workload offered.

Hypervisor-2 vs Docker

Hypervisor-1 vs Docker

Docker

Hypervisor-2 vs Hypervisor-1

Note: Hypervisor 1 [Servers mainly] vs Hypervisor 2 [Desktop mainly]

VM Hypervisor-2 vs Docker [Linux] vs Docker [VM Linux]