|
|
| Line 12: |
Line 12: |
| [http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list] | | [http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list] |
|
| |
|
| ==== More Device Support in virt-manager ==== | | ==== ==== |
| [[ColeRobinson|Cole Robinson]]
| |
| patched<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00013.html</ref>
| |
| {{package|virt-manager}} to implement adding of virtual video devices in the
| |
| 'Add Hardware' wizard. Cole also implemented<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00012.html</ref> attaching serial and parallel devices.
| |
| | |
| Both these features were added to
| |
| {{package|python-virtinst|virt-install}}<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00010.html</ref>. Serial ports can be directed to sockets listening on remote hosts. For example: <code>--serial udp,host=192.168.10.20:4444</code>. That may come in handy for the F12 Hostinfo feature<ref>http://fedoraproject.org/wiki/Features/Hostinfo</ref>.
| |
| | |
| <references />
| |
| | |
| ==== Xen, Windows, and ACPI ====
| |
| [[GuidoGünther|Guido Günther]]
| |
| noted<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00000.html</ref>
| |
| that <code>virt-install</code> disables ACPI and APIC for Windows XP guests.
| |
| Adding, that it seems "that Windows XP is working fine with acpi/apic enabled which has
| |
| the immediate advantage that poweroff via ACPI works as expected.
| |
| So does it make sense to handle winxp the same win2k3?". Windows 2003 guests have ACPI enabled.
| |
| | |
| [[PasiKärkkäinen|Pasi Kärkkäinen]]
| |
| went to the xen-devel list and confirmed<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00007.html</ref>
| |
| and relayed "Keir Fraser replied that ACPI with Windows has been working properly at least since Xen 3.1.0 days".
| |
| Pasi then updated the Xen wiki page<ref>http://wiki.xensource.com/xenwiki/XenWindowsACPI</ref>.
| |
| | |
| <references /> | | <references /> |
|
| |
|
| Line 42: |
Line 19: |
| [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. | | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
|
| ==== Fedora Virt Status Update ==== | | ==== New Release libguestfs 1.0.59 ==== |
| [[MarkMcLoughlin|Mark McLoughlin]]
| |
| posted<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00083.html</ref>
| |
| another Fedora Virt Status Update reminding that [[releases/12|Fedora 12]] is
| |
| quickly approaching with the Feature Freeze on 2009-07-28.
| |
| | |
| Also mentioned were:
| |
| * Details of a fix for "a dramatic slowdown in virtio-blk performance in F-11 guests"<ref>https://bugzilla.redhat.com/509383</ref>
| |
| * Note on Xen Dom0 support.
| |
| * New wiki pages created.
| |
| * Detailed run-down of current virt bugs.
| |
| | |
| <references />
| |
| | |
| ==== New Mailing List and New Releases of libguestfs ====
| |
| [[RichardJones|Richard Jones]] | | [[RichardJones|Richard Jones]] |
| announced<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00107.html</ref> | | announced<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00132.html</ref> |
| the creation of a new list<ref>http://www.redhat.com/mailman/listinfo/libguestfs</ref> dedicated to | | the release of {{package|libguestfs}} 1.0.59. |
| "{{package|libguestfs}}/<code>guestfish</code>/<code>virt-inspector</code> discussion/development".
| |
| | |
| The current release is now 1.0.57<ref>http://www.redhat.com/archives/libguestfs/2009-July/msg00011.html</ref>, but Richard is so fast that may change by the time you read this.
| |
|
| |
|
| '''Recent new features:''' | | '''New Features:''' |
| * <code>virt-df</code> - like 'df' for virtual machines | | * Support for Linux extended attributes. |
| * New Perl library called Sys::Guestfs::Lib | | * Allow guestfish to be controlled remotely, so you can use one guestfish instance in a long-running shell script. |
| * Now available for EPEL | | * Support for reiserfs. |
| * Tab completion in guestfish now completes files and devices | | * New function 'guestfs_zfile' -- 'file' inside compressed files. |
| * Big change to the code generator | | * New guestfish command 'reopen' -- reopen guestfish connection. |
| * Lots more regression tests
| | * guestfish -x option (echo commands). |
| * guestfish commands: time, glob, more, less | | * New function 'guestfs_version' to get the library version. |
| * new commands: readdir, mknod*, umask, du, df*, head*, tail*, wc*, mkdtemp, scrub, sh, sh-lines.
| |
| * Debian native<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00088.html</ref> (debootstrap, debirf) support | |
|
| |
|
| See previous release announcement for 1.0.14 in FWN#179<ref>http://fedoraproject.org/wiki/FWN/Issue179#New_Release_libguestfs_1.0.41</ref> | | 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 | | and be sure to see the project homepage<ref>http://libguestfs.org/</ref> for |
| extensive usage examples. | | extensive usage examples. |
|
| |
| <references />
| |
|
| |
| ==== USB Passthrough to Virtual Machines ====
| |
| [[MarkMcLoughlin|Mark McLoughlin]]
| |
| posted instructions<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00182.html</ref> for attaching a USB device to a guest using {{package|virt-manager}} in Fedora 11. This could previously (FWN#165<ref>http://fedoraproject.org/wiki/FWN/Issue165#Hot_Add_USB_Device_to_Guest</ref>) be accomplished only on the command line.
| |
|
| |
| Unfortunately, those wishing to manage their iPhone or newer iPods in a guest (yours truly included), KVM does not yet support the required USB 2.
| |
|
| |
|
| <references /> | | <references /> |
| Line 93: |
Line 44: |
| [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. | | [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. |
|
| |
|
| ==== New Release libvirt 0.6.5 ==== | | ==== ==== |
| [[DanielVeillard|Daniel Veillard]]
| |
| announced<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00060.html</ref>
| |
| a new {{package|libvirt}} release, version 0.6.5.
| |
| "This is mostly a bug fix release, though it includes some serious
| |
| improvements for storage/NPIV<ref>http://www.libvirt.org/storage.html</ref> and on the OpenNebula driver<ref>http://www.libvirt.org/drvone.html</ref>."
| |
| | |
| '''New features:'''
| |
| * create storage columes on disk backend (Henrik Persson)
| |
| * drop of capabilities based on libcap-ng when possible (Daniel Berrange)
| |
| | |
| '''Improvements:'''
| |
| * create and destroy NPIV support (David Allan)
| |
| * networking in UML driver (Daniel Berrange)
| |
| * HAL driver restart thread safety (Daniel Berrange)
| |
| * capabilities and nodeinfo APIs for LXC (Daniel Berrange)
| |
| * iNUMA API for VBox (Daniel Berrange)
| |
| * dynamically search and use kvm-img qemu-img or qcow-create (Doug Goldstein)
| |
| * fix qemu and kvm version parsing (Mark McLoughlin)
| |
| * serial number for HAL storage (Dave Allan)
| |
| * improve error reporting for virConnectOpen URIs (Daniel Berrange)
| |
| * include OS driver name in device XML (Daniel Berrange)
| |
| * fix qemu command flags fetching (Cole Robinson)
| |
| * check that qemu support -drive format= (Cole Robinson)
| |
| * improve emulator detection (Cole Robinson)
| |
| * changes to config parser to accomodate VMX syntax (Matthias Bolte)
| |
| * update network schemas and driver for missing elements (Satoru SATOH)
| |
| * avoid changing file context if not needed (Tim Waugh)
| |
| * skip labelling if no src path (Cole Robinson)
| |
| * add arm emulation if qemu-system-arm is present (C.J. Adams-Collier)
| |
| | |
| <code>libvirt</code> 0.6.4 was
| |
| released<ref>http://fedoraproject.org/wiki/FWN/Issue179#New_Release_libvirt_0.6.4</ref>
| |
| on May 29.
| |
| [[DanielVeillard|Daniel Veillard]]
| |
| is "shooting for a slightly smaller
| |
| development cycle, in order to be able to push the next version in time
| |
| for [[Releases/12|Fedora 12]] Beta, this means a new release at the end of July, so only
| |
| a bit more than a couple of weeks for pushing the changes, I really hope
| |
| we will be able to include a first version of the ESX driver and Power
| |
| Hyprvisor, if it's the case I think it will be worth bumping the release
| |
| name to 0.7.0."
| |
| | |
| <references />
| |
| | |
| ==== libvirt Repositories Mirrored on Gitorious ====
| |
| Development of libvirt recently moved<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00064.html</ref> to git as the source control management system.
| |
| [[DanielBerrange|Daniel Berrange]]
| |
| announced<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00252.html</ref>
| |
| "I have created a {{package|libvirt}} project<ref>http://gitorious.org/libvirt</ref> on gitorious which has a mirror of
| |
| the master branch of the libvirt.git repository. This mirror is *readonly*
| |
| and updated automatically every 15 minutes. The purpose of this mirror is
| |
| to allow people to easily publish their personal <code>libvirt</code> working repos
| |
| to the world. The master upstream repository for <code>libvirt</code> does not change<ref>http://libvirt.org/git</ref>".
| |
| | |
| <references />
| |
| | |
| ==== The Role of libvirtd ====
| |
| [[HughBrock|Hugh Brock]]
| |
| described<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00179.html</ref>
| |
| a client's desire to make
| |
| "libvirtd be a one-stop shop for everything they need
| |
| to do on a virtualization host, including things we have traditionally
| |
| held out-of-scope for <code>libvirt</code>. A partial list of those things would
| |
| include:"
| |
| | |
| * In-depth multipath config management
| |
| * Hardware lifecycle management (power-off, reboot, etc.)
| |
| * HA configuration
| |
| | |
| Hugh then asked "why *not* expand the scope of <code>libvirtd</code>
| |
| to be a one-stop shop for managing a node? Is there a really good
| |
| reason it shouldn't have the remaining capabilities <code>libvirt</code> users
| |
| want?"
| |
| | |
| [[DanielBerrange|Daniel Berrange]]
| |
| replied<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00182.html</ref>
| |
| "This is essentially suggesting that <code>libvirtd</code> become a general purpose
| |
| RPC layer for all remote management tasks. At which point you have
| |
| just re-invented QPid/AMQP or CIM or any number of other general
| |
| purpose message buses. <code>libvirtd</code> has a core well defined goal:"
| |
| * Provide a remote proxy for <code>libvirt</code> API calls
| |
| | |
| "If you want todo anything more than that you should be considering an
| |
| alternative remote management system. We already have 2 good ones to
| |
| choose from supported with <code>libvirt</code>"
| |
| * QPid/AMQP, with <code>libvirt-qpid</code><ref>http://libvirt.org/qpid/</ref> agent + your own custom agents
| |
| * CIM, with libvirt-CIM<ref>http://libvirt.org/CIM/</ref> + your own custom CIM providers
| |
| | |
| "Furthermore, adding more plugins to <code>libvirtd</code> means we will never
| |
| be able to reduce its privileges to an acceptable level, because we'll
| |
| never know what capabilities the plugins may want."
| |
| | |
| Hugh countered <ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00183.html</ref>
| |
| "given a <code>libvirt-qpid</code> daemon on the node that handles RPC over
| |
| QMF (for example), is there not some value in having <code>libvirt</code> expose a
| |
| consistent API for the operations people want to do on a host regardless
| |
| of whether they have directly to do with managing a virtual machine or
| |
| not?"
| |
| | |
| [[DanielBerrange|Daniel Berrange]]
| |
| didn't "really see any value in that"
| |
| "You're just putting in another
| |
| abstraction layer where none need exist. Just have whatever QMF agent
| |
| you write talk directly to the thing you need to manage."
| |
| | |
| Hugh
| |
| "I will note that when I presented the large client with the option of
| |
| QMF talking to multiple agents on the node but exposing (effectively) a
| |
| single API and a single connection, they seemed much happier. So perhaps
| |
| the right way to attack this is with the
| |
| <code>ovirt-qpid</code><ref>http://ovirt.org/</ref> daemon we are
| |
| currently working on."
| |
| | |
| [[DanielVeillard|Daniel Veillard]]
| |
| was<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00186.html</ref>
| |
| "a bit synpathetic to the suggestion though."
| |
| "I think <code>libvirt</code> API
| |
| should help run those virtualization nodes, I would not open the gate
| |
| like completely, but if we could provide all APIs needed to manage the
| |
| node on a day by day basis then I think this is not really beyond our
| |
| scope. I think that netcf(FWN#170<ref>http://fedoraproject.org/wiki/FWN/Issue170#First_Release_netcf_0.0.1</ref>) is an example of such API where we start to
| |
| add admin services for the purpose of running virtualization. Things
| |
| like rebooting or shutting down the node would fit in this, maybe
| |
| editing a drive partition too."
| |
| | |
| "Basically if we take the idea of a stripped down Node used only for
| |
| virtualization, then except for operations which are first time setup
| |
| options or maintainance, I think we should try to cover the requirements
| |
| of normal operations of that node. To some extend that means we would
| |
| step on the toes of CIM, but we would stick to a subset that's sure."
| |
| | |
| <references />
| |
| | |
| | |
| | |
| | |
| | |
| ==== Storage cloning for LVM and Disk backends ====
| |
| [[ColeRobinson|Cole Robinson]]
| |
| submitted<ref>http://www.redhat.com/archives/libvir-list/2009-July/msg00268.html</ref>
| |
| a patch series which "implements cloning for LVM and disk backends. Most
| |
| of the functionality is already here, it just needed some reorganization
| |
| to be accessible for every backend."
| |
| | |
| "I verified the following scenarios produced a bootable image:"
| |
| * Clone within a disk pool
| |
| * Clone within a logical pool
| |
| * Clone a raw file to a disk pool
| |
| * Clone a disk pool to a logical pool
| |
| | |
| <references /> | | <references /> |
|
| |
|
| Line 250: |
Line 51: |
| [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. | | [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. |
|
| |
|
| ==== Xen dom0 Forward Ported to Latest Kernel ==== | | ==== ==== |
| Previously, Xen dom0 support in Fedora was provided by forward porting the Xensource patches from kernel 2.6.18 to the version found in the Fedora release at the time. This consumed developer resources and led to separate {{package|kernel}} and {{package|kernel-xen}} packages for a time. As of
| |
| [[Releases/9|Fedora 9]]<ref>http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Virtualization.html</ref> this practice was deamed<ref>https://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html</ref> untenable, and support for hosting Xen guests was dropped from Fedora.
| |
| | |
| Work has since focused on creating a paravirt operations dom0<ref>http://fedoraproject.org/wiki/Features/XenPvopsDom0</ref> kernel based on the most recent upstream vanilla kernel. This work is incomplete and not expected to be done before F12 or even F13. However, experimental dom0 kernels<ref>http://fedoraproject.org/wiki/FWN/Issue170#Experimental_Dom0_Kernel_Update</ref> have been created for the adventurous.
| |
| | |
| [[PasiKärkkäinen|Pasi Kärkkäinen]]
| |
| tells<ref>http://www.redhat.com/archives/fedora-xen/2009-July/msg00000.html</ref> us
| |
| the Xen 2.6.18 patches have now been forward-ported to the current 2.6.29 and
| |
| 2.6.30 kernel. "Forward-porting has been done by Novell for OpenSUSE. Novell also has a forward-port to 2.6.27 for SLES11."
| |
| | |
| The patches can be found
| |
| here<ref>http://www.nabble.com/2.6.30-dom0-Xen-patches-td24293721.html</ref>
| |
| here <ref>http://code.google.com/p/gentoo-xen-kernel/downloads/list</ref>
| |
| and here<ref>http://x17.eu/xen/</ref>.
| |
| | |
| Pasi added "These patches are still more stable and mature than the
| |
| pv_ops dom0 code.. Also, these patches have the full Xen feature set
| |
| (pv_ops still lacks some features)."
| |
| | |
| More history is avilable<ref>http://fedoraproject.org/wiki/Virtualization/History</ref>.
| |
| | |
| <references /> | | <references /> |
libguestfs