[virt-tools-list] [virt-viewer v2 0/6] Ovirt foreign menu support

Jonathon Jongsma jjongsma at redhat.com
Fri Jun 27 15:29:17 UTC 2014


I haven't looked at the code closely yet, but I die try to apply and
test briefly on fedora 20. There were no configure issues, but it failed
to build due to the following missing functions:

        ovirt_resource_refresh_async
        ovirt_resource_refresh_finish

Perhaps the libgovirt version requirements need to be increased?  

Jonathon



On Thu, 2014-06-26 at 22:01 +0200, Christophe Fergeau wrote:
> This is the second version of the ovirt foreign menu patch series which was
> first sent as
> https://www.redhat.com/archives/virt-tools-list/2014-April/msg00110.html
> 
> It took longer than expected as I found several issues when addressing the
> review comments (in particular, it turned out the .vv code path was totally
> untested, and thus buggy). I also tested this against oVirt 3.4, and had to
> make some adjustment to take into account some small bugs in the REST API.
> I did not keep track of all the changes I made, so no list of changes since v1 :(
> 
> 
> Initial cover letter:
> 
> In oVirt, after switching from starting remote-viewer through the Spice-XPI
> plugin to starting remote-viewer by downloading a .vv file, the oVirt portal
> lost the ability to specify a so-called 'foreign menu' which remote-viewer
> would display in its UI.
> 
> This patch series readds this support when using .vv files, though it does
> it differently. Rather than letting the oVirt portal specify an arbitrary
> menu, this series teaches remote-viewer to use the oVirt REST API to
> create a predefined menu similar to the foreign menu. Currently, this
> menu will only list the ISOs available in oVirt for insertion in the
> VM CDRom.
> 
> This patch to librest https://bugzilla.gnome.org/show_bug.cgi?id=708359 
> is needed for this support to work, and due to small bugs in oVirt REST
> API, using oVirt 3.4 is recommended. oVirt will need to be modified to
> fill the necessary parameters in its .vv file for this to work from the
> oVirt portal, but this can already be tested with a direct ovirt://
> connection.
> 
> 
> Christophe
> 
> _______________________________________________
> virt-tools-list mailing list
> virt-tools-list at redhat.com
> https://www.redhat.com/mailman/listinfo/virt-tools-list





More information about the virt-tools-list mailing list