Recent content by J. Augusto de Oliveira

I am not using the official one yet, I created my own template.

Good news to have official support in PVE for rocky. Rocky has worked very well for me.

This has been working for me, but I am puzzled why it does. Why the second line mapping on the host is: root:100000:65536 root:1284000000:200000 And not: root:100000:65536 1284000000:1284000000:200000 Similar to the mapping inside the container.

I will need to investigate Alma vs Rocky. I just downloaded the Rocky image from linux containers. The reason I want from PVE is to save time changing my CI workflow.

I also would like an ETA on this ... I got to get rid of some Centos8 LXC's.

I did read the thread. Like Piers Dawson-Damer mentioned, 6.0-9 and 6.0-13 did not work. I will keep version 6.0-5 until this bug is corrected.

Had to downgrade qemu-server to 6.0-5. This is the workaround for now that works for me.

a recent update of PVE and qemu broke this cloud-init. I get no bootable hard disk.

installed kernel 5.3.7-1-pve and it did not fix this issue.

I have this issue, and not convenient is a understatement. It broke my ansible-based creation and provisioning of VMs. Downgrading to qemu-server-6.0.9 did not work for me. Also upgrading the kernek to 5.3.7-1 did not work. Where is this issue being tracked. Any workarounds?

Hi, I am new to PVE but trying to learn fast. Would it be possible to directly connect the two servers with 10GbE, so each server had 1 (in the real world it would have 2) connections to the 'main' network, but 1 network card with an ethernet cable that connected directly to the second server...