Dear Wiki user, You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification. The following page has been changed by KarstenWade: http://fedoraproject.org/wiki/Docs/Beats/Virtualization?action=diff&rev2=58&rev1=57 The comment on the change is: be wary of "allow you to"; it's a sign that i) it needs to be removed, and ii) the sentence can be tighter. ;-) ------------------------------------------------------------------------------ Virtualization in Fedora [[GetVal(DocsDict,BeatsVer)]] has some major changes, and new features, that continue to support the Xen and KVM platforms: - * paravirt ops in the kernel: previously, the Xen kernel was created by forward-porting Xen bits from the 2.6.18 kernel into the current Fedora kernel. This was an arduous task, that was labor intensive, and resulted in the Xen kernel being several releases behind the bare-metal kernel. The inclusion of paravirt ops means that this process is no longer necessary. Once paravirt ops is merged upstream, it will no longer be necessary to have a separate kernel for Xen. + * The story of paravirt ops in the kernel: previously, the Xen kernel was created by forward-porting Xen bits from the 2.6.18 kernel into the current Fedora kernel. This was an arduous task, that was labor intensive, and resulted in the Xen kernel being several releases behind the bare-metal kernel. The inclusion of paravirt ops means that this process is no longer necessary. Once paravirt ops is merged upstream, it will no longer be necessary to have a separate kernel for Xen. - * Improved storage management: previously, Fedora introduced the ability to manage existing guest domains remotely using `libvirt`. It was not possible to create new guests due to the lack of storage management capabilities. In Fedora [[GetVal(DocsDict,BeatsVer)]], new storage management tools allow you to to create and delete storage volumes from a remote host using `libvirt`. + * Improved storage management: previously, Fedora introduced the ability to manage existing guest domains remotely using `libvirt`. It was not possible to create new guests due to the lack of storage management capabilities. In Fedora [[GetVal(DocsDict,BeatsVer)]], new storage management can create and delete storage volumes from a remote host using `libvirt`. * PolicyKit integration: previously, the `virt-manager` application ran as root when managing a local hypervisor, and used `consolehelper` to authenticate from a desktop session. Running GTK applications as root is bad practice. By integrating with PolicyKit, it is now possible to run `virt-manager` as a regular user. * Improved remote authentication: previously, Fedora introduced support for secure remote management using TLS/SSL, and x509 certificates. Fedora [[GetVal(DocsDict,BeatsVer)]] improves remote management capabilities, by adding support for authentication against a username and password database, Kerberos domain controller, or system authentication using PAM. This feature applies to all tools using `libvirt`. - * A new P2V tool, shipping as a Live CD, which allows you to convert a bare-metal install to a virtual guest. + * A new P2V tool, shipping as a Live CD, for converting a bare-metal install to a virtual guest. - * A new tool, `xenner`, that allows you to run Xen-paravirtual kernels on top of KVM. + * A new tool, `xenner`, for running Xen-paravirtual kernels on top of KVM. * Storage and network paravirtual-drivers for KVM guests. * Full support for monitoring network and block statistics of QEMU and KVM has been added to `libvirt` and `virt-top`, bringing parity with statistics monitoring, previously only available to Xen guests. -- Fedora-relnotes-content mailing list Fedora-relnotes-content@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-relnotes-content
