VM image might have a trail of instance specific configuration from previous runs. In case of network, these historic settings might lead to preserving old MAC address on the NICs, which are supposed to have different MAC (the one proposed by the OpenNebula). The inconsistency between OpenNebula proposed MAC (IP), and MAC enforced by the Windows from past runs can lead to malfunction of network contextualization. Context scripts don't find a NIC with ONE proposed MAC address, so scripts won't be able to configure that NIC with requested IP.
In general, it's recommended to use sysprep tool to generalize Windows golden images. In some cases, user can't do that, but fortunately some recent Windows releases come with a tool netcfg -d, which can drop all network settings.
The idea is to
document this tool on places we mention the sysprep
consider calling network cleanup within context scripts (it's hard to say when, ideally it should be always on boot, but such cleanup requires extra reboot... so we might do that e.g., only when no NICs are found)
VM image might have a trail of instance specific configuration from previous runs. In case of network, these historic settings might lead to preserving old MAC address on the NICs, which are supposed to have different MAC (the one proposed by the OpenNebula). The inconsistency between OpenNebula proposed MAC (IP), and MAC enforced by the Windows from past runs can lead to malfunction of network contextualization. Context scripts don't find a NIC with ONE proposed MAC address, so scripts won't be able to configure that NIC with requested IP.
In general, it's recommended to use
syspreptool to generalize Windows golden images. In some cases, user can't do that, but fortunately some recent Windows releases come with a toolnetcfg -d, which can drop all network settings.The idea is to
https://opennebula.zendesk.com/agent/tickets/13365