|
|
| Line 9: |
Line 9: |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list] | | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list] |
|
| |
|
| ==== Use Avahi to Discover Local Servers in Virt-manager ==== | | === Fedora Xen List === |
| [[ColeRobinson|Cole Robinson]] committed[1] a patch[2] to add support for avahi polling in the virt-manager 'Open Connection' dialog.
| | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. |
| | |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00000.html
| |
| | |
| [2] https://www.redhat.com/archives/et-mgmt-tools/2008-August/msg00123.html
| |
| | |
| ==== Virtio Support in Libvirt and Virt-manager ====
| |
| [[EmreErenoglu|Emre Erenoglu]] asked[1] if virtio[2] would be supported in
| |
| virt-manager. [[DanielBerrange|Daniel P. Berrange]] said[3] libvirt supports it as of 0.4.4 and virt-manager will soon automatically enable virtio for disks known to include it.
| |
| | |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00010.html
| |
| | |
| [2] http://kvm.qumranet.com/kvmwiki/Virtio
| |
| | |
| [3] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00011.html
| |
| | |
| The design paradigm[4] for virt-manager is to allow selection of OS Type and Variant which informs the features to be enabled, rather than exposing individual features toggles. [[ColeRobinson|Cole Robinson]] agreed[5] exposing the option to enable virtio disks for an unknow virtio-enabled distribution might not be a bad idea.
| |
| | |
| [4] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00013.html
| |
| | |
| [5] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00015.html
| |
| | |
| ==== New Virt-manager and Virtinst Releases Pending ====
| |
| [[ColeRobinson|Cole Robinson]] announced[1] that with the pending Fedora 10 beta freeze on Tuesday, September 9th new releases of virt-manager + virtinst are imminent. [[DanielBerrange|Daniel P. Berrange]] concurred[2] that libvirt would roll out a new release around that time as well.
| |
| | |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00002.html
| |
| | |
| [2] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00005.html | |
| | |
| ==== Virt-install Patch for Disk Size and Sparse ====
| |
| [[ColeRobinson|Cole Robinson]] patched[1] virt-install's new ''--disk'' option to specify size of new storage, and whether it be create it as a sparse file.
| |
|
| |
|
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-September/msg00004.html | | ==== Laying the Groundwork for Xen Domain 0 Support ==== |
| | Pasi Kärkkäinen forwarded[1] a patch announcement from xen-devel list. The set of 7 patches begin to lay the groundwork for Xen domain 0 support. [[DanielBerrange|Daniel P. Berrange]] said[2] these Dom0 patches will be make their way into rawhide when they are merged into the LKML |
| | dev tree line used in rawhide at the time. |
|
| |
|
| === Fedora Xen List ===
| | [1] https://www.redhat.com/archives/fedora-xen/2008-September/msg00001.html |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
| |
|
| |
|
| Nothing to report this week.
| | [2] https://www.redhat.com/archives/fedora-xen/2008-September/msg00003.html |
|
| |
|
| === Libvirt List === | | === Libvirt List === |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. | | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. |
|
| |
| ==== Libvirt vs XenAPI ====
| |
| Atif Bajwa asked[1] about the advantages of using libvirt over [http://wiki.xensource.com/xenwiki/XenApi XenAPI] and what platforms libvirt supports. [[AtsushiSakai|Atsushi Sakai]] pointed to a list[2] of which libvirt calls work on which drivers / hypervisors. [[DanielBerrange|Daniel P. Berrange]] replied[3] that libvirt is available for every major Linux distro, and listed several benefits such as:
| |
|
| |
| * avoids locking applications to a particular hypervisor
| |
| * provides a guaranteed stable API that can be used both locally and remotely
| |
| * remote security options include SSL + x509 certificates, SSH tunnel, Kerberos GSSAPI single sign on, and username + password
| |
| * works with every version of Xen 3.0.x or later while XenAPI is only usable in Xen 3.1.0 and later
| |
|
| |
| [[RichardJones|Richard W.M. Jones]] mentioned[4] that although there are no binaries [[SIGs/MinGW|yet]], libvirt client code can be compiled on windows.
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00002.html
| |
|
| |
| [2] http://libvirt.org/hvsupport.html
| |
|
| |
| [3] https://www.redhat.com/archives/libvir-list/2008-September/msg00008.html
| |
|
| |
| [4] https://www.redhat.com/archives/libvir-list/2008-September/msg00016.html
| |
|
| |
| ==== Latest MinGW Patches ====
| |
| [[DanielBerrange|Daniel P. Berrange]] posted[1] patches to allow building on F10 of libvirt-0.dll and virsh.exe which run successfully under Wine, provided only 'test' and 'remote' drivers are turned on.
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00065.html
| |
|
| |
| ==== Does Libvirtd Need to Always be Running ====
| |
| [[YushuYao|Yushu Yao]] asked[1] a basic question which may be helpful to point
| |
| out. Does libvirtd need to always be running? [[RichardJones|Richard W.M. Jones]] answered[2] "yes and no". The local Xen hypervisor can be managed by direct hypervisor calls and/or a connection to xend. Warnings that libvirtd isn't running may be ignored.
| |
|
| |
| Libvirtd must be running to support the following, however.
| |
| * remote access
| |
| * non-root access
| |
| * if you use the network or storage features
| |
| * managing QEMU and KVM instances
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00085.html
| |
|
| |
| [2] https://www.redhat.com/archives/libvir-list/2008-September/msg00103.html
| |
|
| |
|
| === oVirt Devel List === | | === oVirt Devel List === |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list]. | | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list]. |
|
| |
| ==== Renaming oVirt RPMs ====
| |
| [[AlanPevec|Alan Pevec]] proposed[1] renaming the oVirt packages which turned into a discussion with [[DanielBerrange|Daniel P. Berrange]] about how to organize the git repos and how to continue support build-all after such a change.
| |
|
| |
| [1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00029.html
| |
|
| |
| ==== WUI Management of Underlying Hardware ====
| |
| [[ChrisLalancette|Chris Lalancette]] posted[1] a series of patches to allow the Web User Interface to manage the underlying hardware it is running on.
| |
|
| |
| [1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00081.html
| |
|
| |
| ==== Network Interface Bonding and Failover ====
| |
| [[DarrylPierce|Darryl L. Pierce]] began[1] a discussion on implementing support for ethernet bonding multiple interfaces for load balancing and failover. Special consideration for different hardware scenarios such as blade servers lead [[KonradRzeszutek|Konrad Rzeszutek]] to ask how these extra parameters would be passed in to the bonding setup. Darryl explained[2] that on boot the node identifies itself to the oVirt server, and downloads a configuration file to be processed by augtool[3]. The managed node then restarts the network service to apply the network configuration that it just retrieved.
| |
|
| |
|
| |
| [1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00064.html
| |
|
| |
| [2] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00075.html
| |
|
| |
| [3] http://augeas.net/
| |
