From Fedora Project Wiki

(112 intermediate revisions by 16 users not shown)
Line 1: Line 1:
[[Category:Release Notes]]
== Virtualization ==
Virtualization in Fedora 11 includes major changes, and new features, that continue to support KVM, Xen, and many other virtual machine platforms.
[[Category:Docs Project]]
[[Category:Draft documentation]]
=== Improved VNC Authentication for Virtual Machine Management ===
[[Category:Documentation beats]]
Fedora 11 introduces the ability to use the <code>SASL</code> protocol
for authenticating <code>VNC</code> connection to <code>KVM</code>
and <code>QEMU</code> virtual machines. <code>SASL</code> is a pluggable
system, allowing many different authentication mechanisms to be configured
without changing the application code. The use of <code>SASL</code>, in
combination with existing <code>TLS</code> encryption support, will allow clients like
<code>vinagre</code>, <code>virt-viewer</code> and <code>virt-manager</code>
to securely connect to remote virtual machine consoles hosted on Fedora
servers. In environments where Kerberos is deployed, this further allows for
secure single sign on to the <code>VNC</code> server. This new authentication
capability obsoletes the traditional <code>VNC</code> password scheme which
is not sufficiently secure.
For further details refer to the [[Features/VirtVNCAuth|Virtualization VNC Authentication]] wiki page
=== Improved Graphical Console for Virtual Machines ===
Previous Fedora virtual guest consoles were limited to a screen
resolution of 800x600, and the <code>PS2</code> mouse pointer operated in
relative coordinate mode. This prevented the guest pointer from tracking
the local client pointer one for one.
Fedora 11 provides more accurate mouse pointer positioning and higher
screen resolutions for virtual machine consoles.
Fedora 11 guests default to a screen resolution of at least 1024x768,
and are provided with a <code>USB</code> tablet in absolute coordinate
mode. This results in a mouse pointer which tracks the local client pointer one
for one.
For further details refer to the [[Features/VirtImprovedConsole|Improved Graphical Console for Virtual Guests]] wiki page
=== KVM PCI Device Assignment ===
{{Admon/warning|Work in progress.|Feature is 95% complete.}}
Fedora 11 expands its virtualization capabilities to include <code>KVM</code> PCI device assignment support. <code>KVM</code> users can now give virtual machines exclusive access to physical PCI devices using Fedora's virtualization toools, including the Virtual Machine Manager application.
{{Admon/note|Hardware requirements|Intel <code>VT-d</code> or AMD <code>IOMMU</code> hardware platform support is required in order for this feature to be available.}}
For further details refer to the [[Features/KVM_PCI_Device_Assignment|KVM PCI Device Assignment]] wiki page.
=== SVirt Mandatory Access Control ===
Fedora 11 integrates SELinux's Mandatory Access Control with Virtualization. Virtual machines can now be much more effectively isolated from the host and one another, giving the increased assurance that security flaws cannot be exploited by malicious guests.
For further details refer to the [[Features/SVirt_Mandatory_Access_Control|SVirt Mandatory Access Control]] wiki page.
=== Other Improvements ===
Fedora also includes the following virtualization improvements:
==== libvirt Updated to 0.6.1 ====
The <code>libvirt</code> package provides an API and tools to interact with the virtualization capabilities of recent versions of Linux (and other OSes). The <code>libvirt</code> software is designed to be a common denominator among all virtualization technologies with support for the following:
* The Xen hypervisor on Linux and Solaris hosts.
* The QEMU emulator
* The KVM Linux hypervisor
* The LXC Linux container system
* The OpenVZ Linux container system
* Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, and NFS
'''New features and improvements since 0.4.6:'''
* new APIs for Node device detach reattach and reset
* sVirt mandatory access control support
* thread safety of the API and event handling
* allow QEmu domains to survive daemon restart
* extended logging capabilities
* support copy-on-write storage volumes
* support of storage cache control options for QEmu/KVM
* driver infrastructure and locking
* Test driver infrastructure
* parallelism in the daemon and associated config
* virsh help cleanups
* logrotate daemon logs
* more regression tests
* QEmu SDL graphics
* add --version flag to daemon
* memory consumption cleanup
* QEmu pid file and XML states for daemon restart
* gnulib updates
* PCI passthrough for KVM
* generic internal thread API
* RHEL-5 specific Xen configure option and code
* save domain state as string in status file
* add locking to all API entry points
* new ref counting APIs
* IP address for Xen bridges
* driver format for disk file types
* improve QEmu/KVM tun/tap performances
* enable floppies for Xen fully virt
* support VNC password settings for QEmu/KVM
* qemu driver version reporting
There were also dozens of cleanups, documentation enhancements, portability and bug fixes. For further details refer to:
==== virt-manager Updated to 0.7.0 ====
The <code>virt-manager</code> package provides a GUI implementation of <code>virtinst</code> and <code>libvirt</code> functionality.
'''New features and improvements since 0.6.0:'''
* Redesigned 'New Virtual Machine' wizard
* Option to remove storage when deleting a virtual machine.
* File browser for libvirt storage pools and volumes, for use when attaching storage to a new or existing guest.
* Physical device assignment (PCI, USB) for existing virtual machines.
* VM disk and network stats reporting
* VM Migration support
* Support for adding sound devices to an existing VM
* Enumerate host devices attached to an existing VM
* Allow specifying a device model when adding a network device to an existing VM
* Combine the serial console view with the VM Details window
* Allow connection to multiple VM serial consoles
* Bug fixes and many minor improvements.
For further details refer to:
==== virtinst Updated to 0.400.2 ====
The <code>python-virtinst</code> package contains tools for installing and manipulating multiple VM guest image formats.
'''New features and improvements since 0.400.0:'''
* New <code>virt-clone</code> option <code>--original-xml</code>, allows cloning a guest from an xml file, rather than require an existing, defined guest.
* New <code>virt-install</code> option <code>--import</code>, allows creating a guest from an existing disk image, bypassing any OS install phase.
* New <code>virt-install</code> option <code>--host-device</code>, for connecting a physical host device to the guest.
* Allow specifying 'cache' value via <code>virt-install</code>'s <code>--disk</code> options (Ben Kochie)
* New <code>virt-install</code> option <code>--nonetworks</code> (John Levon)
* Add <code>virt-image</code> to <code>vmx</code> format support to <code>virt-convert</code>, replacing <code>virt-pack</code> (Joey Boggs)
* Add disk checksum support to <code>virt-image</code> (Joey Boggs)
* Enhanced URL install support: Debian Xen paravirt, Ubuntu kernel and boot.iso, Mandriva kernel, and Solaris Xen Paravirt (Guido Gunther, John Levon, Cole Robinson)
* Expanded test suite
* Numerous bug fixes, cleanups, and improvements
For further details refer to:
==== Xen Updated to 3.3.1 ====
Fedora 11 supports booting as a domU guest, but will not function as a dom0 host until such support is provided in the upstream kernel. Support for a <code>pv_ops</code> dom0 is targeted for Xen 3.4.
'''Changes since 3.3.0:'''
* Xen 3.3.1 is a maintenance release in the 3.3 series.
For further details refer to:
* -- Xen roadmap
* -- paravirt_ops patch queue
=== Xen Kernel Support ===
The <code>kernel</code> package in Fedora 11 supports booting as a guest domU, but will not function as a dom0 until such support is provided upstream. The most recent Fedora release with dom0 support is Fedora 8.
Booting a Xen domU guest within a Fedora 11 host requires the KVM based <code>xenner</code>. Xenner runs the guest kernel and a small Xen emulator together as a KVM guest.
{{Admon/important | KVM requires hardware virtualization features in the host system.| Systems lacking hardware virtualization do not support Xen guests at this time. }}
For more information refer to:
<noinclude>[[Category:Release Notes]]<noinclude>

Latest revision as of 01:33, 20 September 2016

DocsProject Header docTeam1.png

Beat Closed on Wiki
Work on beats has now moved to git at If you have changes or additions, please contact the docs team via #fedora-docs,, or with the release-notes BZ component.