FWN/Beats/Virtualization: Difference between revisions

Revision as of 01:04, 12 October 2009

Virtualization

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

Contributing Writer: Dale Bewley

Fedora Virtualization List

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

New Release virt-top 1.0.4

Richard Jones announced^[1] a new release of virt-top. "Virt-top^[2] looks and acts like the familiar top(1) command, displays virtual machines, and uses libvirt so it works with just about every virtualization system out there. It also has cool features for sysadmins, like you can use it to log stats into a database or spreadsheet."

Limit VNC Access to a Single Guest

Dennis asked^[1] if it was possible to limit a user to a single guest console rather than the all guests in a virt-manager instance.

Richard Jones answered that virt-manager doesn't support that level of authorization^[2] yet, but each guest console can be given^[3] a static VNC port number which can be secured with a firewall or ssh port forwarding.

Libvirt List

This section contains the discussion happening on the libvir-list.

@@ Line 3: / Line 3: @@
 {{Anchor|Virtualization}}
 == Virtualization ==
 In this section, we cover discussion of Fedora virtualization technologies on the
-@fedora-virt and @fedora-xen-list lists.
+@fedora-virt, @fedora-xen-list, @libguestfs, @libvirt-list,
+@virt-tools-list, and @ovirt-devel-list lists.
 Contributing Writer: [[User:Dale | Dale Bewley]]
@@ Line 15: / Line 15: @@
 [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
-==== Fedora virt status ====
+==== New Release virt-top 1.0.4 ====
-The latest status report<ref>http://www.redhat.com/archives/fedora-virt/2009-October/msg00013.html</ref> from [[MarkMcLoughlin|Mark McLoughlin]]
+[[RichardJones|Richard Jones]]
-Prompts us all to help out as the Fedora 12 "Beta is on its way
+announced<ref>http://www.redhat.com/archives/fedora-virt/2009-October/msg00019.html</ref> a new release of {{package|virt-top}}.
-out the door and release candidate composes will begin in less than
+"Virt-top<ref>http://et.redhat.com/~rjones/virt-top/</ref> looks and acts
-four weeks time." "Here are three ways you could help out with getting F12 into great shape." Continue reading in the archive to find out how you can help!
+like the familiar top(1) command, displays virtual machines, and uses
+libvirt so it works with just about every virtualization system out
+there. It also has cool features for sysadmins, like you can use it to
+log stats into a database or spreadsheet."
 <references />
-==== New Tools virt-rescue and virt-edit ====
+==== Limit VNC Access to a Single Guest ====
-[[RichardJones|Richard Jones]]
+Dennis asked<ref>http://www.redhat.com/archives/fedora-virt/2009-October/msg00027.html</ref>
-announced<ref>http://www.redhat.com/archives/fedora-virt/2009-September/msg00099.html</ref> two new tools in {{package|libguestfs-tools}}, <code>virt-rescue</code> and <code>virt-edit</code>.
+if it was possible to limit a user to a single guest console rather than the
+all guests in a {{package|virt-manager}} instance.
-The <code>virt-rescue</code><ref>http://www.libguestfs.org/virt-rescue.1.html</ref> tool "lets you run a rescue shell against a virtual machine" while <code>virt-edit</code><ref>http://www.libguestfs.org/virt-edit.1.html</ref> lets you edit a file inside a VM".
+[[RichardJones|Richard Jones]] answered that <code>virt-manager</code> doesn't
-For example:
+support that level of authorization<ref>http://fedoraproject.org/wiki/Features/VirtAuthorization</ref> yet, but each guest console can be given<ref>http://www.libvirt.org/formatdomain.html#elementsGraphics</ref> a
- virt-edit mydomain /boot/grub/grub.conf
+static VNC port number which can be secured with a firewall or ssh port
+forwarding.
 <references />
-=== Fedora Xen List ===
+=== Libvirt List ===
 This section contains the discussion happening on the
-[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
+[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
-==== xen/master: pvops git trees rearranged  ====
-[[PasiKärkkäinen|Pasi Kärkkäinen]]
-forwarded<ref>http://www.redhat.com/archives/fedora-xen/2009-September/msg00107.html</ref> an announcement from Jeremy Fitzhardinge about reorganizing the Xen git tree<ref>git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git xen/master</ref> with the dom0 kernel.
-"The kernel tree is fairly featureful:"
-* basic dom0 support
-* blkback
-* netback
-* ACPI power management
-* S3 suspend/resume (at least for some people)
-* microcode update
-* MSI support
-"In other words, it has as much as it ever has.
-There are a few notable missing features:"
-* blktap2
-* netchannel2
-* pci front/back
-* upstream Linux support
-* your pet feature
-The Xensource wiki has instructions<ref>http://wiki.xensource.com/xenwiki/XenParavirtOps</ref> compiling.
+====  ====
 <references />

Search