|
Re: Loading the module xen-gntdev on boot
Hi Paulo,
This should not impact the module loading.
This is the interesting file.
It shall be used by systemd on boot to load the modules required by Xen.
Please check if gntdev is listed
Hi Paulo,
This should not impact the module loading.
This is the interesting file.
It shall be used by systemd on boot to load the modules required by Xen.
Please check if gntdev is listed
|
By
Bertrand Marquis
·
#7101
·
|
|
Re: Loading the module xen-gntdev on boot
Hi Bertrand,
One very important piece of information I missed to disclose: I am not
using runqemu,
as it was not being properly set by the resulting bitbake build (the
resulting image was
pointing to
Hi Bertrand,
One very important piece of information I missed to disclose: I am not
using runqemu,
as it was not being properly set by the resulting bitbake build (the
resulting image was
pointing to
|
By
Paulo Sherring
·
#7100
·
|
|
Re: Loading the module xen-gntdev on boot
Hi Paulo,
Hardknott is long term while honister is not but both are stable releases.
I am not quite sure I get your 4.14 pulling 4.16. The 4.14 recipe is building the latest 4.14 version of
Hi Paulo,
Hardknott is long term while honister is not but both are stable releases.
I am not quite sure I get your 4.14 pulling 4.16. The 4.14 recipe is building the latest 4.14 version of
|
By
Bertrand Marquis
·
#7099
·
|
|
Re: Loading the module xen-gntdev on boot
Hello Bertrand,
<Bertrand.Marquis@...> wrote:
Oops, my mistake, sorry.
The main reason was that hardknott is tagged as a stable release and
it already includes xen 4.14 or latest (it is actually
Hello Bertrand,
<Bertrand.Marquis@...> wrote:
Oops, my mistake, sorry.
The main reason was that hardknott is tagged as a stable release and
it already includes xen 4.14 or latest (it is actually
|
By
Paulo Sherring
·
#7098
·
|
|
Re: Loading the module xen-gntdev on boot
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.
Please see some questions here after.
Any reason not to use
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.
Please see some questions here after.
Any reason not to use
|
By
Bertrand Marquis
·
#7097
·
|
|
Re: Loading the module xen-gntdev on boot
Hi Paulo,
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
Hi Paulo,
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
|
By
Bertrand Marquis
·
#7096
·
|
|
Loading the module xen-gntdev on boot
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
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
|
By
Paulo Sherring
·
#7095
·
|
|
Re: [PATCH] ceph: set CXXFLAGS and CFLAGS
The phrase:
"was added ... which removes"
is awkward. As a student of Strunk and White, I suggest:
---
In oe-core, the commit:
a83623a54a Revert "cmake.bbclass: Set CXXFLAGS and CFLAGS"
drops
The phrase:
"was added ... which removes"
is awkward. As a student of Strunk and White, I suggest:
---
In oe-core, the commit:
a83623a54a Revert "cmake.bbclass: Set CXXFLAGS and CFLAGS"
drops
|
By
Randy MacLeod
·
#7094
·
|
|
[PATCH] ceph: set CXXFLAGS and CFLAGS
commit a83623a54a375d3ae9198a135b94379881a2b7a5 was added
to oe-core which removes CXXFLAGS and CFLAGS causing
compilation for ceph to fail.
Set CXXFLAGS and CFLAGS to resolve the
commit a83623a54a375d3ae9198a135b94379881a2b7a5 was added
to oe-core which removes CXXFLAGS and CFLAGS causing
compilation for ceph to fail.
Set CXXFLAGS and CFLAGS to resolve the
|
By
sakib.sajal@...
·
#7093
·
|
|
Re: [PATCH] xen: Override CC and CPP in make command line
No problem. I did the cherry pick.
Bruce
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
No problem. I did the cherry pick.
Bruce
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
|
By
Bruce Ashfield
·
#7092
·
|
|
Re: [PATCH] cloud-init: inherit setuptools3_legacy
merged
Bruce
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
merged
Bruce
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
|
By
Bruce Ashfield
·
#7091
·
|
|
Re: [PATCH] xen: Override CC and CPP in make command line
Hi Bruce,
Could this be also added in honister branch ?
Thanks
Bertrand
Hi Bruce,
Could this be also added in honister branch ?
Thanks
Bertrand
|
By
Bertrand Marquis
·
#7090
·
|
|
[PATCH] cloud-init: inherit setuptools3_legacy
cloud-init still requires legacy setup.py behavior.
Signed-off-by: Tim Orling <tim.orling@...>
---
recipes-extended/cloud-init/cloud-init_21.4.bb | 2 +-
1 file changed, 1 insertion(+), 1
cloud-init still requires legacy setup.py behavior.
Signed-off-by: Tim Orling <tim.orling@...>
---
recipes-extended/cloud-init/cloud-init_21.4.bb | 2 +-
1 file changed, 1 insertion(+), 1
|
By
Tim Orling
·
#7089
·
|
|
Re: [meta-virt][PATCH 1/1] libvert: modify dependencies on lxc_protocol.h
I have never seen the failure. This is from a build that did see it.
NOTE: recipe qemu-6.2.0-r0: task do_package_qa: Succeeded
NOTE: recipe libvirt-7.2.0-r0: task do_configure: Succeeded
NOTE:
I have never seen the failure. This is from a build that did see it.
NOTE: recipe qemu-6.2.0-r0: task do_package_qa: Succeeded
NOTE: recipe libvirt-7.2.0-r0: task do_configure: Succeeded
NOTE:
|
By
Joe Slater
·
#7088
·
|
|
Re: [meta-cloud-services][PATCH] layer.conf: Update to kirkstone namespace
merged.
Bruce
In message: [meta-virtualization][meta-cloud-services][PATCH] layer.conf: Update to kirkstone namespace
on 10/03/2022 wangmy wrote:
merged.
Bruce
In message: [meta-virtualization][meta-cloud-services][PATCH] layer.conf: Update to kirkstone namespace
on 10/03/2022 wangmy wrote:
|
By
Bruce Ashfield
·
#7087
·
|
|
Re: [PATCH] xen: Override CC and CPP in make command line
I've merged the patch, if Christopher has any review comments or needs
changes, we'll stack them on top.
Bruce
In message: [meta-virtualization] [PATCH] xen: Override CC and CPP in make command
I've merged the patch, if Christopher has any review comments or needs
changes, we'll stack them on top.
Bruce
In message: [meta-virtualization] [PATCH] xen: Override CC and CPP in make command
|
By
Bruce Ashfield
·
#7086
·
|
|
Re: [meta-virt][PATCH 1/1] libvert: modify dependencies on lxc_protocol.h
s/libvert/libvirt/
In message: [meta-virtualization] [meta-virt][PATCH 1/1] libvert: modify dependencies on lxc_protocol.h
on 10/03/2022 Joe Slater wrote:
Can you document the configuration (i.e.
s/libvert/libvirt/
In message: [meta-virtualization] [meta-virt][PATCH 1/1] libvert: modify dependencies on lxc_protocol.h
on 10/03/2022 Joe Slater wrote:
Can you document the configuration (i.e.
|
By
Bruce Ashfield
·
#7085
·
|
|
[meta-virt][PATCH 1/1] libvert: modify dependencies on lxc_protocol.h
src/remote/meson.build does not create a dependency on
the generated lxc_protocol.h for remote_daemon.c. Restructure
how this file is generated to allow the dependency.
Signed-off-by: Joe Slater
src/remote/meson.build does not create a dependency on
the generated lxc_protocol.h for remote_daemon.c. Restructure
how this file is generated to allow the dependency.
Signed-off-by: Joe Slater
|
By
Joe Slater
·
#7084
·
|
|
Re: OCI images in yocto image
It is something I've used in the past as well (import on first boot),
but due to the nature of how the docker daemon, and tools run, it
isn't feasible to do on the build side (which is what you
It is something I've used in the past as well (import on first boot),
but due to the nature of how the docker daemon, and tools run, it
isn't feasible to do on the build side (which is what you
|
By
Bruce Ashfield
·
#7083
·
|
|
Re: OCI images in yocto image
Hi Bruce,
following up an old thread with some more toughts...
I have found another solution that I would like to have your input on. I'm installing the OCI-image output from Yocto in my image for
Hi Bruce,
following up an old thread with some more toughts...
I have found another solution that I would like to have your input on. I'm installing the OCI-image output from Yocto in my image for
|
By
Peter Bergin
·
#7082
·
|