Comment 29 for bug 145382

I realized after my previous message that this bug relates to Gutsy in general, and not just the JeOS version..

My comment was specific to the JeOS build, which operates in a fundamentally different environment as a Virtual Machine, which leads to issues with the virtual NIC devices being a lot more dynamic than physical NIC devices.

For example, if a VM is cloned, moved to another host, or even has some seemingly unrelated change made to its configuration, the MAC address of the VM can change - causing loss of connectivity for the VM on the next reboot, in a way that is non-trivial to diagnose.

The scenarios described above are from my experience with VMware ESX, and may not come into play with Xen, KVM, MS Viridian, or others.