Skip to content

Conversation

@ryanbreen
Copy link
Owner

Summary

  • Added VirtIO network device to all ARM64 QEMU test scripts to fix ENETUNREACH errors
  • Removed readonly=on flag from ext2 disk configuration to allow filesystem writes
  • Modified scripts to create writable copy of ext2 disk image before tests

Test plan

  • Run ARM64 boot test: ./docker/qemu/run-aarch64-boot-test-native.sh
  • Verify network syscalls no longer return ENETUNREACH
  • Verify filesystem write operations succeed

🤖 Generated with Claude Code

Fixes two categories of ARM64 test failures:

1. Network ENETUNREACH (~6 tests):
   - Root cause: VirtIO network device was not configured in QEMU
   - Fix: Added `-device virtio-net-device,netdev=net0 -netdev user,id=net0`
   - Result: http_test, dns_test now pass

2. Filesystem write errors (~6 tests):
   - Root cause: ext2 disk mounted with `readonly=on` flag
   - Fix: Create writable copy of disk, remove readonly flag
   - Result: Write operations now work

Scripts modified:
- run-aarch64-boot-test-native.sh
- run-aarch64-boot-test-strict.sh
- run-aarch64-interactive.sh
- run-aarch64-test-runner.py
- run-aarch64-test-suite.sh
- run-aarch64-test.exp
- run-aarch64-test.sh
- run-aarch64-userspace-test.sh
- run-aarch64-userspace.sh

Updated arm64-parity.md with session notes and status updates.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@ryanbreen ryanbreen merged commit e31b245 into main Feb 2, 2026
0 of 2 checks passed
@ryanbreen ryanbreen deleted the fix/arm64-network-and-fs-writes branch February 2, 2026 21:54
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

Successfully merging this pull request may close these issues.

2 participants