Cloning VMs: sheep and tricks
summary
Cloning VMs copies everything including identifiers, so multiple clones end up sending identical DHCP client IDs and colliding for the same IP, causing broken or flaky networking. Dolly was the only successful sheep from 277 attempts, illustrating why identical copies matter. Use libvirt/virt-clone (cloning tools already rewrite MACs) plus explicitly regenerate the systemd machine-id or run virt-sysprep to remove/change DHCP client IDs and hostnames, then reboot; following that procedure lets clones run side-by-side reliably.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:35Dolly the Sheep
- 2:08Cloning Sheep vs Cloning VMs (II)
- 2:49One Environment, Many Clones
- 3:55Cloning VMS: MAC address
- 4:17Cloning VMs: IP address (static)
- 4:45Cloning VMs: IP address (dynamic)
- 6:31Cloning VMs: hostname
- 7:21Linux Host Identity: the machine-id
- 9:11Story of a VM Failure: The Plot
- 10:12Story of a VM Failure: The Circumstances
- 12:44Story of a VM Failure: The Outcome
- 13:401 Clone the VM
- 14:212 Do It Like a Sheep!
- 16:04CLONING VMS SUMMARY
- 16:54QUESTIONS?
related talks
41m#snapsafe: restoring uniqueness in Virtual Machine clones
37mVirter – How the "Docker for VMs" Can Help You Test the Linux Kernel
26mLessons Learned: Optimizing KVM Performance for EHR Systems
01h 01mDiskless Booting of RPi 400 Using Bootp, tftp, iscsi and NFS
39mKVM Modifications for Clustered Operation
28mTBC
53mXen: Open Source Hypervisor Designed for Clouds
01h 33mGetting Started with Kernel-based Virtual Machine (KVM)