... | ... | @@ -3,7 +3,7 @@ Here's a list of features which are/ are not enabled on QEMU on redox: |
|
|
1. vde (virtual distributed network) - it seems to need a pkg called `vde2`
|
|
|
2. xen (seems to be a backend support for xen) - we don't support xen (also
|
|
|
`xen_ctrl_version`)
|
|
|
3. NOTE: linux-io-uring in the future. For now, linux-aio
|
|
|
3.
|
|
|
4. xfsctl : mostly used when host uses xfs filesystem
|
|
|
5. membarrier : It seems QEMU may function without it as it "reduces overhead" in multi core systems and not provide vital functionality
|
|
|
6. vhost* : may need KVM; it mainly accelarates virtio to perform better,so excluded
|
... | ... | @@ -17,7 +17,12 @@ Here's a list of features which are/ are not enabled on QEMU on redox: |
|
|
14. secret_keyring : not sure what that is
|
|
|
15. libdaxctl : may be needed only for virtio fs
|
|
|
16. auth-pam : not supported
|
|
|
17.
|
|
|
17. guest agent
|
|
|
18. linux_aio
|
|
|
19. linux_io_uring (future)
|
|
|
20. guest_agent
|
|
|
21. redox is non-kvm, so no linux headers included (while building)
|
|
|
|
|
|
|
|
|
Some libraries that seem to be needed, but are removed:
|
|
|
1. ncursesw : recipe failed to build
|
... | ... | @@ -31,7 +36,18 @@ Some libraries that seem to be needed, but are removed: |
|
|
9.
|
|
|
|
|
|
Currently undergoing testing:
|
|
|
1. guest agent
|
|
|
2.
|
|
|
1. removed `env` (setjmp.h dependency) - may be restored soon
|
|
|
2. modified the
|
|
|
|
|
|
CONFIG_LINUX not replaced with CONFIG_REDOX since we're not sure:
|
|
|
1. qemu backend softmmu
|
|
|
2. u-boot scripts config whitelists
|
|
|
3. hmp_commands gpa2hpa
|
|
|
4. qemu fsdev softmmu
|
|
|
5. <the tests folder is excluded as it's deemed unnecessary at the moment>
|
|
|
6. qemu util util_ss
|
|
|
7. <none of the json files were checked: block-core, qom, sockets>
|
|
|
|
|
|
|
|
|
NOTE; `--enable-tools`, `coroutine-pool` needs to be verified i.e. exactly what it is doing. |
|
|
\ No newline at end of file |
|
|
> NOTE: `--enable-tools`, `coroutine-pool` needs to be verified i.e. exactly what it is doing.
|
|
|
> NOTE: we use "WARN" the way we use "TODO" to indicate stuff within the repo. |