Closed mmelyp closed 3 days ago
I'm closing this issue. It is now working after removing
started = true
machine = "q35"
scsi_hardware = "virtio-scsi-single"
bios = "ovmf"
efi_disk {
datastore_id = "local-lvm"
file_format = "raw"
type = "4m"
}
and adding:
serial_device {
device = "socket"
}
don't really know what's happened there 🤷🏼♂️
Hi everyone,
I have a problem which has been bothering me for a few days and I really don't know how to solve it.
I'm using since some time ago this terraform plugin and i was able to create successfully new debian 12 genericcloud based VMs (cloud-init).
Since some days ago, i get a "Kernel panic - not syncing: Attempted to kill init!" after disk is resized and the VM is started. When i apply the terraform manifest, this is what in proxmox side is happening:
UPID:tango:0003C2AF:00828CC1:6738AA72:download:debian-12-generic-amd64-latest.img:root@pam!terraform: 6738AA7F OK UPID:tango:0003C2FF:00829204:6738AA7F:qmcreate:100:root@pam!terraform: 6738AA80 OK UPID:tango:0003C3A3:008296D0:6738AA8B:resize:100:root@pam!terraform: 6738AA8C OK UPID:tango:0003C3C2:00829778:6738AA8D:qmstart:100:root@pam!terraform: 6738AA8E OK
This used to work without problems.
This is my terraform file:
If i enable:
then i do not get the kernel panic, but cloud-init somehow is not applied.
Here is how the cloud image and cloud-config file generation looks like:
and the cloud-init config template ("${path.module}/cloud-init/base-debian-k8s.yaml.tftpl):
I have a the feeling the problem of the kernel panic, is because for some reason cloud-init is not able to be applied and cannot grow/resize the vm disk.
What strange is the VM knows about the cloud-init config
and a dump of cloud-init:
After restarting manually the VM, then it boots ok and no kernel panic is shown, but i cannot see the hostname, user or any other cloud-init definition being applied:
My environment is:
Terraform: 1.9.8 bpg/proxmox: 0.66.3 Proxmox: 8.2.8
As i said, this used to work some time ago. Any idea?
Thanks in advance ;)