![]() With these bits, the player has everything it needs to power on and run a virtual machine. The config file tells the player “this VM has 2GB of RAM, 1 CPU, and a fake sound card.” The other important part of the config file is that is tell the player: “When you need to access the disk for this virtual machine, use this file called disk1.vmdk instead”. A virtual machine is just a directory with a configuration file and bunch of virtual disk files. Think of the VMware Fusion software as a “player”. From the point of view of your Windows install, when you boot from Bootcamp then shut down and later boot from Fusion, it looks just like you moved the hard drive between computers. Virtualization software like Fusion or Parallels can use either a file-based virtual disk, or a raw disk partition as source of the virtual disk. Please don’t nitpick with comments like: “ITS NOT PARTITION 2 YOU IDI0T!!!” I’ll say upfront that this is not completely technically accurate and I have left out some bits on purpose. No one asked but enough people have talked about it that I thought I would follow up on the "bootcamp vs running a VM" discussion with an explanation of what is going on under the hood (this is Fusion specific, but most of the important details are the same) that makes this work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |