From Fedora Project Wiki

< FWN‎ | Beats

(→‎Enterprise Management Tools List: Maintain VM State While Restarting libvirtd)
 
(428 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Category:Virtualization]] <!-- do not copy into FWN issue -->
{{Anchor|Virtualization}}
{{Anchor|Virtualization}}


== Virtualization ==
== Virtualization ==
In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies.
In this section, we cover discussion of Fedora virtualization technologies on the
 
@fedora-virt list.
Contributing Writer: [[DaleBewley | Dale Bewley]]
 
=== Enterprise Management Tools List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
 
==== virt-manager Adds Disk and Network I/O Graphs ====
[[GuidoGünther|Guido Günther]] submitted[1] a patch for <code>virt-manager</code>
to display with disk and network input/output graphs in addition to the CPU and memory utilization graphs.
 
[1] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00026.html
 
==== virt-manager Supports Multiple Serial Consoles ====
[[ColeRobinson|Cole Robinson]] patched[1] <code>virt-manager</code> to
combine "the serial console window with the VM details window. Opening the serial console now appends a tab to the details view. In addition, multiple serial consoles are now supported, not just the primary/first defined console, though this still only works for 'pty' devices."
 
[1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00109.html
 
==== Maintaining VM State While Restarting libvirtd Needed ====
Upgrades of <code>libvirt</code> necessitate a restart of <code>libvirtd</code>.  [[GuidoGünther|Guido Günther]] asked[1] if there was any progress on saving enough state to restart <code>libvirtd</code> without restarting any guests. [[DanielBerrange|Daniel P. Berrange]] replied[2] this has been solved for the LXC driver and the same approach may apply to the QEMU driver.
 
[1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00093.html
 
[2] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00094.html
 
Guido pointed[3] out "This would solve the problem of restarting libvirtd. How are we going to
distinguish this from daemon shutdown on e.g. system reboot?" To which, Daniel B. proposed[4]
"We can probably distinguish by picking a specific signal for orderly shutdown of the daemon + vms, vs a simple restart." Adding, "Perhaps we should have an explicit API, or a convenient virsh command to
shutdown all VMs in one go."
 
[3] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00046.html


[4] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00047.html
Contributing Writer: [[User:Dale | Dale Bewley]]


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


==== No Dom0 Support in Fedora 10 ====
==== Virt Status Report ====
[[DanielBerrange|Daniel P. Berrange]] laid[1] it out there.  
[[JustinForbes|Justin Forbes]]
"There is pretty much zero chance that Fedora 10 will include a Xen
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.  
Dom0 host. While upstream Xen developers are making good progress
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.
on porting Dom0 to paravirt_ops, there is simply too little time
for this to be ready for Fedora 10. So if you need to use Fedora 10
as a host, then KVM is your only viable option at this time. If
you can wait for Fedora 11 (or use RHEL-5 / CentOS-5) then Xen may
be an option for you." See also FWN 143[2].


[1] https://www.redhat.com/archives/fedora-xen/2008-September/msg00035.html
<references />


[2] https://fedoraproject.org/wiki/FWN/Issue143#Laying_the_Groundwork_for_Xen_Domain_0_Support
==== RHEL and Fedora Virtualization Feature Parity ====
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
compared to Fedora 12.


=== Libvirt List ===
[[DanielBerrange|Daniel Berrange]]
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
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
kvm-83 and kvm-84."


==== Running Xen Guests Without xend ====
<references />
[[StefanKonink|Stefan de Konink]] asked[1] if users could someday run xen
guests without a xend running. [[GerdHoffmann|Gerd Hoffmann]] said[2] there
are patches queued up which begin to allow qemu to do this. Adding, "If things work out well we might have that in the F11 timeframe." Assuming Dom0 support in the pv_ops based kernel is completed.


[1] https://www.redhat.com/archives/libvir-list/2008-September/msg00402.html


[2] https://www.redhat.com/archives/libvir-list/2008-September/msg00406.html
====  ====
<references />


=== oVirt Devel List ===
====  ====
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
<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.

  1. ↑ http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html
  2. ↑ http://fedoraproject.org/wiki/Virtualization_bugs

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."

  1. ↑ http://www.redhat.com/virtualization/rhev/
  2. ↑ http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html



Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Virtualization&oldid=142485"