Understanding Virtualized Machine Components CCNA Certification
Whenever a new virtual machine is created, some necessary hardware components are allocated through the use of software emulation. Think about it. Whenever you use an individualized operating system, it has to access its own hard drive, network card, and system memory. Some of these components are vital for operation. Say, for instance, you’re running an instance of SUSE Linux, and you’re going to be using this instance of Linux to run a website that takes advantage of PHP Hypertext Preprocessor (PHP). To do this, you?d need to have an individual installation that had its own Mcsa Exams network settings, memory, and disk. Imagine for a moment that this is a medium-traffic web server. The I/O operations alone would be dif?cult for a single server to hold, but since this is a consolidated and ?hypervised? (monitored by Hyper-V) system, it’s even harder to maintain.
A lot of the reason behind this is that although there may be two operating systems running two of every single operating component, on most low-end, low-cost servers there is only one memory bus, or one memory card, and maybe even one RAID Configuration. And that isn?t likely to change. Thus, the hypervisor has the task of determining where the resources are allocated. At times, this can be very complicated.
Thankfully, most of what the hypervisor does has been automated to a point that it doesn?t require much administrative work on the part of the lowly administrator who has been tasked with designing a consolidated server role. Really, using Hyper-V is as simple as opening up the virtualization management console (VMC).
The VMC in Windows Server 2008 is called the Hyper-V Manager. Using the Hyper-V Manager, you’re allowed access to the central brains of the hypervised machines. Here, you can create new virtualized machines, take snapshots, manage the licensing, and alter the hard-ware settings discussed earlier.
If you’ve used Windows XP or Windows Vista, a snapshot is pretty easy to understand. In a way, it’s similar to a system restore. A VM snapshot gives you the ability to take a ?photo?at a certain time of the condition of that virtualized operating Comptia Security system. The mother operating system (Windows Server 2008 when using Hyper-V) has the virtual machine record a data list of all its settings that will allow you to roll back to the previously estab- lished settings within Hyper-V at any point. So, if for some reason your virtual machine stops working, you can revert to a snapshot and continue working unimpeded as if nothing ever happened. Of course, any changes made after the snapshot will be lost. But part of the real advantage of snapshots is that you can decide where you want to place them on the system. This is useful if you want to deposit a snapshot on an external resource, such as a networked drive or external hard drive, for recovery purposes.
Processing your request, Please wait....
