interest to integrate virt-manager?

interest to integrate virt-manager?

[Gotthard, Petr]

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

Hello,

I managed to build virt-manager (plus virt-viewer and the virt-* scipts) for Yocto, so I wonder if you would be interested to integrate the virt-manager (and related bitbake recipes) into the meta-virtualization? Or is there another recommended graphical manager for KVM?
https://virt-manager.org/

New virt-manager releases unfortunately require python-pygobject 3.0, which is (seems to be) not supported in Yocto (yet). I wanted to avoid the GObject Introspection (dependency on meta-gir), so I have scripts for virt-manager 0.9.5 only, which is the latest GTK2 release. (It's better than nothing.)

Shall I just post the .bb files (or a long list of patches), or would you prefer another approach? The virt-manager depends on gtk-vnc and few python-* packages that I also had to create. Should the new python-* packages required by virt-manager go also into meta-virtualization (as no one else is apparently using them), or shall these go into some other layer?

Please advise.


Cheers,
Petr


[-- Attachment #2: Type: text/html, Size: 3217 bytes --]

Re: interest to integrate virt-manager?

[Bruce Ashfield]

On Fri, Apr 10, 2015 at 8:19 AM, Gotthard, Petr
<Petr.Gotthard@honeywell.com> wrote:
> Hello,
>
>
>
> I managed to build virt-manager (plus virt-viewer and the virt-* scipts) for
> Yocto, so I wonder if you would be interested to integrate the virt-manager
> (and related bitbake recipes) into the meta-virtualization? Or is there
> another recommended graphical manager for KVM?

I'm definitely interested .. see below.

>
> https://virt-manager.org/
>
>
>
> New virt-manager releases unfortunately require python-pygobject 3.0, which
> is (seems to be) not supported in Yocto (yet). I wanted to avoid the GObject
> Introspection (dependency on meta-gir), so I have scripts for virt-manager
> 0.9.5 only, which is the latest GTK2 release. (It’s better than nothing.)

:)

We also have virt-manager recipes and uncompleted work here, it slammed
into g-i-r and stopped .. needing on target compilation to finish the packaging
of virt-manager.

So I feel your pain!

At some point, we will need to figure this out, but having an older version in
the tree until that happens makes a lot of sense.

I'll compare what you have versus those other changes, and see what we can
pull together.

>
>
>
> Shall I just post the .bb files (or a long list of patches), or would you
> prefer another approach? The virt-manager depends on gtk-vnc and few

Post the bb files. If you want to capture any significant points in
your development
history, feel free to split the patches. But otherwise, post a series that is
clean, and introduces the recipes from scratch directly to a working version.

> python-* packages that I also had to create. Should the new python-*
> packages required by virt-manager go also into meta-virtualization (as no
> one else is apparently using them), or shall these go into some other layer?

Start them in meta-virt, for initial introduction I prefer to have
support python
libraries near the code that actually exercises them!

Bruce

>
>
>
> Please advise.
>
>
>
>
>
> Cheers,
>
> Petr
>
>
>
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: interest to integrate virt-manager?

[Rob Woolley]

On 4/10/2015 9:52 AM, Bruce Ashfield wrote:
> On Fri, Apr 10, 2015 at 8:19 AM, Gotthard, Petr
> <Petr.Gotthard@honeywell.com> wrote:
>> Hello,
>>
>>
>>
>> I managed to build virt-manager (plus virt-viewer and the virt-* scipts) for
>> Yocto, so I wonder if you would be interested to integrate the virt-manager
>> (and related bitbake recipes) into the meta-virtualization? Or is there
>> another recommended graphical manager for KVM?
> I'm definitely interested .. see below.
>
>> https://virt-manager.org/
>>
>>
>>
>> New virt-manager releases unfortunately require python-pygobject 3.0, which
>> is (seems to be) not supported in Yocto (yet). I wanted to avoid the GObject
>> Introspection (dependency on meta-gir), so I have scripts for virt-manager
>> 0.9.5 only, which is the latest GTK2 release. (It’s better than nothing.)
> :)
>
> We also have virt-manager recipes and uncompleted work here, it slammed
> into g-i-r and stopped .. needing on target compilation to finish the packaging
> of virt-manager.

