Skip to content
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

iperf3 causes virtio device to panic on macOS #99

Open
kdrag0n opened this issue Nov 27, 2022 · 0 comments
Open

iperf3 causes virtio device to panic on macOS #99

kdrag0n opened this issue Nov 27, 2022 · 0 comments

Comments

@kdrag0n
Copy link

kdrag0n commented Nov 27, 2022

I'm trying to run iperf3 to benchmark TSI on an M1 host running macOS 13. A panic occurs in a virtio device after sending about 1.3 GB:

/ # iperf3 -c 10.1.1.3
Connecting to host 10.1.1.3, port 5201
[  5] local 0.0.0.0 port 0 connected to 10.1.1.3 port 5201
thread 'fc_vcpu 1' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 35, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/devices/src/virtio/mmio.rs:322:53
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'fc_vcpu 0' panicked at 'Failed to acquire device lock: PoisonError { .. }', src/devices/src/bus.rs:150:18

The panic seems to be here:

eventfd.write(v as u64).unwrap();

Steps to reproduce:

  • iperf3 -s on host
  • Run a container with krunvm (e.g. Alpine) and install iperf3
  • iperf3 -c <host external LAN IP> in VM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant