Search results

It really does not matter as they are pointing to the exact same devices. Example from a 2-disk NVMe system: $ ls -l /dev/disk/by-id/nvme* /dev/disk/by-id/nvme-KINGSTON_SA2000M8250G_50026B7683B8E848 -> ../../nvme0n1 /dev/disk/by-id/nvme-KINGSTON_SA2000M8250G_50026B7683B8E848-part1 ->...

If I understand you correctly, there might be a fundamental misunderstanding: The entire structure below /dev/disk/by-* consists of only symlinks to physical devices, which are dynamically generated by udev based on hardware data (i.e. mostly for convencience). For any sgdisk -R command (to...

To expand on @Aubs guidance: I have successfully been using the Debian 12 Bookworm cloud-variant images from https://jenkins.linuxcontainers.org/job/image-debian/ on Proxmox 8.2. At first, I had no network connectivity but during (or after) container creation, if you rename the ethernet...

For future reference, Benoît's guide still works with PVE 8.1. One minor addition as I experienced this myself: 6a. If existing, move the relevant firewall config file too: mv /etc/pve/firewall/100.fw /etc/pve/firewall/101.fw Regards

I think I ran into a related issue with my two NVMe drives back with the 6.1 opt-in kernel, see my post here. You could try and compare the device links in /dev/disk/by-id/ (i.e. not only in /dev/ !) between 5.15 and 6.2, because at least for me they have changed since 5.19 (i.e. due to the bug...

Following up on this, as I have not seen any replies: I did some testing and noticed that pve-kernel-6.1 does not expose an EUI identifier for one of my NVMe devices, and therefore its WWID changes too (which is supposed to be unique and stable?) compared to default pve-kernel-5.15 (which shows...

Switched to pve-kernel-6.1 yesterday, from 5.15. Apparently, something in 6.1 messes with the device IDs of one single storage device: After restart, I noticed a delay in booting the system, so I looked at the console and noticed a "A start job is running for dev-disk-by-id...

You are right, this may be a false expectation from my side. Would be nice though to either use existing functionality for this use case too, or being able to hook into the cloning process. Regards

Hi, I noticed a disturbing/surprising behavior of Proxmox when creating linked/full clones from container templates: SSH host keys are not regenerated during cloning process. Isn't this something fundamental that would make sense as functionality? Maybe I missed something. I verified both with...

Hi, I am building a new Proxmox 6.2 server right now using Open vSwitch-based network configuration. I came up with a (from ovs-perspective) perfectly fine working configuration that is however not accepted by Proxmox, apparently due to naming: # Loopback interface auto lo iface lo inet...

Thanks, wolfgang! Good to know, yet having "the same" approach in both worlds (i.e. cloud-init user data) would've been nice. ;) Regards

Hi, I had great success with using cloud-init enabled images (specifically Ubuntu minimal cloud images) for virtual machines and custom user data (cicustom and own YAML) to tailor my deployments, using the Wiki guide. However, how is it possible to use the cloud-init approach for Proxmox...