To the OP:
Obviously your incorrect use of terminology is causing confusion, here are some common definitions:
DHCP (automatically assigned addresses) - When a machine (virtual or physical) boots up on the network, it broadcasts its existence and a DHCP server responds by providing a unique network configuration the machine can use. You configure the client machine as a “DHCP client,” on openSUSE typically in YAST or Network Manager.
Static Address - When a machine (virtual or physical) boots up on the network, it is pre-configured with known network settings. On openSUSE this is more commonly configured using YAST, but can also be configured in Network Manager.
Reserved Lease - This is a hybrid of the above, when a machine (virtual or physical) boots up on the network, it broadcasts its existence and a DHCP server responds by first finding the machine’s MAC address in a list of reserved addresses mapped to specific IP addresses. In this way, the newly booted machine is always assigned the same IP address whereas a normal DHCP address could change.
Solutions to the above:**
First, you should understand that the MAC address is always the fundamental way a machine identifies itself but it is difficult to use when designing an IP network. For that reason although machines communicate fundamentally using MAC addresses, they normally find and manage each other using IP addresses which are mapped locally to the MAC address. In this way there is typically a “soft relationship” (configurable) between the IP address and the MAC address.
Note that the following only re-establishes fundamental networking. If you’re also running network security, ie LDAP, AD, etc. then there will be other far-ranging consequences. That gets complicated, would be something you need to contact your Network Administrator about (and would more than triple the length of this post).
DHCP - Since the DHCP server assigns “some” IP address to any machine that needs one, all you need to do is restart your client machine’s networking service which can be done by the following command, note that this is comparable to the Windows “ipconfig -renew”
systemctl restart network
When the local machine’s network service restarts, it again broadcasts requesting an IP address. The DHCP server responds, replacing any old configuration on the machine.
Static IP address - Depending on circumstances, changing your MAC address shouldn’t cause much of a network issue although you may need to either wait or manually initiate some ARPs to announce your machine’s changes.
**Reserved Lease **- Since the DHCP server maintains a list of MAC addresses mapped to IP addresses, that list would have to be modified, followed by the procedure described for a regular DHCP IP address above.
Lastly, these are fundamental principles that apply to any virtualized or physical Hosts, it does not matter that your Guest is running on Hyper-V.