-
Notifications
You must be signed in to change notification settings - Fork 27
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
vm_virtio_net: add zcu102 support #57
Conversation
731cb18
to
39efe78
Compare
The ZCU102 hardware tests are failing in my test hack at #64 that uses seL4/ci-actions#319. |
275be01
to
00ebce4
Compare
Which one is failing? This is what I get on a local run:
|
Okay, I see it now. I don't think the init script is configured properly in the overlay fs. I've loaded some init scripts before, so I should be able to make the change to get it working right |
Alright, I got the
|
bfa7446
to
fc3773c
Compare
I did try to compile a static version of arping for an aarch64 host, but it didn't work. So for now, I just err out with |
If we have the ping test working, that makes a good baseline to merge everything. We can easily leave the other test out for now. |
That works for me. What is the "dependency chain" we want to work with here? I'm thinking we start with the vm_minimal 2018.3 Petalinux version commit, then I can update this, and the other vm_minimal to follow that same methodology. |
We have minimal and ping working now (https://github.com/seL4/camkes-vm-examples/actions/runs/7699640620/job/20981854409?pr=64), so for me this looks like a good point to merge things - @lsf37 ? |
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.
Looks ok to me.
FYI, I tried to update this to also run with Petalinux 2021.1, and it does. However, there seems to be an issue with the device tree generation and the virtio-pci? I get this line: |
6af071d
to
ec6c485
Compare
I need to compile artifacts for 2022.1 for a different project. You can add |
I've gotten 2022.1 booting, but there are some permissions issues that i'll have to work through
Probably just a configuration value in the buildroot/petalinux configuration. |
Happy to start merging things for these two and add |
Got the ping and arping tests working with 2022.1 Petalinux:
2022.1 switched from init.d -> systemd, which means I needed to add a |
40777c1
to
f6ded33
Compare
Signed-off-by: Chris Guikema <[email protected]>
f6ded33
to
0bc0a8e
Compare
Seems my CI test job crashes on the hardware run, see #64. It should pick up you latest change, is some configuration missing there? |
Does it always try to load two images to the same address? |
Here is a good run:
On the failing runs, its actually running a @lsf37 did something change with the ZCU102 hardware? |
There has been seL4/ci-actions#310, but this was revered by seL4/ci-actions#324. However, there is this change to binary images that might impact this, see seL4/machine_queue#14 |
It's possible that the machine queue update yesterday messed something up. It shouldn't have, but it's shell scripts.. Edit: rerunning https://github.com/seL4/camkes-vm-examples/actions/runs/7705607749 which has previously passed, to check if it's something with the infrastructure. |
My fault as I was changing stuff around yesterday, fixed now. |
(Edit: testing with merged PRs)