Issues filed for mirage/mirage

View Full Project
Do you use mirage? Leave a review!

Rate of open issues in the last 60 days

mirage open issues (View Closed Issues)
  • about 2 years remove Str module
  • about 2 years platforms (xen/solo5)
  • about 2 years TCP/UDP v4/v6 woes
  • about 2 years infrastructure tasks for mirage3
  • about 2 years IP configuration --v4 ip/mask instead of --ip X --netmask Y
  • about 2 years should the type for interfaces be a numerical index, not a string?
  • about 2 years default network interface should be named something more generic
  • about 2 years determine compatibility with Google libfuzzer and oss-fuzz
  • about 2 years A way to know the cpu running time of the microkernel
  • about 2 years mirage vs Makefile
  • about 2 years update README - it shouldn't be so Xen-specific
  • about 2 years Stack.TCPV4.write do not return not even fail asynchronously.
  • about 2 years V1_LWT.CHANNEL
  • about 2 years mirage configure should be re-run when config.ml changes
  • about 2 years 32bit CI builds
  • about 2 years [tracking] docs.mirage.io
  • about 2 years uncaught exceptions in the networking stack
  • over 2 years mirage configure should not install depext by default
  • over 2 years doc: CLOCK -> PCLOCK
  • over 2 years Tracking issue towards MirageOS 3.0
  • over 2 years mirage.github.io completely broken
  • over 2 years Improved CI and end-to-end testing
  • over 2 years Simultaneous multi-backend support
  • over 2 years pending items for consideration for Mirage 3.0
  • over 2 years Centralise library/repository list and changelogs
  • over 2 years mirage.io updates/improvements
  • over 2 years mirage configure --no-opam reports ocamlfind packages, not opam packages
  • over 2 years arp and ip module types should assume one ip address and default gateway
  • over 2 years Non-TLS http_server / tcp_conduit_connector depend on nocrypto
  • over 2 years mirage configure --help and mirage help configure are not synonym
  • over 2 years mirage configure should detect and warn re: known unsupported (transitive) deps
  • almost 3 years Generated example .xl file should contain kernel arguments
  • almost 3 years IP.write can fail
  • almost 3 years Functoria: block device names get turned into Unix paths, even on Xen
  • almost 3 years Mirage + ocamlbuild + jsoo.ocamlbuild breakage
  • almost 3 years lots of noise generated in the `disk` field of `.xl` and `.xl.in` files
  • almost 3 years No way to specify package versions/pins in config.ml
  • almost 3 years Protection against key confusion
  • almost 3 years Embed crunch in an ELF section rather than static linking
  • about 3 years Inter-VM communications via Conduit
  • about 3 years Unikernel size
  • about 3 years Add native ARM64/Xen support
  • over 3 years Extract mirage scripts in independent libraries
  • over 3 years Improve the deployment model
  • over 3 years Incompatibility feedback at configure-time
  • over 3 years STACKV4.UDPV4 interface: callback handling
  • over 3 years Add an option to not generate the fat file
  • over 3 years Wrong computation of the fat image when using sub-directories
  • over 3 years Fix support for disk images
  • over 3 years The script to create the fat image doesn't work with symbolic links
  • over 3 years Allow the `main.native` Makefile target to be extended.
  • over 3 years `Mirage.load` doesn't work in bytecode
  • over 3 years Improve the Channel API
  • over 3 years Very large crunches can possibly overflow the Xen static segments
  • over 3 years Add package version constraints
  • over 3 years Test infrastructure
  • almost 4 years Deprecate libraries
  • almost 4 years Remove `V1`
  • almost 4 years tap0 interface is created with ipv6 only?
  • almost 4 years Customise HTTP server and OS name
  • about 4 years Add HTTP client generators to Mirage
  • about 4 years Add HVM booting support to MiniOS
  • about 4 years Mapping in foreign grants fails on ARM
  • over 4 years Async support in Mirage/Xen
  • over 4 years Comments on Mirage website posts
  • over 4 years xen: Avoid generating paths in Makefile containing '.opam/...'
  • over 4 years update docs for pkg-config dependency
  • over 4 years RRD logging support
  • over 4 years support accelerated netfront protocol
  • over 4 years DHCPv4: what do we do with Interface_mtu
  • almost 5 years dns cache: check for resolver poisoning
  • almost 5 years Cloud Init support
  • almost 5 years clean is too aggressive
  • almost 5 years Testing: packet generation using Ostinato
  • almost 5 years Experiment: Raspberry Pi backend
  • almost 5 years Experiment: UEFI backend
  • almost 5 years Document and port kFreeBSD backend
  • almost 5 years Port Baardskeerder to KV_RO
  • almost 5 years Get cohttp+vchan working across two domains
  • almost 5 years cross-compilation to ARM/Android
  • about 5 years Mirage-types: KV_RO `read` and `size` are inconsistent
  • about 5 years Update the DNS performance tests page on the wiki

mirage closed issues

  • about 2 years tracing support for solo5
  • about 2 years trying to enable tracing for solo5 targets gets xen tracing stuff
  • about 2 years Allow disabling of warnings in config.ml
  • about 2 years error while configuring mirage-www
  • about 2 years startup errors, once again
  • over 2 years mirage.io gives a very bad first impression as a self hosted mirage app
  • over 2 years `mirage configure -t xen` attempts to install mirage-clock-unix