Redhat Enterprise Virtualization

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras vitae purus eros. Sed lacinia eros lectus, ac pretium ligula.

Category:

Science & Technology

Tags:

• red
• hat
• virtual
• technology
• software
• data
• management
• system
• office
• flash
• demo
• systems
• information
• security
• design
• computer
• solutions
• customer
• training

[areefrakhangi]

Its like a car with more space but same engine. Its upto the car owner to decide how much weight should be put. Its not the problem of the software but rather of the administrators and companies who try to use it the wrong way. Also if properly planned and implemented there will rather be less problems and more memory is available to the operating system. Without a proper plan you are bound to fail.

[stevenabb]

From my previous comments.... What really happens is that instead of having one operating system per server, companies have multiple operating systems per server. When the server hardware crashes (example 80 O.S. Images ) it all goes down. As for the fail over modes, applications like Oracle and SAP get screwed up. It's great for development environments and testing. Labor costs... with 100 servers, each with 80 images, that is 8000 operating systems. Each O.S. still requires some staff time.

[stevenabb]

Here are the virtualization pitfalls never discussed. First, there comes the almost uncontrollable growth of virtual images (like fungus) that eat resources and are abandoned for months. Another pitfall, nobody really pays attention to system utilization so the "spare servers" are also jam packed full, nowhere to fail to. On that note, if one piece of hardware goes down, dozens of "virtual servers" and applications die instantly. It's ok for developement and quality assurance but not production.