but it's still possible for it to bypass the vm
u never know,,,.,......,,
well, it is, but it depends on how the vm is structured. iirc, the virtual machine has no clue that anything exists, in a sense, from outside its little bubble (allocated memory).
let's say that vm_1 is on a hard drive. when it is created, on said hard drive, with a host computer of let's say, windows, to host said vm software, it is given some memory. for sake of example, let's say 50 GB. when it puts aside this memory, as a vm, it essentially assumes that its 50 GB is just the drive itself. you could be using a TB hard drive, but the vm will only be aware of this 50 GB, so it'll think that there's only one OS, just a simple 50 GB main drive that the vm is on.
so let's say you want to take a memory-deleting program that deletes everything on vm_1. let's say it's an ubuntu vm, and you want to run:
sudo rm / -rf
to delete everything on the vm. now, you might think: "holy stuff how does that not kill my whole computer?" simple, the vm is alone on itself, unaware of the rest of your hard drive, other than that 50 GB that it allocated. you could have a stuffton of stuff on the rest of your hard drive - won't do anything, because the vm, vm_1 specifically, is separate from everything on the host computer.
of course, you could argue with file sharing (sharing files with the host computer) and other things like that, you could accidentally delete your host computer, but i doubt anyone is silly enough to actually do that.
this is the best explanation i could think of, please correct me if i'm wrong!
