| @arneme:matrix.org | It looks like that the new "Automated Virtual Installation" is the most mature one (given that it actually aims at setting up everything on the virtual machine in an automated fashion). I therefore tried to use it, but the vbox VM specification that is created will not start on my server for some reason. Not sure what the problem might be, and no help from vbox logs since they show no errors. Anyone had same problem? To be honest, I am not even sure if my vbox installation is actually working as it should (I installed it on my Debian 11 based server, but I have never used vbox before). Anyone else that has tried to install StarlingX using the "Automated Virtual Installation" on a Debian server as host? | 06:29 |
|---|---|---|
| @arneme:matrix.org | * It looks like that the new "Automated Virtual Installation" is the most mature one (given that it actually aims at setting up everything on the virtual machine in an automated fashion). I therefore tried to use it, but the vbox VM specification that is created will not start the VM on my server for some reason. Not sure what the problem might be, and no help from vbox logs since they show no errors. Anyone had same problem? To be honest, I am not even sure if my vbox installation is actually working as it should (I installed it on my Debian 11 based server, but I have never used vbox before). Anyone else that has tried to install StarlingX using the "Automated Virtual Installation" on a Debian server as host? | 06:30 |
| @arneme:matrix.org | * It looks like that the new "Automated Virtual Installation" is the most mature one (given that it actually aims at setting up everything on the virtual machine in an automated fashion). I therefore tried to use it, but the vbox VM specification that is created will not start the VM on my server for some reason. Not sure what the problem might be, and no help from vbox logs since they show no errors. Anyone had same problem? To be honest, I am not even sure if my vbox installation is actually working as it should (I installed it on my Debian 11 based server, but I have never used vbox before). Anyone else that has tried to install StarlingX using the "Automated Virtual Installation" on a Debian server as host (and succeeded)? | 06:30 |
| @arneme:matrix.org | * It looks like that the new "Automated Virtual Installation" is the most mature one (given that it actually not only configures and starts the virtual machine(s), but also aims at setting up everything on the virtual machine(s) in an automated fashion). I therefore tried to use it, but the vbox VM specification that is created will not start the VM on my server for some reason. Not sure what the problem might be, and no help from vbox logs since they show no errors. Anyone had same problem? To be honest, I am not even sure if my vbox installation is actually working as it should (I installed it on my Debian 11 based server, but I have never used vbox before). Anyone else that has tried to install StarlingX using the "Automated Virtual Installation" on a Debian server as host (and succeeded)? | 06:35 |
| @arneme:matrix.org | * It looks like that the new "Automated Virtual Installation" is the most mature one (given that it actually not only configures and starts the virtual machine(s), but also aims at setting up everything on the virtual machine(s) in an automated fashion). I therefore tried to use it, but the vbox VM specification that is created will not start the VM on my server for some reason. Not sure what the problem might be, and no help from vbox logs since they show no errors. Anyone had same problem? To be honest, I am not even sure if my vbox installation is actually working as it should (I installed it on my Debian 11 based server, but I have never used vbox before). Anyone else that has tried to install StarlingX using the "Automated Virtual Installation" on a Debian server as host (and succeeded)? Who created the "Automated Virtual Installation" setup? | 06:36 |
| @arneme:matrix.org | I do believe that I found the reason why the "Automated Virtual Installation" did not fully work. It appears that on Debian KVM/QEMU/libvirt is installed by default. Having to virtualisation systems on one server is apparently a bad idea since both KVM/QEMU/libvirt and virtualbox installs and uses kernel modules. After removing the KVM/QEMU/libvirt installation the "Automated Virtual Installation" at least managed to get past where it stopped and the VM for the controller is now running (although not completely installed yet). | 13:23 |
| @arneme:matrix.org | * I do believe that I found the reason why the "Automated Virtual Installation" did not fully work on Debian. It appears that on Debian KVM/QEMU/libvirt is installed by default. Having to virtualisation systems on one server is apparently a bad idea since both KVM/QEMU/libvirt and virtualbox installs and uses kernel modules. After removing the KVM/QEMU/libvirt installation the "Automated Virtual Installation" at least managed to get past where it stopped and the VM for the controller is now running (although not completely installed yet). | 13:23 |
| @arneme:matrix.org | * I do believe that I found the reason why the "Automated Virtual Installation" did not fully work on Debian. It appears that on Debian KVM/QEMU/libvirt is installed by default. Having two virtualisation systems on one server is apparently a bad idea since both KVM/QEMU/libvirt and virtualbox installs and uses kernel modules. After removing the KVM/QEMU/libvirt installation the "Automated Virtual Installation" at least managed to get past where it stopped and the VM for the controller is now running (although not completely installed yet). | 13:23 |
| @arneme:matrix.org | I can confirm that the install on Debian worked fairly well. In the logs I see some kube related errors and I am not able to access the Kubernetes dashboard after the install. I am however able to view the StarlingX Horizon GUI. | 19:36 |
| @arneme:matrix.org | * I can confirm that the install on Debian worked fairly well. In the logs I see some kube related errors and I am not able to access the Kubernetes dashboard after the install. I am however able to view the StarlingX Horizon GUI. brunomuniz , have you ben able to access Kubernetes Dashboard on your installations? | 19:37 |
| @arneme:matrix.org | * I can confirm that the install on Debian worked! I had to make one small change in the script, and to access the Kubernetes dashboard the documentation needs to be updated to state that https needs to be used in order to access the dashboard. | 20:17 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!