|
2015-12-17
| ||
| 19:07 | • Closed ticket [0a4116f6ab]: MAC assignment problem plus 3 other changes artifact: 43b71b9c63 user: vitus | |
| 15:11 | • Ticket [0a4116f6ab]: 5 changes artifact: 6ab4fddc86 user: vitus | |
|
2015-11-11
| ||
| 07:34 | • New ticket [0a4116f6ab]. artifact: 5dffea9ac4 user: vitus | |
| Ticket Hash: | 0a4116f6ab41f446121012b8b0f0022f941b294d | |||
| Title: | MAC assignment problem | |||
| Status: | Closed | Type: | Feature_Request | |
| Severity: | Important | Priority: | Immediate | |
| Subsystem: | Resolution: | Fixed | ||
| Last Modified: | 2015-12-17 19:07:47 | |||
| Version Found In: | 0.2 | |||
| User Comments: | ||||
vitus added on 2015-11-11 07:34:11:
Now we put MAC address into start script of the machine. It is important, because it allows machine to receive same address via DHCP, and also can affect internal working of operating system (i.e. linux guests can change name of network interface if mac changes). But if we move virtual machine from one host no another, mac conflict can happen. So, we need MAC assigning algorithm, which minimize probability of the conflict, and method of conflict resolution on the first start of the machine on new host. vitus added on 2015-12-17 15:11:43: Fixed in 0.2 by generating 5 of 6 octets randomly | ||||