search

kubernetes-sigs / cluster-api-provider-kubevirt

Cluster API Provider for KubeVirt
Apache License 2.0
110 stars 63 forks source link

KubevirtMachineTemplate VMs with our default ubuntu images have no console logs #197

Closed hh closed 1 year ago

hh commented 1 year ago

What steps did you take and what happened:

We used the ubuntu-2004 images generated from our-image-creation-process.md as in a KubeVirtMachineTemplate here

What did you expect to happen:

Be able to view the output via: virtctl console VM However no logs appear.

Anything else you would like to add:

It seems the default serial console tty is ttyS0, however at least our ubuntu images do not seem to be configured to log to console. I may be missing something, but by default ubuntu does no logging to console, and I do not see us doing anything an image-build time or vm-creation time to modify the necessary kernel argument for console=ttyS0

Environment:

/kind bug

qinqon commented 1 year ago

Latest Ubuntu image we use for kubevirtci at capk has console, they are build from https://github.com/kubernetes-sigs/image-builder/pull/984

Here is the change at capk https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/pull/186

hh commented 1 year ago

Not sure if my comment on the closed #186 would notify folks, so pulling into this open issue: https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/pull/186#issuecomment-1280072067

I can see the image was pushed here: https://quay.io/repository/capk/ubuntu-2004-container-disk?tab=tags&tag=latest

Are there other locations / type of images? Is there a documented release process for these images?

hh commented 1 year ago

Do we push qcow or other images?

qinqon commented 1 year ago

This is the docs capk has to build images:

Right now there is no automation to push image changes.

I have update the console activation PR so it does not depends on guest agent now, you can review it if you want: