Type 1 Hypervisor: It is run on actual hardware. OS running on each VM is called as Guest OS. In each VM we can run various OS, software and libraries which are unique to each VM. This virtualization software component transforms physical hardware into software and shares with VM. To achieve this we need a virtualization software component. In the case of virtualization, we can set up multiple machine(virtual) in a single physical machine. They can produce something to improve that aspect slightly.Without VM: Single OS owns all hardware resources. You do get something called host profiles, which they've also improved slightly, however, I still think it's a bit clunky in terms of the way you can manage it. That's caused a number of issues already. That's one of the key things that I need really, from a support perspective. I would say for me personally, the management aspect with large memory and in-memory databases for the motions and stuff like that is what it needs. We are always sort of one or two versions behind. That's a big pain point that the firmware management of the underlying hardware should handle. VMware doesn't really cater to it, however, Nutanix to some degree does cater for.
That said, one of the problems is that when we're sort of behind big memory servers and the databases in them if you migrate it, it potentially breaks the system off.
If you have to do firmware upgrades, it's organizing downtime and all sorts of things, which normally in a VMS space isn't an issue. They have embedded some of this in 7.1, however, I haven't tested it or seen it in action as yet. It's an in-memory database and that can sometimes cause issues. The biggest thing is the firmware upgrades and other items at the backend. The biggest pain point is probably the firmware management of the underlying hardware.
0 kommentar(er)
