Anatomy of Virtual Machine
- To create vms we need hypervisor to be installed on physical servers.
- Hypervisor creates virtual cpu, virtual ram and virtual disk with os in it. when this machine starts it behaves like a physical machine
- Every cloud uses a customized hypervisor to create virtual machines
- AWS => Nitro Hypervisor
- Azure => Azure Hypervisor (Hyper-V)
- GCP => Customized KVM
Azure VM and what it has/needs
- Overview
- Azure vm is connected to a subnet via network interface which recieves a private ip address and optional public ip
- A firewall around network interface called as network security group will be attached
- VM will get cpu and RAM according the size selected
- A disk will be attached to vm
- IF the disk has os it is referred as OS Disk (mandatory) additional disks are referred as data disks.
AWS EC2 and what it has/needs
- Overview
- AWS will have an existing default vpc in all regions
- AWS EC2 instance will be connected to network in subnet via network interface (elastic network interface) which gets an private ip and optional public ip.
- A firewall around network interface called as security group will be attached
- ec2 instance will get cpu and RAM according the instance type selected
- A ebs volume disk will be attached to ec2 instance
- IF the ebs volume has os it is referred as root ebs volume k (mandatory) additional ebs volumes can be attached.
