ARM64 and KVM - 'bus error'

[Paul H]

Hello everyone,

I've been working on performance tests with gVisor for a while now.

I have two single-board systems. One is a Raspberry Pi 5, the other is an Intel-based system.

Everything works perfectly on both platforms using Systrap.

However, as soon as I define KVM as the "--platform" parameter, I run into some problems with the Raspberry Pi.

I'm using Docker, and the container is Ubuntu 24.04.

Even with `apt update`, I encounter difficulties on the Raspberry Pi.
If I try to run `service apache2 start`, I get a "Bus error".
Therefore, I can't install or run anything within this container.

The same procedure on the x86 system causes no problems whatsoever.

What could be causing the problem?

Thanks in advance.

Cheers,
-paul

Docker: 29.3.0, build 5927d80
Runsc: release-20260302.0 spec: 1.1.0-rc.1

[Konstantin Bogomolov]

Hi Paul,

Can you provide debug logs of the crash? You can do so by using the `--debug` and `--debug-log=mycrash.log` flags.

Thanks,

Konstantin

[Jimmy Tran]

+1 on Konstantin's ask.

Thank you for reaching out. That is an interesting issue with the Pi 5 and the KVM platform. Could you please open a GitHub issue to track this?

You mentioned encountering difficulties with apt update . When you create the ticket, could you please include the exact error output from that command?

Thanks!

JT

--
You received this message because you are subscribed to the Google Groups "gVisor Users [Public]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gvisor-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/gvisor-users/71941402-10d8-48aa-beda-4ab4fdd7442fn%40googlegroups.com.

[Paul H]

Hello again,

my mistake, I've now managed to generate logs, however, no further logs are being generated when the "Bus error" occurs within the container.

Attached are the boot, create, gofer and start logs.

Perhaps you can already see the problem?

Thanks,
-paul

[Paul H]

Good morning,

Thank you for your prompt replies.
I started the container with both debug options enabled.

Unfortunately, no debug logs are being created.

Here is the screen output.

The message about the Apache2 configuration only appeared once, and that was the very first time it's come up.

Thanks in advance.

'apt update'

Hit:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
 Err:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
   Sub-process apt-key exited unexpectedly
 Get:2 http://ports.ubuntu.com/ubuntu-ports noble-updates InRelease [126 kB]
 Get:3 http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease [126 kB]
 Get:4 http://ports.ubuntu.com/ubuntu-ports noble-security InRelease [126 kB]
 Get:5 http://ports.ubuntu.com/ubuntu-ports noble-updates/universe arm64 Packages [1975 kB]
 Err:3 http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease
   Sub-process apt-key exited unexpectedly
 Err:4 http://ports.ubuntu.com/ubuntu-ports noble-security InRelease
   Sub-process apt-key exited unexpectedly
 Get:6 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages [2388 kB]
 Get:7 http://ports.ubuntu.com/ubuntu-ports noble-updates/restricted arm64 Packages [4825 kB]
 Fetched 9567 kB in 3s (3393 kB/s)
 Reading package lists... Done
 Building dependency tree... Done
 Reading state information... Done
 12 packages can be upgraded. Run 'apt list --upgradable' to see them.
 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ports.ubuntu.com/ubuntu-ports noble InRelease: Sub-process apt-key exited unexpectedly
 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease: Sub-process apt-key exited unexpectedly
 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ports.ubuntu.com/ubuntu-ports noble-security InRelease: Sub-process apt-key exited unexpectedly
 W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble/InRelease  Sub-process apt-key exited unexpectedly
 W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble-backports/InRelease  Sub-process apt-key exited unexpectedly
 W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble-security/InRelease  Sub-process apt-key exited unexpectedly
 W: Some index files failed to download. They have been ignored, or old ones used instead.

-----

 root@e3a42b62be48:/# service apache2 start
  * Starting Apache httpd web server apache2        *
  * The apache2 configtest failed.
 Output of config test was:
 Bus error
 
 root@e3a42b62be48:~# service start apache2
 Bus error
 root@e3a42b62be48:~#
 
 
 root@e3a42b62be48:~# apache2ctl configtest
 Bus error
 root@e3a42b62be48:~#

Jimmy Tran schrieb am Montag, 9. März 2026 um 18:37:25 UTC+1:

[Paul H]

Hello,

So, I tried again to reproduce everything and understand how the logging actually works.

Here's the excerpt from the boot.log where the process was recorded, where I try to start Apache2 with 'service apache2 start' and get the error message 'Bus error'.

Thanks!