Исходное сообщение
"Релиз Xen Cloud Platform (XCP) 1.6" Отправлено Аноним, 28-Ноя-12 00:11
> RedHat и Убунту (тоже вроди) перешли на KVM. > Видать не зря. Какая выгода от нового Ксена? http://theinvisiblethings.blogspot.ru/2012/09/how-is-qubes-o... We think Xen is unique because it combines an elegant architecture (type I, baremetal, hypervisor) with a number of practical features, such as power management, support for Intel VT-d and driver domains, support for both para-virtualizaed, and fully-virtualized VMs, and many more, not found in e.g. academic microkernels/hypervisor projects, that otherwise seem attractive from the architecture point of view. Много интересного про Xen vs KVM можно найти в http://qubes-os.org/files/doc/arch-spec-0.3.pdf Xen hypervisor is very small comparing to Linux kernel (KVM), which makes it substantially easier to audit for security problems. Xen allows to move most of the “world-facing” code out of Dom0, including the I/O emulator, networking code and many drivers, leaving very slim interface between other VMs and Dom0. Xenʼs support for driver domain is crucial in Qubes OS architecture. KVM relies on the Linux kernel to provide isolation, e.g. for the I/O emulator process, which we believe is not as secure as Xenʼs isolation based on virtualization enforced by thin hypervisor. KVM also doesnʼt support driver domains.

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	>> RedHat и Убунту (тоже вроди) перешли на KVM. >> Видать не зря. Какая выгода от нового Ксена? > http://theinvisiblethings.blogspot.ru/2012/09/how-is-qubes-os-different-from.html > We think Xen is unique because it combines an elegant architecture (type > I, baremetal, hypervisor) with a number of practical features, such as > power management, support for Intel VT-d and driver domains, support for > both para-virtualizaed, and fully-virtualized VMs, and many more, not found in > e.g. academic microkernels/hypervisor projects, that otherwise seem attractive from the > architecture point of view. > Много интересного про Xen vs KVM можно найти в http://qubes-os.org/files/doc/arch-spec-0.3.pdf > Xen hypervisor is very small comparing to Linux kernel (KVM), which makes > it substantially easier to audit for security problems. Xen allows to > move most of the “world-facing” code out of Dom0, including the > I/O emulator, networking code and many drivers, leaving very slim interface > between other VMs and Dom0. Xenʼs support for driver domain is > crucial in Qubes OS architecture. KVM relies on the Linux kernel > to provide isolation, e.g. for the I/O emulator process, which we > believe is not as secure as Xenʼs isolation based on virtualization > enforced by thin hypervisor. KVM also doesnʼt support > driver domains.
	Введите код, изображенный на картинке: