All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Woolley <rob.woolley@windriver.com>
To: <meta-virtualization@yoctoproject.org>
Subject: Re: interest to integrate virt-manager?
Date: Fri, 10 Apr 2015 14:32:07 -0400	[thread overview]
Message-ID: <55281727.6040703@windriver.com> (raw)
In-Reply-To: <CADkTA4NsatnZUvVxPZFap=O33LPkhTa0rLJwhE4oPSQ-07+tzw@mail.gmail.com>



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


  reply	other threads:[~2015-04-10 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 12:19 interest to integrate virt-manager? Gotthard, Petr
2015-04-10 13:52 ` Bruce Ashfield
2015-04-10 18:32   ` Rob Woolley [this message]
2015-04-10 20:11   ` Gotthard, Petr
  -- strict thread matches above, loose matches on Subject: below --
2016-06-02  1:08 Mihaylov, Emil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55281727.6040703@windriver.com \
    --to=rob.woolley@windriver.com \
    --cc=meta-virtualization@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.