Hi Martin, Thanks for your answer.
On Fri, Oct 16, 2020 at 2:15 PM Martin Lucina <mar...@lucina.net> wrote: > Hi Hans, > > On Sunday, 11.10.2020 at 19:55, Hans Ole Rafaelsen wrote: > > Hi, > > > > I'm trying to run some of the tutorial examples on OpenStack. This is a > > "Nokia AirFrame Cloud Infrastructure" with "OpenStack Compute version > > 17.0.7-1" > > Any idea what QEMU version that uses internally? > I have asked the provider. I'll let you know if I get a reply. > > > > I have built a virtio target and created a qcow2 image. > > > > When running this on OpenStack it seems to start the Solo5 execution > > environment, but the MirageOS application does not seem to start. The log > > only show: > > Which example, specifically? > First the network example, and later the "hello world" example, taken from https://github.com/mirage/mirage-skeleton > > SYSLINUX 6.03 20171017 Copyright (C) 1994-2014 H. Peter Anvin et al > > Loading unikernel.bin... ok > > | ___| > > __| _ \ | _ \ __ \ > > \__ \ ( | | ( | ) | > > ____/\___/ _|\___/____/ > > Solo5: Bindings version v0.6.6 > > Solo5: Memory map: 1024 MB addressable: > > Solo5: reserved @ (0x0 - 0xfffff) > > Solo5: text @ (0x100000 - 0x47dfff) > > Solo5: rodata @ (0x47e000 - 0x519fff) > > Solo5: data @ (0x51a000 - 0x74afff) > > Solo5: heap >= 0x74b000 < stack < 0x40000000 > > 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:a6:51:b7, features=0x48bf81a6 > > Solo5: PCI:00:04: virtio-block device, base=0xc000, irq=11 > > Solo5: PCI:00:04: configured, capacity=125829120 sectors, > features=0x79000e54 > > > > Not sure if it is a problem with getting the log output from the > > application or if it is not starting at all. The cloud infrastructure > says > > the VM is active, but it does not show the actual resource usage of the > VM, > > so it is hard to say what is going on. > > For network applications it does not respond to ping, so it seems like it > > is not running. > > Try adding "--logs=*:debug" to the kernel command line. > I tried adding it during the "mirage configure" step. On the local qemu VM I get additional debugging info, but on the OpenStack cloud I get the same result. No logs from the application itself. > > > > > The qcow2 image runs fine on a local (Ubuntu 18.04 host) qemu/kvm VM and > I > > have no problem running other qcow2 images (Ubuntu) on the OpenStack > cloud. > > > > Is there some limitation on the images created with mirage/solo5 that > > prevents them from running on the OpenStack platform? > > I suspect no one's tried on OpenStack. Also, be aware that the virtio > target is somewhat limited; all the exciting stuff is going on in the other > Solo5-based targets. > > I tried another post about that on the mailing list, but it seems like it has got stuck. (This post took 2 days before showing up on the list.) Is there some way to make a hvt target to run on qemu/kvm? -- Hans Ole -mato > > > > > Any tips on how to investigate this problem? > > > > Regards, > > > > Hans Ole Rafaelsen >
