|
|
Line 8: |
Line 8: |
| === Enterprise Management Tools List === | | === 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] | | This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list] |
|
| |
| ==== Starting Guests from a Desktop Icon ====
| |
| [[OrionPoplawski|Orion Poplawski]] said[1]
| |
| "I'd like to provide an icon that would startup the virtual machine and connect to it."
| |
| [[ColeRobinson|Cole Robinson]] posted[2] a couple of ways to accomplish this.
| |
|
| |
| * With <code>virt-manager</code> and support for CDROM and USB devices
| |
| <pre>
| |
| UUID=`virsh --connect qemu:///system domuuid vm-name`
| |
| virsh --connect qemu:///system start $UUID
| |
| virt-manager --connect qemu:///system \
| |
| --show-domain-console=$UUID
| |
| </pre>
| |
|
| |
| * With <code>virt-viewer</code> which won't support CDROM and USB access
| |
| <pre>
| |
| UUID=`virsh --connect qemu:///system domuuid vm-name`
| |
| virsh --connect qemu:///system start $UUID
| |
| virt-viewer --connect qemu:///system $UUID
| |
| </pre>
| |
|
| |
| Each solution requires adequate user permissions to work.
| |
|
| |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00100.html
| |
|
| |
| [2] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00103.html
| |
|
| |
| ==== Plugins for Performance Monitoring Applications ====
| |
| [[GuidoGünther|Guido Günther]] announced[1] the creation
| |
| of libvirt plugins[2] for net and block I/O monitoring in <code>Munin</code>[3].
| |
|
| |
| [[DanielVeillard|Daniel Veillard]] posted[4] a patch to add this and
| |
| similar plugins for <code>collectd</code>[5] and <code>Nagios</code>[6] to the <code>libvirt</code>
| |
| applications page[7].
| |
|
| |
|
| |
| [1] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00118.html
| |
|
| |
| [2] http://munin.projects.linpro.no/
| |
|
| |
| [3] http://honk.sigxcpu.org/projects/libvirt/monitor/
| |
|
| |
| [4] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00121.html
| |
|
| |
| [5] http://collectd.org/plugins/libvirt.shtml
| |
|
| |
| [6] http://et.redhat.com/~rjones/nagios-virt/
| |
|
| |
| [7] http://libvirt.org/apps.html"
| |
|
| |
|
| === Fedora Xen List === | | === Fedora Xen 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 [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. |
|
| |
| There was no list traffic this week.
| |
|
| |
|
| === 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]. |
|
| |
| ==== Openvz Bridge Support and Related Patches ====
| |
| [[DanielBerrange|Daniel Berrange]] posted[1] a
| |
| patch series "derived from [[AntonProtopopov|Anton Protopopov]] / [[EvgeniySokolov|Evgeniy Sokolov]] bridge device patches. It first does some generic refactoring of <code>MAC</code> address handler in all drivers, then adds code to extract <code>OpenVZ</code>[2] version number, then does network config, and finally does filesystem config."
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00323.html
| |
|
| |
| [2] http://wiki.openvz.org/
| |
|
| |
| ==== Guest Image Locking ====
| |
| [[ItamarHeim|Itamar Heim]] asked[1]
| |
| "how libvirt envisions image locking. i.e., how do we make sure multiple nodes are not trying to access the same storage volume[?]"
| |
|
| |
| [[DanielBerrange|Daniel Berrange]] said[2] in the domain <code>XML</code> format "the semantics are that every <disk> section added to a guest config is read-write, with an exclusive lock. To allow multiple guests to use the same disk, is intended that you add either <readonly/> or <sharable/> element within the <disk>."
| |
|
| |
| Adding, "we only implement this for the Xen driver, handing off the actual logic to XenD to perform. That we don't implement this in the QEMU driver is a clear shortcoming that needs addressing. "
| |
|
| |
| The problem on a single host is relatively simple, but more complex among multiple host nodes. [[GuidoGünther|Guido Günther]] has been toying[3] "with the idea of using DLM[4] for libvirt".
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00334.html
| |
|
| |
| [2] https://www.redhat.com/archives/libvir-list/2008-October/msg00336.html
| |
|
| |
| [3] https://www.redhat.com/archives/libvir-list/2008-October/msg00342.html
| |
|
| |
| [4] http://sources.redhat.com/cluster/dlm/
| |
|
| |
| ==== Exporting the Label on Block Devices ====
| |
| [[ChrisLalancette|Chris Lalancette]] described[1] his patch "To support LVM partitioning in oVirt, one of the things we need is the ability to tell what kind of label is currently on a block device. Here, a 'label' is used in the same sense that it is used in parted; namely, it defines which kind of partition table is on the disk, whether it be DOS, LVM2, SUN, BSD, etc." Note that is is not the same as the partition type.
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00341.html
| |
|
| |
| ==== Experimental User Mode Linux Driver ====
| |
| [[DanielBerrange|Daniel P. Berrange]] applied[1] a patch that
| |
| "implements a driver supporting User Mode Linux[2] guests. User mode
| |
| linux is a kind of paravirtualized kernel which runs on a plain Linux host.
| |
| It requires no elevated privileges at all, except for some of the network
| |
| integration. It is a pretty straightforward thing to invoke, so I figured
| |
| it would be easy to write a driver to support it. I was right :-)"
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00355.html
| |
|
| |
| [2] http://user-mode-linux.sourceforge.net/
| |
|
| |
| ==== Experimental Driver Thread Safety ====
| |
| [[DanielBerrange|Daniel P. Berrange]] continued[1] work toward making libvirt thread-safe.
| |
| The "series of 5 patches implement basic thread safety for the
| |
| QEMU, LXC and Network drivers. It does not address the OpenVZ or Test
| |
| driver yet. The Xen driver is totally stateless so does not require
| |
| changes - though I do need to verify there's no 'static' variables that
| |
| are used in an unsafe yet in Xen drivers." Daniel's earlier work was referenced[2] in FWN #146.
| |
|
| |
| [1] https://www.redhat.com/archives/libvir-list/2008-October/msg00417.html
| |
|
| |
| [2] http://fedoraproject.org/wiki/FWN/Issue146#libvirtd_Multi-threaded_Support_in_the_Works
| |
|
| |
|
| === 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]. |