All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Compagnucci <angelo@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add libvirt (KVM) support
Date: Sun, 26 May 2019 22:14:54 +0200	[thread overview]
Message-ID: <CA+_SqVY2wACSL=-5rugRsL0O+kKJqHnqgSzc1ouuy=9gcoRDjQ@mail.gmail.com> (raw)
In-Reply-To: <25259681-75b6-fe4b-bb4b-e9a903f48058@mind.be>

On Sun, May 26, 2019 at 3:21 PM Arnout Vandecappelle <arnout@mind.be> wrote:
>
>  Hi Angelo, Christopher,
>
> On 15/04/2019 16:54, Christopher Peeters wrote:
> > On 15/04/2019 16:06, Angelo Compagnucci wrote:
> >> On Mon, Apr 15, 2019 at 2:23 PM Arnout Vandecappelle <arnout@mind.be> wrote:
> >>>  Hi Christopher,
> >>>
> >>>  Plese don't top-post, but reply inline like I do below.
> >>>
> >>> On 15/04/2019 09:46, Christopher Peeters wrote:
> >>>> Hi Thomas,
> >>>>
> >>>> Thank you for your email. I wasn't aware about the commit title
> >>>> conventions so I will fix this.
> >>>>
> >>>> The reason why I selected a different distribution is the lack of
> >>>> support for Libvirt by the original distribution.
> >>>  I would prefer in that case that we always use this other distribution (which
> >>> is actually the same distribution, right? bionic == ubuntu1804...).
> >> I wouldn't like to use this distribution if possible, is not the
> >> official one and not maintained by canonical. The official one is:
> >>
> >> https://app.vagrantup.com/ubuntu/boxes/bionic64
> > As I said before there's no support from Canonical for libvirt images.
> > This can only be solved by Canonical. And if I look at Launchpad, it
> > won't happen very soon. There's another question for LXC support open
> > for more then a year now.
> >
> > An other option when preferring official images is to switch over to one
> > of the following boxes since they do understand that source projects
> > should support each other and therefore have support for libvirt in
> > their Vagrant boxes. I haven't tested them though.
> >
> > - https://app.vagrantup.com/debian/boxes/stretch64
>
>  Without understanding all this vagrant stuff, I would say that simply switching
> away from Ubuntu and to Debian sounds like the right thing to do, no? Debian
> stable is definitely a distro we want to have supported at all times.

The only thing that bothers me is that the debian images for vagrant
are not official and only maintained by a single person
(https://app.vagrantup.com/debian).
On the contrary, Ubuntu images are officially maintained by canonical
into their efforts for ubuntu on cloud.

Alternatively we can switch to Fedora which is officially supported
and supports libvirt, but we have to completetly rewrite the provision
section of the vagrantfile.

>
>  Regards,
>  Arnout
>
> >
> > - https://app.vagrantup.com/centos/boxes/7
> >
> > - https://app.vagrantup.com/fedora/boxes/29-atomic-host
> >
> > - https://app.vagrantup.com/opensuse/boxes/openSUSE-15.0-x86_64
> >
> > - https://app.vagrantup.com/archlinux/boxes/archlinux
> >

  reply	other threads:[~2019-05-26 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 17:36 [Buildroot] [PATCH 1/1] Add libvirt (KVM) support Christopher Peeters
2019-04-13 20:21 ` Thomas Petazzoni
2019-04-15  7:46   ` Christopher Peeters
2019-04-15 12:23     ` Arnout Vandecappelle
2019-04-15 14:06       ` Angelo Compagnucci
2019-04-15 14:54         ` Christopher Peeters
2019-05-13 11:34           ` Christopher Peeters
2019-05-26 13:21           ` Arnout Vandecappelle
2019-05-26 20:14             ` Angelo Compagnucci [this message]
2019-05-26 21:30               ` Arnout Vandecappelle
2019-05-27  7:04               ` Thomas Petazzoni
2019-05-27  7:24                 ` Angelo Compagnucci

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='CA+_SqVY2wACSL=-5rugRsL0O+kKJqHnqgSzc1ouuy=9gcoRDjQ@mail.gmail.com' \
    --to=angelo@amarulasolutions.com \
    --cc=buildroot@busybox.net \
    /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.