Bug#868679: Re: Bug#868679: cloud.debian.org: Multiple identical vagrant boxes appear as the same machine to libvirt's dnsmasq dhcp provider
Having had a look: when I *remove* /var/lib/dbus/machine-id and leave
a 0-byte file in /etc/machine-id, the boot sequence completes and
generates a new machine-id.
I'm able to bring up multiple "identical" VMs at that point; dnsmasq
reports them all having different client IDs.
On Tue, Jul 18, 2017 at 10:58 PM, jan <email@example.com> wrote:
> Will run through this tomorrow to confirm, cheers.
> Excuse typos. Phone screens don't make great ketbroads.
> -------- Original message --------
> From: Emmanuel Kasper <firstname.lastname@example.org>
> Date: 18/07/2017 5:14 p.m. (GMT+00:00)
> To: Jan Grant <email@example.com>, firstname.lastname@example.org,
> Subject: Re: Bug#868679: cloud.debian.org: Multiple identical vagrant boxes
> appear as the same machine to libvirt's dnsmasq dhcp provider
> On 07/17/2017 05:16 PM, Jan Grant wrote:
>> The box image should not include those files (it suffices to delete them
>> to packaging the image). This causes each instance to mint its own new
>> UUID, which in turn results in distinct client-ids being supplied by
> It does not seem to me that deleting /etc/machine-id and
> /var/lib/dbus/machine-id is enough to have each instance generating this
> on boot, you have to call dbus-uuidgen --ensure manually.
> Can you double check this ?