Hi Petr,

I was trying something similar.  I've shared my work here:

https://github.com/rcwoolley/meta-cloud-services/commits/virt-install
https://github.com/rcwoolley/meta-virtualization/commits/virt-install

To get things to work, I had to build gobject-introspection on the 
target itself.

Let me know if you're interested in collaborating.  As Bruce said, I 
temporarily put things on hold when I realized that I couldn't get any 
further without cross-building gobject-introspection.

Here are my raw notes on building it natively on the target:

rpm -Uvh \
   gtk-doc-stub-1.1+git0+1dea266593-r0.core2_64.rpm \
   gtk-doc-stub-dev-1.1+git0+1dea266593-r0.core2_64.rpm

# Remove the Makefile.introspection from gtk-doc-stub
# This must be done before you do "make install" for gobject-introspection
# Otherwise you will miss the cflags-begin feature
# 
https://github.com/GNOME/gobject-introspection/commit/7639a440b43ea1197de96035304404b0c87db608 

rm /usr/share/gobject-introspection-1.0/Makefile.introspection

rpm -Uvh \
   bison-2.7.1-r0.core2_64.rpm \
   libcairo-script-interpreter2-1.12.18-r0.core2_64.rpm \
   libcairo-perf-utils-1.12.18-r0.core2_64.rpm \
   libcairo-dev-1.12.18-r0.core2_64.rpm \
   libpixman-1-dev-0.32.6-r0.core2_64.rpm \
   libfontconfig-dev-2.11.1-r0.core2_64.rpm \
   libfreetype-dev-2.5.4-r0.core2_64.rpm \
   libpng16-dev-1.6.16-r0.core2_64.rpm

git clone git://git.gnome.org/gobject-introspection
cd gobject-introspection
./autogen.sh
./configure --prefix=/usr
make
make install

rpm -Uvh \
   gnome-common-3.14.0-r0.all.rpm \
   libsoup-2.4-dev-2.46.0-r0.core2_64.rpm \
   libxslt-dev-1.1.28-r0.core2_64.rpm \
   libcheck-0.9.14-r0.core2_64.rpm \
   libcheck-dev-0.9.14-r0.core2_64.rpm

git clone git://git.fedorahosted.org/libosinfo.git
cd libosinfo
# set --enable-gtk-doc to --disable-gtk-doc in autogen.sh
mkdir build
cd build
../autogen.sh --prefix=/usr
make

osinfo/Makefile: the libosinfo_1_0_la_CFLAGS variable should have 
-I$(top_builddir) too; to avoid a fatal error finding osinfo_enum_types.h

PROBLEM: python-gobject doesn't provide gi.repository

rpm -Uvh python-pycairo-dev-1.10.0-r2.core2_64.rpm
Copy pygobject-2.28.3.tar.bz2
tar -jxvf pygobject-2.28.3.tar.bz2
cd pygobject
./configure --prefix=/usr
cp $(which libtool) .

git clone git://git.gnome.org/pygobject
cd pygobject
# In autogen.sh replace the automake and aclocal checks for 1.11 with 1.15
./autogen.sh --prefix=/usr
make
make install

rpm -Uvh libvirt-libvirtd-1.2.12-r1.core2_64.rpm \
   dmidecode-2.12.-r0.core2_64.rpm \
   libbsd0-0.7.0-r0.core2_64.rpm \
   netcat-openbsd-1.105-r0.core2_64.rpm

At this point I was able to run virt-install and virt-manager and 
stopped there.

Cheers,
Rob

Re: interest to integrate virt-manager?

[Gotthard, Petr]

I thought I was not the only one trying to make this working. ;-)

(1) I made a temporary github repository with my work
https://github.com/gotthardp/recipes-virt-manager
It's not a standalone layer; you need is to clone this into meta-virtualization (or any other layer).

