Our old version of ONE was 5.4.13 and there we selected a kernel image via sunstone. It appeared as “-kernel /var/lib/one//datastores/0/2380903/kernel” in command line arguments to qemu-system-x86_64. When looking at the template generated, it has both KERNEL and KERNEL_DS set:
OS = [
KERNEL = “/var/lib/one//datastores/0/2392078/kernel”,
KERNEL_DS = “$FILE[IMAGE_ID=0]”,
With 5.8.1 any selection of kernel files has no affect on the launch command, and thus is ignored.
Also looking at the template which is generated, it lacks the KERNEL parameter all together. It only has KERNEL_DS, like this:
OS = [
ARCH = “x86_64”,
BOOT = “”,
KERNEL_DS = “$FILE[IMAGE_ID=0]”,
How do I get the kernel image to be along in the qemu launch command?
**Versions of the related components and OS (frontend, hypervisors, VMs):
OpenNebula 5.8.1
Steps to reproduce:
Generate image that tries starting up with a custom kernel image.
Current results:
The KERNEL_SD value from sunstone gets ignored.
Expected results:
It’s applied to the qemu launch command
I’m trying to instantiate an image created from a dockerfile script and, after downloading a “kernel” from Apps (MarketPlace), when VM boots, I only see “Booting from ROM”, but no more…
IMAGE 236 INFORMATION
ID : 236
NAME : Fall3D
USER : oneadmin
GROUP : oneadmin
LOCK : None
DATASTORE : default
TYPE : OS
REGISTER TIME : 02/21 15:05:17
PERSISTENT : No
SOURCE : /var/lib/one//datastores/1/caf417cf6f11389812024c9a017ec3dc
PATH : dockerfile://?fileb64=RlJPTSB1YnVudHUKCkVOViBERUJJQU5fRlJPTlRFTkQ9bm9uaW50ZXJhY3RpdmUKUlVOIGFwdC1nZXQgdXBkYXRlClJVTiBhcHQtZ2V0IGluc3RhbGwgLXkgYnVpbGQtZXNzZW50aWFsClJVTiBhcHQtZ2V0IGluc3RhbGwgLXkgZ2ZvcnRyYW4KUlVOIGFwdC1nZXQgaW5zdGFsbCAteSBnaXQKUlVOIGFwdC1nZXQgaW5zdGFsbCAteSBsaWJuZXRjZGYtZGV2IGxpYm5ldGNkZmYtZGV2ClJVTiBhcHQtZ2V0IGluc3RhbGwgLXkgb3Blbm1waS1iaW4gbGlib3Blbm1waS1kZXYKUlVOIGFwdC1nZXQgaW5zdGFsbCAteSBuY28KUlVOIGFwdC1nZXQgaW5zdGFsbCAteSB4dmZiIApSVU4gYXB0LWdldCBpbnN0YWxsIC15IHdraHRtbHRvcGRmCgpSVU4gYXB0LWdldCBpbnN0YWxsIC15IGJ1aWxkLWVzc2VudGlhbCBsaWJhZWMtZGV2IHpsaWIxZy1kZXYgbGliY3VybDQtb3BlbnNzbC1kZXYgbGliYm9vc3QtZGV2IGN1cmwgd2dldCB6aXAgdW56aXAgYnppcDIgZ2ZvcnRyYW4gZ2NjIGcrKwpSVU4gcm0gLXJmIC91c3IvbG9jYWwvZ3JpYjIvClJVTiBta2RpciAtcCAvdXNyL2xvY2FsL2dyaWIyLwpSVU4gd2dldCBmdHA6Ly9mdHAuY3BjLm5jZXAubm9hYS5nb3Yvd2Q1MXdlL3dncmliMi93Z3JpYjIudGd6LnYyLjAuNmMKUlVOIG12IHdncmliMi50Z3oudjIuMC42YyAvdG1wL3dncmliMi50Z3oKUlVOIHRhciAteGYgL3RtcC93Z3JpYjIudGd6ClJVTiBtdiBncmliMi8gL3Vzci9sb2NhbC9ncmliMi8KV09SS0RJUiAvdXNyL2xvY2FsL2dyaWIyL2dyaWIyCkVOViBGQz1nZm9ydHJhbgpFTlYgQ0M9Z2NjClJVTiBtYWtlICYmIHJtIC1yZiAvdXNyL2xvY2FsL2Jpbi93Z3JpYjIKUlVOIGxuIC1zIC91c3IvbG9jYWwvZ3JpYjIvZ3JpYjIvd2dyaWIyL3dncmliMiAvdXNyL2xvY2FsL2Jpbi93Z3JpYjIKUlVOIHJtIC90bXAvd2dyaWIyLnRnegoKV09SS0RJUiAvClJVTiBnaXQgY2xvbmUgaHR0cHM6Ly9naXRsYWIuY29tL2ZhbGwzZC1kaXN0cmlidXRpb24vdjguMCBmYWxsM2QKV09SS0RJUiAvZmFsbDNkClJVTiB0YXIgLXh2ZiBmYWxsM2QtOC4wLjEudGFyLmd6CldPUktESVIgL2ZhbGwzZC9mYWxsM2QtOC4wLjEKUlVOIC4vY29uZmlndXJlClJVTiBtYWtlCgpSVU4gYXB0LWdldCBpbnN0YWxsIC15IHB5dGhvbjMgcHl0aG9uMy1waXAKCldPUktESVIgLwpSVU4gbWtkaXIgL291dHB1dHMKUlVOIG1rZGlyIC9iaW5hcmllcwpSVU4gY3AgL3Vzci9sb2NhbC9ncmliMi9ncmliMi93Z3JpYjIvd2dyaWIyIC9iaW5hcmllcwpSVU4gY3AgL3Vzci9iaW4vbmNhdHRlZCAvYmluYXJpZXMvClJVTiBjcCAvdXNyL2Jpbi9uY3JlbmFtZSAvYmluYXJpZXMKUlVOIGNwIC9mYWxsM2QvZmFsbDNkLTguMC4xL1NvdXJjZXMvRmFsbDNkLnI4LnggL2JpbmFyaWVz&context=yes&size=10240
FORMAT : qcow2
SIZE : 10G
STATE : used
RUNNING_VMS : 1
PERMISSIONS
OWNER : um-
GROUP : ---
OTHER : ---
IMAGE TEMPLATE
DEV_PREFIX="sd"
VIRTUAL MACHINES
ID USER GROUP NAME STAT CPU MEM HOST TIME
9073 oneadmin oneadmin Fall3D-9073 unkn 2 2G localhost 0d 00h03
And kernel image:
IMAGE 238 INFORMATION
ID : 238
NAME : Kernel 5.4 x86_64 - KVM
USER : oneadmin
GROUP : oneadmin
LOCK : None
DATASTORE : files
TYPE : KERNEL
REGISTER TIME : 02/22 15:23:54
PERSISTENT : No
SOURCE : /var/lib/one//datastores/2/6cc26eddeb034dd711ab17078d4c1075
PATH : https://marketplace.opennebula.io/appliance/8e41b18a-3d62-4342-a26f-20629999b56a/download/0
FORMAT : raw
SIZE : 55M
STATE : rdy
RUNNING_VMS : 0
PERMISSIONS
OWNER : um-
GROUP : ---
OTHER : ---
IMAGE TEMPLATE
FROM_APP="179"
FROM_APP_MD5="ed6ac036eed7ee44ec0664585166ce17"
FROM_APP_NAME="Kernel 5.4 x86_64 - KVM"
VIRTUAL MACHINES
Actually from our experience deploying container images with KVM, is not an easy tasks as it strongly depends on the kernel and image dependencies, also there are some requirements from the host where the VMs are deployed: Using Container Images — OpenNebula 6.2.1 documentation.
The suggested way of using these images is either by using Firecracker or LXC drivers, instead of KVM.