Martin and Ricardo, Thanks for the fix!
It works fine on the OpenStack platform. $ opam list --all | grep solo5-bindings-virtio solo5-bindings-virtio 0.6.7 pinned to version 0.6.7 at git+https://github.com/solo5/solo5.git SYSLINUX 6.03 20171017 Copyright (C) 1994-2014 H. Peter Anvin et al Loading unikernel.bin... ok | ___| __| _ \ | _ \ __ \ \__ \ ( | | ( | ) | ____/\___/ _|\___/____/ Solo5: Bindings version v0.6.8-4-g0eb8cb8 Solo5: Memory map: 1023 MB addressable: Solo5: reserved @ (0x0 - 0xfffff) Solo5: text @ (0x100000 - 0x48ffff) Solo5: rodata @ (0x490000 - 0x52efff) Solo5: data @ (0x52f000 - 0x7b7fff) Solo5: heap >= 0x7b8000 < stack < 0x3ffdc000 Solo5: Clock source: KVM paravirtualized clock Solo5: PCI:00:03: virtio-net device, base=0xc060, irq=11 Solo5: PCI:00:03: configured, mac=fa:16:3e:cc:88:0f, features=0x48bf81a6 Solo5: PCI:00:04: virtio-block device, base=0xc000, irq=11 Solo5: PCI:00:04: configured, capacity=2097152 sectors, features=0x79000e54 Solo5: PCI:00:05: unknown virtio device (0x5) Solo5: Application acquired 'service' as network device 2020-12-23 07:53:55 -00:00: INF [netif] Plugging into service with mac fa:16:3e:cc:88:0f mtu 1500 2020-12-23 07:53:55 -00:00: INF [ethernet] Connected Ethernet interface fa:16:3e:cc:88:0f 2020-12-23 07:53:55 -00:00: INF [dhcp_client_lwt] Lease obtained! IP: 10.3.91.3, routers: 10.3.91.1 2020-12-23 07:53:55 -00:00: INF [ARP] Sending gratuitous ARP for 10.3.91.3 (fa:16:3e:cc:88:0f) 2020-12-23 07:53:55 -00:00: INF [udp] UDP interface connected on 10.3.91.3 2020-12-23 07:53:55 -00:00: INF [tcpip-stack-direct] stack assembled: mac=fa:16:3e:cc:88:0f,ip=10.3.91.3 Regards, Hans Ole On Tue, Dec 22, 2020 at 5:40 PM Martin Lucina <mar...@lucina.net> wrote: > Hans, > > On Thursday, 05.11.2020 at 16:05, Martin Lucina wrote: > > thanks for investigating! I've created an issue to track this, though I > > don't expect to have time to look into it soon: > > > > https://github.com/Solo5/solo5/issues/483 > > > > Hans, you might want to subscribe to that, I don't know your Github ID. > > Thanks to Ricardo, we now have a proper fix for this on master. If you have > time, would you mind confirming that it also works on your OpenStack > platform? > > > In the mean time, you can work with Ricardo's patch; if you want to get > > that working with a MirageOS application, then do something like > (assuming > > OPAM already set up): > > > > 1. git clone https://github.com/Solo5/solo5.git > > 2. apply Ricardo's workaround to solo5/ > > 3. opam pin add -k path solo5-bindings-virtio solo5/ > > 4. proceed as normal with building a Mirage application. > > To work with master, replace (3) above with > > opam pin add --dev-repo solo5-bindings-virtio > > Cheers, > > Martin >
