Let's see, I'll give an example of what happens to me.
I have bought a dedicated server in a hosting company, and buy 24 ipv4 and 2 ipv6.
Imagine that the ipv4 that I want to put to my vm is the following: 111.111.111 (It is an example).
Well, when I install windows in vm, it assigns an automatic ipv4 that does not even exist.
In the network options of vm I have put the bridge corresponding to the ip that I wanted to put to that machine.
This is the ipv4 that is assigned automatically and I do not want: 169.254.92.83
(This error occurs to me in all the operating systems that I tried to install)
I have bought a dedicated server in a hosting company, and buy 24 ipv4 and 2 ipv6.
Imagine that the ipv4 that I want to put to my vm is the following: 111.111.111 (It is an example).
Well, when I install windows in vm, it assigns an automatic ipv4 that does not even exist.
In the network options of vm I have put the bridge corresponding to the ip that I wanted to put to that machine.
This is the ipv4 that is assigned automatically and I do not want: 169.254.92.83
(This error occurs to me in all the operating systems that I tried to install)
Code:
proxmox-ve: 4.4-86 (running kernel: 4.4.49-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.49-1-pve: 4.4.49-86
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-49
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-97
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80