(2) It requires python support in libxml2, which was not enabled by default in the dizzy release. There is already a patch for that I'm using:
http://patchwork.openembedded.org/patch/82407/
I also had to enable python in libxml2 explicitly in my local.conf, but I suspect there is a better way
PACKAGECONFIG_append_pn-libxml2 = " python"
PACKAGECONFIG_append_pn-libxml2-native = " python"

(3) In addition to that, the meta-virtualization/recipes-extended/fontconfig has one minor bug that needs to be fixed. I use the following patch (again, this may not be the cleanest way)

diff -u old/fontconfig.pc.in new/fontconfig.pc.in
--- old/fontconfig.pc.in        2014-01-20 09:14:20.000000000 +0100
+++ new/fontconfig.pc.in        2015-03-25 10:42:38.285970575 +0100
@@ -15,4 +15,4 @@
 Requires.private: @PKGCONFIG_REQUIRES_PRIVATELY@
 Libs: -L${libdir} -lfontconfig
 Libs.private: @EXPAT_LIBS@ @FREETYPE_LIBS@ @ICONV_LIBS@ @LIBXML2_LIBS@
-Cflags: -I${includedir} @EXPAT_CFLAGS@ @FREETYPE_CFLAGS@ @ICONV_CFLAGS@ @LIBXML2_CFLAGS@
+Cflags: -I${includedir} @EXPAT_CFLAGS@ -I${includedir}/freetype2 @ICONV_CFLAGS@ @LIBXML2_CFLAGS@

(the generated fonconfig.pc contains paths to the building machine; I suspect the *.pc.in should not include any @MACROS@)


That's all. Now you should be able to build the virt-manager. I'm using the dizzy release of poky. If it does not work for you, please let me know; I went through several troubles, so I may know a solution.

It would be great if this get eventually merged into meta-virt.


Cheers,
Petr

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@gmail.com] 
Sent: 10. dubna 2015 15:53
To: Gotthard, Petr
Cc: meta-virtualization@yoctoproject.org
Subject: Re: [meta-virtualization] interest to integrate virt-manager?

On Fri, Apr 10, 2015 at 8:19 AM, Gotthard, Petr
<Petr.Gotthard@honeywell.com> wrote:
> Hello,
>
>
>
> I managed to build virt-manager (plus virt-viewer and the virt-* scipts) for
> Yocto, so I wonder if you would be interested to integrate the virt-manager
> (and related bitbake recipes) into the meta-virtualization? Or is there
> another recommended graphical manager for KVM?

I'm definitely interested .. see below.

>
> https://virt-manager.org/
>
>
>
> New virt-manager releases unfortunately require python-pygobject 3.0, which
> is (seems to be) not supported in Yocto (yet). I wanted to avoid the GObject
> Introspection (dependency on meta-gir), so I have scripts for virt-manager
> 0.9.5 only, which is the latest GTK2 release. (It’s better than nothing.)

:)

We also have virt-manager recipes and uncompleted work here, it slammed
into g-i-r and stopped .. needing on target compilation to finish the packaging
of virt-manager.

So I feel your pain!

At some point, we will need to figure this out, but having an older version in
the tree until that happens makes a lot of sense.

I'll compare what you have versus those other changes, and see what we can
pull together.

>
>
>
> Shall I just post the .bb files (or a long list of patches), or would you
> prefer another approach? The virt-manager depends on gtk-vnc and few

Post the bb files. If you want to capture any significant points in
your development
history, feel free to split the patches. But otherwise, post a series that is
clean, and introduces the recipes from scratch directly to a working version.

> python-* packages that I also had to create. Should the new python-*
> packages required by virt-manager go also into meta-virtualization (as no
> one else is apparently using them), or shall these go into some other layer?

Start them in meta-virt, for initial introduction I prefer to have
support python
libraries near the code that actually exercises them!

Bruce

>
>
>
> Please advise.
>
>
>
>
>
> Cheers,
>
> Petr
>
>
>
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: interest to integrate virt-manager?

[Mihaylov, Emil]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Hi
anybody added virt-viewer/virt-manager  receipt to  meta-virtualization
Thanks Emil





Spirent Communications e-mail confidentiality.
------------------------------------------------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300

[-- Attachment #2: Type: text/html, Size: 2993 bytes --]