From Fedora Project Wiki

< FWN‎ | Beats

(→‎Virtualization Tools List: remove for this week)
 
(93 intermediate revisions by 2 users not shown)
Line 2: Line 2:


{{Anchor|Virtualization}}
{{Anchor|Virtualization}}


== Virtualization ==
== Virtualization ==
In this section, we cover discussion of Fedora virtualization technologies on the
In this section, we cover discussion of Fedora virtualization technologies on the
@et-mgmnt-tools-list, @fedora-virt, @fedora-xen-list, @libguestfs, @libvirt-list,
@fedora-virt list.
@virt-tools-list, and @ovirt-devel-list lists.


Contributing Writer: [[User:Dale | Dale Bewley]]
Contributing Writer: [[User:Dale | Dale Bewley]]
=== Enterprise Management Tools List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
==== Good Bye to ET-Mgmt-Tools List ====
[[DanielBerrange|Daniel Berrange]]
announced<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00046.html</ref> the end of life for the et-mgmt-tools list and the birth of the @virt-tools-list. "In retrospect this was a really bad choice of names for a mailing list
and causes endless confusion for people wrt what to discuss where. Most
of the emerging technology projects have lists of their own
({{package|cobbler}}<ref>http://fedorahosted.org/mailman/listinfo/cobbler</ref><ref>http://fedorahosted.org/mailman/listinfo/cobbler-devel</ref>,
{{package|augeas}}<ref>http://www.redhat.com/mailman/listinfo/augeas-devel</ref>,
{{package|libguestfs}}<ref>http://www.redhat.com/mailman/listinfo/libguestfs</ref>,
{{package|libvirt}}<ref>http://www.redhat.com/mailman/listinfo/libvir-list</ref>)
and it is about time that {{package|virt-manager}} and friends joined them."
"To that end we have created a new mailing list  'virt-tools-list'<ref>http://www.redhat.com/mailman/listinfo/virt-tools-list</ref>. This
will be the new home for all developer & user discussions relating to
the following applications:"
* virt-manager
* virt-viewer
* virt-install
* virt-clone
* virt-image
* virt-convert
<references />


=== Fedora Virtualization List ===
=== Fedora Virtualization List ===
Line 41: Line 14:
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


==== Virtual Machine Disk Setup Tips ====
==== Virt Status Report ====
[[RichMahn|Rich Mahn]]
[[JustinForbes|Justin Forbes]]
recognized<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00141.html</ref>
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.  
"that the best
Justin pointed out F13 bugs<ref>http://fedoraproject.org/wiki/Virtualization_bugs</ref> now include Important and Pony classifications in addition to Blocker and Target.
performance for virtual disks is with the backing storage on the host
being a parititon or LV. Since I want some flexibility I will use
LVs, with virtio disks on most of the VMs." But Rich
had
several questions (paraphrased below) about how best to configure the backing stores for virtual machines and the disks within them. 
[[DanielBerrange|Daniel Berrange]] provided some answers (also paraphrased
below).
 
* '''Q:''' If each VM needs three file systems: {{filename|/boot}}, {{filename|root}}, and {{filename|swap}}. "Is it better to create three LVs (each) on the hosts, and treat it as three separate disks on the VMs?"
: '''A:''' "There's no point separating /boot & root onto separate virtual disks." "The only separation I'd do is for the OS system disks, vs application data disks..." This makes it easier to provision a new VM with the latest disto and reassign the data disk to the new guest.
 
* '''Q:''' "Do I get better performance/stability by NOT using lvm on the VMs?"
: '''A:''' "LVM makes is easier to resize guest FS. eg add a second disk to the guest, format it as a LVM PV and add it to your VG.  That's pretty much only wayto add more capacity on a running guest."
 
* '''Q:''' "Do I get the best performance/stability by creating an LV for each disk I need, and then NOT partitioning it on the VM, but using the whole disk for a file system?"
: '''A:''' "Anaconda will refuse to install onto a raw disk, it mandates partitioning. Second point is that not using a partition table can cause unexpected problems..."
 
* '''Q:''' "Are these issues too miniscule in their effects that I probably shouldn't even be worrying about" trying to avoid using partitions and LVM?
: '''A:''' "That's certainly my opinion. Sure you get some performance but you loose the great administrative flexibility  of LVM."


<references />
<references />


==== Placeholder ====
==== RHEL and Fedora Virtualization Feature Parity ====
F12 virt features - what will or won't make it in?
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
http://www.redhat.com/archives/fedora-virt/2009-July/msg00133.html
compared to Fedora 12.


<references />
[[DanielBerrange|Daniel Berrange]]  
 
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
=== Libguestfs List ===
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
This section contains the discussion happening on the
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
[http://www.redhat.com/mailman/listinfo/libguestfs libguestfs list].
rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is
 
also pretty close to that using what's best described as a hybrid of
==== New Release libguestfs 1.0.59 ====
kvm-83 and kvm-84."
[[RichardJones|Richard Jones]]
announced<ref>http://www.redhat.com/archives/libguestfs/2009-July/msg00023.html</ref>
the release of {{package|libguestfs}} 1.0.59.
 
'''New Features:'''
* Support for Linux extended attributes.
* Allow guestfish to be controlled remotely, so you can use one guestfish instance in a long-running shell script.
* Support for reiserfs.
* New function 'guestfs_zfile' -- 'file' inside compressed files.
* New guestfish command 'reopen' -- reopen guestfish connection.
* guestfish -x option (echo commands).
* New function 'guestfs_version' to get the library version.
 
See previous release announcement for 1.0.57 in
FWN#184<ref>http://fedoraproject.org/wiki/FWN/Issue184#New_Mailing_List_and_New_Releases_of_libguestfs</ref>
and be sure to see the project homepage<ref>http://libguestfs.org/</ref> for
extensive usage examples.
 
<references />
 
==== New Hypervisor Migration Tool virt-v2v ====
[[MatthewBooth|Matthew Booth]]
posted<ref>http://www.redhat.com/archives/libguestfs/2009-July/msg00024.html</ref>
his "initial thoughts on the design for the v2v tool". This tool will be used
to implement the planned Fedora 12 feature "Xen to KVM Migration"<ref>http://fedoraproject.org/wiki/Features/Xen_to_KVM_migration</ref>.


<references />
<references />




 
==== ====
=== Libvirt List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
==== ====
<references />
<references />


=== Fedora-Xen List ===
==== ====
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
==== ====
<references />
<references />

Latest revision as of 18:09, 18 December 2009



Virtualization

In this section, we cover discussion of Fedora virtualization technologies on the @fedora-virt list.

Contributing Writer: Dale Bewley

Fedora Virtualization List

This section contains the discussion happening on the fedora-virt list.

Virt Status Report

Justin Forbes posted[1] a Fedora virtualization status report. Justin pointed out F13 bugs[2] now include Important and Pony classifications in addition to Blocker and Target.

RHEL and Fedora Virtualization Feature Parity

Robert Day wondered how the virtualization features[1] of Red Hat Enterprise Linux 5.4 compared to Fedora 12.

Daniel Berrange explained[2] "The KVM based virtualization in RHEL-5.4 is not nearly so far behind Fedora as you might think. The Package-x-generic-16.pnglibvirt mgmt stack in RHEL-5.4 was rebased to be near parity with Fedora 11, and KVM in RHEL-5.4 is also pretty close to that using what's best described as a hybrid of kvm-83 and kvm-84."