/etc/machine-id is identical #6

New issue

Open

opened 2026-02-24 16:48:04 +01:00 by lilly · 0 comments

lilly commented 2026-02-24 16:48:04 +01:00

Owner

Copy link

Currently, when instantiating the template multiple times, /etc/machine-id is being duplicated across VMs. This results in both VMs having the same DHCP client identifier and thus broken IPv4 connectivity if both VMs are running simultanously.

Broad ideas to fix this:

• Change this script to directly create a VM instead of a template. I assume that by creating a new VM from scratch, a new machine-id is hopefully generated.
• Figure out how to enable systemds firstboot.service which (but only once) in the template which should generate a new machine-id when the template is instantiated and first started.

Currently, when instantiating the template multiple times, `/etc/machine-id` is being duplicated across VMs. This results in both VMs having the same DHCP client identifier and thus broken IPv4 connectivity if both VMs are running simultanously. Broad ideas to fix this: - Change this script to directly create a VM instead of a template. I assume that by creating a new VM from scratch, a new machine-id is hopefully generated. - Figure out how to enable [systemds firstboot.service](https://man.archlinux.org/man/systemd-firstboot.1.en) which (but only once) in the template which should generate a new machine-id when the template is instantiated and first started.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

No results found.

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

CCCHH/pve-template-vm#6

No description provided.