yes the problem is that KVM is not running. also with your specification it does not work…
I must investigate on the KVM installation on the host machine. thanks a lot > Il giorno 18 apr 2019, alle ore 05:51, Waldek Kozaczuk <[email protected]> > ha scritto: > > Definitely you are NOT using KVM acceleration - you should see "-enable-kvm" > in the cmdline. > > Could you please check that you have KVM module installed and setup for your > user like so: > > usermod -aG kvm <user name> > > Also make sure you have this line: > > disable_kvm: false > > in ~/.capstan/config.yaml. > > I do not remember if capstan enables KVM by default if detected or if you > have to specify it explicitly. This - > https://github.com/cloudius-systems/capstan/blob/efad2dff6ddeded449aa3954bcaefba554a36209/Documentation/Installation.md > > <https://github.com/cloudius-systems/capstan/blob/efad2dff6ddeded449aa3954bcaefba554a36209/Documentation/Installation.md> > - says that it is enabled by default but probably only of KVM is setup. > > Waldek > > > On Wednesday, April 17, 2019 at 12:35:32 AM UTC-4, robertob wrote: > I'm using Linux Fedora (Linux version 5.0.7-200.fc29.x86_64): > > qemu-system-x86_64: QEMU emulator version 3.0.0 (qemu-3.0.0-4.fc29) > > When I run the image through "capstan run" this is the qemu cmdline executed: > > /usr/bin/qemu-system-x86_64 -nographic -m 1500 -smp 4 -device > virtio-blk-pci,id=blk0,bootindex=0,drive=hd0 -drive > file=/home/robbat/.capstan/instances/qemu/unikure/disk.qcow2,if=none,id=hd0,aio=threads,cache=none > -chardev stdio,mux=on,id=stdio,signal=off -device isa-serial,chardev=stdio > -netdev bridge,id=hn0,br=virbr0,helper=/usr/libexec/qemu-bridge-helper > -device virtio-net-pci,netdev=hn0,id=nic1,mac=6e:48:b2:0e:48:08 -chardev > socket,id=charmonitor,path=/home/robbat/.capstan/instances/qemu/unikure/osv.monitor,server,nowait > -mon chardev=charmonitor,id=monitor,mode=control > > I do not know how to set accelerator in QEMU. > > thanks > > roberto > > Il giorno martedì 16 aprile 2019 16:52:58 UTC+2, Waldek Kozaczuk ha scritto: > The convert output should go under $HOME/.capstan subdirectory with the > extension .vbox like so: > > ``` > qemu-img convert -O vdi ~/.capstan/repository/app/app.qemu > ~/.capstan/repository/app/app.vbox > ``` > > If you are using Mac then qemu-img has a bug > (https://bugs.launchpad.net/qemu/+bug/1776920 > <https://bugs.launchpad.net/qemu/+bug/1776920>) so you have to use a > workaround (see https://bugs.launchpad.net/qemu/+bug/1776920/comments/14 > <https://bugs.launchpad.net/qemu/+bug/1776920/comments/14>). > > Can you tell us which development platform are you using to play with OSv? > Laptop with: > - Linux > - OSX (MacBook) > - Windows > on it? > > What version of QEMU? What version of VirtualBox? > > Depending on it I might give you better advice on which accelerator (KVM, > Intel HAXM, etc) to use with QEMU. > > Waldek > > On Tuesday, April 16, 2019 at 2:06:26 AM UTC-4, Pekka Enberg wrote: > Hi, > > I don't think Capstan supports building VirtualBox images, but you can use > the "qemu-img convert -O vdi" command to convert a QCOW2 (QEMU's format) > image to a VirtualBox image. > > - Pekka > > On Tue, Apr 16, 2019 at 9:03 AM Roberto Battistoni <[email protected] <>> > wrote: > Hi guys! > > Any advice? Please I am very close to conclude my experimentations but QEMU > is too slow and I need to do other tests with more efficient platform. > > thanks so much > > r > >> Il giorno 14 apr 2019, alle ore 08:13, robertob <[email protected] <>> ha >> scritto: >> >> I made package.yaml that correctly run with default QEMU platform, but now I >> do not understand how to build image for virtualbox platform. When I build >> the image (capstan package compose uni) I see every time that the QEMU image >> was created. >> >> I tried this package.yaml file with "platform: vbox" but noting.... >> >> name: uni >> title: Uni >> platform: vbox >> >> require: >> - openjdk8-zulu-compact3-with-java-beans >> - osv.httpserver-html5-gui-and-cli >> - osv.run-java >> - osv.cli >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "OSv Development" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/osv-dev/-fwSG-MY9Ks/unsubscribe >> <https://groups.google.com/d/topic/osv-dev/-fwSG-MY9Ks/unsubscribe>. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "OSv Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "OSv Development" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/osv-dev/-fwSG-MY9Ks/unsubscribe > <https://groups.google.com/d/topic/osv-dev/-fwSG-MY9Ks/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
