[SOLVED] CentOS Cloud Init - doesn’t work

[KAMALA]

Hello,
Everyone I am trying some automation with cloud init Images it works fine with Ubuntu and Debian.

However I could not managed to make it work for centos.

Could you please advise me on that or if you have any image already tested and worked would be nice to share it.

Thanks
Kamala

 

[bbgeek17]

Hi @KAMALA ,
Perhaps you could add more details, someone can advise you. For example:
What image/s you tried to use?
What type of cloudinit did you try?
What was the VM config?
What did not work?
What troubleshooting did you try?

Standard Cloud images (are they still available?) work just fine with both PVE built-in cloudinit and custom one.

Best

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[KAMALA]

Hi @KAMALA ,
Perhaps you could add more details, someone can advise you. For example:
What image/s you tried to use?
What type of cloudinit did you try?
What was the VM config?
What did not work?
What troubleshooting did you try?

Standard Cloud images (are they still available?) work just fine with both PVE built-in cloudinit and custom one.

Best

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @bbgeek17 ,

Here are VMs configs:
qm create 9000 --memory 2048 --core 2 --name CentOS-Cloud --net0 virtio,bridge=vmbr0
qm disk import 9000 CentOS.qcow2 HDD_Pool
qm set 9000 --scsihw virtio-scsi-pci --scsi0 HDD_Pool:vm-9000-disk-0
qm set 9000 --ide2 HDD_Pool:cloudinit
qm set 9000 --boot c --bootdisk scsi0
qm set 9000 --serial0 socket --vga serial0
qm template 9000

Teamplate creation went well with this Image that i used "CentOS-Stream-GenericCloud-x86_64-9-20241021.0.x86_64.qcow2"

- VM creation was successfull too

qm clone 9000 1003 --name CentOS01--full

- VM started




By default I keept IP config on DHCP



as you can see everything went well but I am not able to access or connect to the VM!


All the the comments are wellcomed as I said same steps worked for Ubuntu and Debian.

 

[bbgeek17]

I suspect you are missing the the boot trace.
Stop your VM, then run: qm start 901 && qm terminal 901

For me this image crashes with Kernel panic, which has nothing to do with cloudinit

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[KAMALA]

I suspect you are missing the the boot trace.
Stop your VM, then run: qm start 901 && qm terminal 901

For me this image crashes with Kernel panic, which has nothing to do with cloudinit

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

This is what I get from:

2J[ 0.000000] Linux version 5.14.0-522.el9.x86_64 (mockbuild@x86-05.stream.rdu2.redhat.com) (gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2), GNU ld version 2.35.2-54.el9) #1 SMP PREEMPT_DYNAMIC Sun Oct 20 13:04:34 UTC 2024

[ 0.000000] The list of certified hardware and cloud instances for Red Hat Enterprise Linux 9 can be viewed at the Red Hat Ecosystem Catalog, https://catalog.redhat.com.

[ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.14.0-522.el9.x86_64 root=UUID=74c8a951-d254-4f9e-a83f-116a727217a6 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M

 

[KAMALA]

I suspect you are missing the the boot trace.
Stop your VM, then run: qm start 901 && qm terminal 901

For me this image crashes with Kernel panic, which has nothing to do with cloudinit

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

[ 2.046205] Kernel Offset: 0x10e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

[ 2.047218] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]---

 

[bbgeek17]

First, please use either CODE <> tags, or, for this amount of text, SPOILER option (under street light dots (3 dots) on the right side).

Second, there was no need to post the entirety of the log:

[ 2.047218] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]---

As mentioned earlier, the image/OS crashes with Kernel panic. There may be many reasons for that.
Its a "bleeding edge" release and could be broken, it may be in some way incompatible with Qemu9, it may not be liking particular CPU architecture, etc.
You are welcome to troubleshoot it more. If you do: try older image, try Rocky and/or Alma, wait a week and try next release, try to change CPU, reduce/increase memory, reduce/increase cores, change hardware, etc.

It's unlikely to be directly related to the topic of this forum, which is: "Proxmox VE: Installation and configuration"

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[BobhWasatch]

Fatal glibc error: CPU does not support x86-64-v[ 0.959953] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

This seems to be saying the image was built to use some x86 instruction set extensions that aren't enabled. If you are using the default "kvm64" CPU settings that might be the problem. Have you tried using "host" instead? If so, what CPU does the host have?

 

[KAMALA]

Fatal glibc error: CPU does not support x86-64-v[ 0.959953] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

This seems to be saying the image was built to use some x86 instruction set extensions that aren't enabled. If you are using the default "kvm64" CPU settings that might be the problem. Have you tried using "host" instead? If so, what CPU does the host have?

what do you mean by? "Have you tried using "host" instead?"

This my CPU:
lscpu | grep "Model name:"
Model name: AMD Ryzen Threadripper 1920X 12-Core Processor

 

[bbgeek17]

what do you mean by? "Have you tried using "host" instead?"

https://pve.proxmox.com/wiki/Qemu/K...cific host cores.-,CPU Type,-QEMU can emulate

https://qemu-project.gitlab.io/qemu...#:~:text=-,Host passthrough,-This passes the

qm set 100 --cpu host

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[KAMALA]

@bbgeek17 and @BobhWasatch that worked like a charm, thank you so much for your help!
can't we configur the pve to have both seted, and then VMs will use the option that is support ?

I am going through the links you have shared with me

Thanks