Other posts related to virtualisation

Red Hat Virtualization 2.2 v2v

 | Friday, 25. June 2010 17:29

Red Hat Virtualization 2.2 introduce v2v for XEN and Vmware ESX

http://www.redhat.com/promo/summit/2010/highlights/

Share

Red Hat Enterprise Linux 5.5

 | Thursday, 1. April 2010 17:03

Mit Red Hat Enterprise Linux 5.5 wird im Bereich Virtualisierung einiges geändert  / ergänzt.

siehe auch die Release Notes:

http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.5/html-single/Release_Notes/#id543727

Share

Red Hat Enterprise Virtualization 2.2 migriert VMs

 | Tuesday, 30. March 2010 17:55

16 Cores und 256 GB Memory per Gast ist doch nicht zu verachten bei der neuen RHEV 2.2 ! Das ist einiges mehr als bei vielen anderen Lösungen wie Vmware 4.0 oder auch Citrix XenServer aber auch Microsoft Hyper-V ist noch nicht soweit.

Gutes Video zum Erklähren von Virtualisierung

Share

The Linux Kernel should also be a Hypervisor…

 | Sunday, 7. March 2010 23:57

As a Linux developer, it’s hard for me to be that interested in Xen…
When you think about it, it is really quite silly. We advocate Linux for
everything from embedded systems to systems requiring real-time
performance, to high-end mainframes. I trust Linux to run on my dvd
player, my laptop, and to run on the servers that manage my 401k.
Is virtualization so much harder than every other problem in the
industry that Linux is somehow incompatible of doing it well on its own?
Of course not.
– Anthony Liguori, Qemu maintainer

Share

Virtualisation with Linux

 | 23:45

After lot of googeling in the Internet for some Basics about Virtualistion with Linux / Windows I collect some links abhout this.

One good Description why they choice KVM was the following from http://www.elastichosts.com/cloud-hosting/infrastructure

Why we chose KVM virtualization

Before selecting Linux KVM, we evaluated VMWare and Xen, two other virtualization platforms providing similar capabilities to KVM (Virtuozzo only provides OS-level containers). We selected KVM as the best architecture for virtualization on modern processors with fast hardware virtualization support (VT-x and NPT on Intel or AMD-V and EPT on AMD).
Increasing hardware virtualization support

* Historically, virtualization platforms used software to trap and simulate certain instructions, memory management and I/O in the host virtual machines. VMWare was an early leader in this software technology.
* With the first generation of hardware virtualization, the VT-x/AMD-V extensions trapped these instructions in hardware, giving a significant speed improvement. However, virtualized memory management and I/O remained bottlenecks. Xen was an early proponent of paravirtualization, which attacks those bottlenecks by modifying the host operating system at compile time.
* With the second generation of hardware virtualization, the NPT/EPT extensions minimize the memory management bottleneck. As a result, MMU paravirtualization is a legacy approach, leaving just scheduling and I/O to be virtualized in software by a hypervisor. (I/O virtualization requires a good set of device drivers for the underlying hardware, of course: an area in which Linux excels.)

Hypervisor architecture and device drivers

* Linux KVM is a hypervisor which is built into mainline Linux. It uses the full range of hardware virtualization support, and directly uses the regular Linux scheduler and I/O device drivers.
* Xen runs an external hypervisor for scheduling, and uses a modified Linux kernel in domain 0 to provide device drivers.
* VMWare runs a proprietary external hypervisor, which includes scheduling and device drivers, many of which are adapted from Linux.
* We believe the KVM architecture is superior to both Xen and VMWare, since the mainline Linux scheduler and device drivers are both extremely well designed, widely deployed, professionally maintained and throughly tested, to a level likely well above what a single company can achieve on either their own proprietary codebase or locally maintained fork of Linux.

http://en.wikipedia.org/wiki/Comparison_of_platform_virtual_machines

http://www.ibm.com/developerworks/linux/library/l-hypervisor/index.html

Cloud Links:

http://aws.typepad.com/aws/2010/01/new-whitepaper-architecting-for-the-cloud-best-practices.html

http://www.allthingsdistributed.com/2009/08/amazon_virtual_private_cloud.html

http://www.jroller.com/MasterMark/entry/the_enterprise_cloud

http://www.linuxjournal.com/article/9915


Generel Virtualisation:

http://www.elastichosts.com/cloud-hosting/infrastructure

http://berrange.com/posts/2010/02/15/guest-cpu-model-configuration-in-libvirt-with-qemukvm/

http://blog.codemonkey.ws/2008/05/truth-about-kvm-and-xen.html

http://avikivity.blogspot.com/

http://docs.fedoraproject.org/virtualization-guide/f12/en-US/html-single/

http://virtualization.com/

http://www.redbooks.ibm.com/abstracts/tips0718.html

http://www.brocade.com/downloads/documents/white_papers/FCoE%20AT%20A%20Glance.pdf

http://virtualization.sys-con.com/

http://developer.novell.com/wiki/index.php/Virtual-bus

http://www.kernel.org/doc/ols/2007/ols2007v2-pages-173-178.pdf

http://virtualizationreview.com/Blogs/Mental-Ward/2009/02/KVM-BareMetal-Hypervisor.aspx

http://wiki.qemu.org/Main_Page

http://www.redhat.com/promo/svvp/

Share

XEN <--> KVM

 | Monday, 25. August 2008 13:48

Obwohl Xen immer wieder updates liefert ist für mich nicht so klar wohin die Reise mit XEN geht. Da es nicht im Kernel ist braucht es immer spez. Arbeit um für einen aktuellen Kernel. Auch die Uebernahme durch Citrix vereinfacht die Sache nicht gerade. KVM scheint dagegen grosse Chancen zu haben, da wohl im nächsten RHEL Release KVM anstatt XEN verwendet wird. Auch braucht es keinen spez. Kernel oder abhänigkeiten, da es upstream drin ist. Bei allen aktuellen Red Hat Virtualisierungsprojekten wird immer auf KVM geschaut: ovirt.org http://genome.et.redhat.com/

Share