-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigating guestagent on FreeBSD, for containerd with runj #1509
Conversation
203840a
to
a1334ce
Compare
I found some old code that I hadn't pushed, it needs to be rebased and cleaned up |
69ae100
to
1464d47
Compare
Note: there is no use case for FreeBSD yet, except for "it exists" and in order to test |
362f41e
to
a4a8044
Compare
@@ -5,6 +5,12 @@ images: | |||
arch: "x86_64" | |||
- location: https://download.freebsd.org/ftp/snapshots/VM-IMAGES/14.0-CURRENT/aarch64/Latest/FreeBSD-14.0-CURRENT-arm64-aarch64.qcow2.xz | |||
arch: "aarch64" | |||
- location: https://download.freebsd.org/ftp/snapshots/VM-IMAGES/14.0-CURRENT/riscv64/Latest/FreeBSD-14.0-CURRENT-riscv-riscv64.qcow2.xz | |||
arch: "riscv64" | |||
kernel: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this u-boot image was mostly a hack to get past the validate (for amd64/arm64), but it is the real image:
https://wiki.freebsd.org/riscv/QEMU
We might want to import it to https://github.com/lima-vm/u-boot-qemu-mirror/ proper, so it can be used here.
The image does seem to be booting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why can't we use Debian's u-boot binary for FreeBSD?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that should be fine as well, just haven't tested it.
writable: true | ||
|
||
additionalDisks: | ||
- "zfs" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ZFS disk is actually only needed if wanting to run containers, it will boot fine without it.
a4a8044
to
b25f65b
Compare
b25f65b
to
4e0692f
Compare
Note: the build configuration for guest agent defaults to FreeBSD disabled (only Linux enabled), so you want to make sure to enable this before building and installing...
|
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
4e0692f
to
2977188
Compare
Needs rebase. Does cloud-init work with FreeBSD? |
I think it could work (in theory at least), but that it is not included by default in the ISO image. It seems to be quite new: https://www.freebsd.org/status/report-2023-01-2023-03/cloud-init/ Previous PR was without any cidata. |
https://samuel.karp.dev/blog/2021/05/running-freebsd-jails-with-containerd-1-5/
https://productionwithscissors.run/2022/09/04/containerd-linux-on-freebsd/
There is no systemd on BSD, so it needs to use
/var/run
.GNU bash is in
/usr/local/bin/bash
, default is/bin/csh
.Eventually it should use BSM Audit events, but empty here.Using a simple
sockstat
call, instead of trying to get kernel eventsAdded "os"
Issue #1508
Related #1735