All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Sherring <pauloasherring@gmail.com>
To: Bertrand Marquis <Bertrand.Marquis@arm.com>
Cc: "meta-virtualization@lists.yoctoproject.org"
	<meta-virtualization@lists.yoctoproject.org>, nd <nd@arm.com>
Subject: Re: [meta-virtualization] Loading the module xen-gntdev on boot
Date: Tue, 22 Mar 2022 12:38:54 +0000	[thread overview]
Message-ID: <CAG9RwPL2adysD-Wyu7eN2jmo85b-Ufx6TWoSe82dJ-XQRr02EQ@mail.gmail.com> (raw)
In-Reply-To: <E80D57C8-590D-4B2C-9A6A-5C4F5BEEA24E@arm.com>

Hello Bertrand,

On Tue, Mar 22, 2022 at 12:28 PM Bertrand Marquis
<Bertrand.Marquis@arm.com> wrote:
>
> Hi Paulo,
>
> Please always keep the mailing list in as me asking the questions does not mean I will necessarily be the one working on this.
>
Oops, my mistake, sorry.

> Please see some questions here after.
>
> > On 22 Mar 2022, at 12:03, Paulo Sherring <pauloasherring@gmail.com> wrote:
> >
> > Hello Bertrand,
> >
> > On Tue, Mar 22, 2022 at 10:44 AM Bertrand Marquis
> > <Bertrand.Marquis@arm.com> wrote:
> >>
> >> Hi Paulo,
> >>
> >>> On 22 Mar 2022, at 11:33, Paulo Sherring via lists.yoctoproject.org <pauloasherring=gmail.com@lists.yoctoproject.org> wrote:
> >>>
> >>> Hello all,
> >>> I am a bit new to meta-virtualization and to the Xen project And to
> >>> virtualizations, so please bear with me :)
> >>> I've been trying to make use of the xen project, currently targeting
> >>> qemu (and later on, rpi4). After messing around, I was able to boot
> >>> dom0 and a domU.
> >>> But, I had to add the xen-gntdev to the `modules-load.d,` because
> >>> `xenstored` was failing to start, due to some missing connection,
> >>> probably brought up by xen-gntdev module.
> >>>
> >>> As I am new to all this, I was just wondering if this is by design, or
> >>> this is an issue (and therefore, I should/could submit a patch).
> >>
> >> No problem at all and thanks a lot for the feedback.
> >> This should not happen and should be fixed.
> >>
> >> Could you tell us what you are building (which image) and what parameters did you set in your local.conf ?
> >>
> >
> > - Baseline is hardknott.
>
> Any reason not to use honester ?
>
The main reason was that hardknott is tagged as a stable release and
it already includes xen 4.14 or latest (it is actually pulling 4.16),
which I wanted/will need for RPi4 support.

> The rest of the configuration sounds about right.
> I will check why gntdev is not in.
>
> > - Target image is xen-minimal-image (for the host)
> > - On local.conf, I have
> >
> > require xen-host.conf
> > and the contents of such file is https://paste.debian.net/1235220/
> >
> > (Also below, just in case the link expires:)
> >
> > Thanks for the prompt answer.
> > Kind regards, Paulo.
> >
> > ## Machine Definitions:
> > MACHINE = "qemuarm64"
> >
> > ## Generate ext4 rootfs for manual handling:
> > IMAGE_FSTYPES:append = " ext4"
> >
> > ## Virtualization:
> > DISTRO_FEATURES:append = " virtualization xen"
> > IMAGE_INSTALL:append = " xen xen-tools"
> >
> > ## Kernel stuff:
> > IMAGE_INSTALL:append = " kernel-modules"
> >
> > # Extra Packages:
> > EXTRA_IMAGE_FEATURES = "debug-tweaks"
> > EXTRA_IMAGE_FEATURES:append = " tools-sdk"
> > EXTRA_IMAGE_FEATURES:append = " tools-debug"
> > EXTRA_IMAGE_FEATURES:append = " eclipse-debug"
> > IMAGE_INSTALL:append = " nano findutils tree openssh"
> >
> >
> > ## Wayland stuff
> > DISTRO_FEATURES:remove = " x11"
> > DISTRO_FEATURES:append = " opengl wayland pam"
> >
> > ## Systemd stuff
> > DISTRO_FEATURES:append = " systemd pam "
> > VIRTUAL-RUNTIME_init_manager = "systemd"
> > DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
> > VIRTUAL-RUNTIME_initscripts = " systemd-compat-units"
> >
> > ## Connman:
> > IMAGE_INSTALL:append = " connman \
> >    connman-client \
> >    connman-static-ip \
> >    "
> >
> > EXTRA_IMAGEDEPENDS += "u-boot"
> > UBOOT_ELF = "u-boot"
> >
> >
> > IMAGE_INSTALL:append = " lvm2 bridge-utils"
> >
> > ## Extra space for fitting VMs:
> > IMAGE_ROOTFS_EXTRA_SPACE = "5242880"
> >
> >
>
> Cheers
> Bertrand
>
Thanks and kind regards, Paulo.


  reply	other threads:[~2022-03-22 12:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 10:33 Loading the module xen-gntdev on boot Paulo Sherring
2022-03-22 10:44 ` [meta-virtualization] " Bertrand Marquis
     [not found]   ` <CAG9RwPKUk+cY4wOStyFqHchmm9vJYrFZxtjpC0V9iwrQ+9XdYw@mail.gmail.com>
2022-03-22 12:27     ` Bertrand Marquis
2022-03-22 12:38       ` Paulo Sherring [this message]
2022-03-22 12:58         ` Bertrand Marquis
2022-03-22 15:01           ` Paulo Sherring
2022-03-22 15:22             ` Bertrand Marquis
2022-03-22 15:30               ` Diego Sueiro
2022-03-22 15:52                 ` Paulo Sherring
2022-03-23  8:38                   ` Bertrand Marquis
2022-03-23 10:30                     ` Richard Purdie
2022-03-23 21:17                       ` Bruce Ashfield
2022-03-24  8:42                         ` Bertrand Marquis
2022-03-24 12:06                           ` Bruce Ashfield
2022-03-24 13:03                             ` Bertrand Marquis
2022-03-24 13:18                               ` Bruce Ashfield
     [not found]                   ` <16DEF5BD23F06258.15837@lists.yoctoproject.org>
2022-03-23  9:03                     ` Bertrand Marquis

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=CAG9RwPL2adysD-Wyu7eN2jmo85b-Ufx6TWoSe82dJ-XQRr02EQ@mail.gmail.com \
    --to=pauloasherring@gmail.com \
    --cc=Bertrand.Marquis@arm.com \
    --cc=meta-virtualization@lists.yoctoproject.org \
    --cc=nd@arm.com \
    /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.