Hello to everyone,
I issued strange virtual network adapted behavior on VMs.
Everything works just fine until reboot host. When reboot VMs this problem don't appear.
After rebooting host and VMs bootup successfully without any error displayed, i found that my VMs have different IP gathered from DHCP not that static one i set on NIC.
I investigating issue and find that on VM device manager appear NIC with #2 (#3, #4 ... etc the number rises on every host reboot).
Old VM NIC was hidden, i can see it if i thick show hidden devices.
also if i try to setup same static address it displays error that this address is used by another LAN adapter, and if i choose to set it up default gateway setup was omitted.
This cause several problem:
- if i left IP from dhcp VM haves connectivity but, server functions which are related to static IP don't work (DNS, AD DC, etc)
- if i left IP from dhcp i haven't easy access to my VMs (remote desktop or network share)
My setup is like described bellow:
VMs have Windows 10 20H2 version and Windows Server 2019 with latest update on this day.
VMs hardware configuration is as suggested by manual : using VirtIO Storage, VirtIO KVM Net paravirualised, and Ballooning (uploaded drivers by installation process of Windows OSs - versions from virtio-win-0.1.190.iso )
After successful VM OS installations i running post installation virtio-guest-tool.exe from virtio-win-0.1.190.iso as well as guest-agent app installation.
I setup static IP on both Windows machines.
Proxmox packages are:
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.11-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-4
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-8
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
Please anyone who can help me?
I issued strange virtual network adapted behavior on VMs.
Everything works just fine until reboot host. When reboot VMs this problem don't appear.
After rebooting host and VMs bootup successfully without any error displayed, i found that my VMs have different IP gathered from DHCP not that static one i set on NIC.
I investigating issue and find that on VM device manager appear NIC with #2 (#3, #4 ... etc the number rises on every host reboot).
Old VM NIC was hidden, i can see it if i thick show hidden devices.
also if i try to setup same static address it displays error that this address is used by another LAN adapter, and if i choose to set it up default gateway setup was omitted.
This cause several problem:
- if i left IP from dhcp VM haves connectivity but, server functions which are related to static IP don't work (DNS, AD DC, etc)
- if i left IP from dhcp i haven't easy access to my VMs (remote desktop or network share)
My setup is like described bellow:
VMs have Windows 10 20H2 version and Windows Server 2019 with latest update on this day.
VMs hardware configuration is as suggested by manual : using VirtIO Storage, VirtIO KVM Net paravirualised, and Ballooning (uploaded drivers by installation process of Windows OSs - versions from virtio-win-0.1.190.iso )
After successful VM OS installations i running post installation virtio-guest-tool.exe from virtio-win-0.1.190.iso as well as guest-agent app installation.
I setup static IP on both Windows machines.
Proxmox packages are:
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.11-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-4
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-8
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
Please anyone who can help me?
