New network port created and old one hidden after server sudden shutdwon

[Wodel]

Hi,

We have a 3 nodes HCI cluster.
One of our nodes was accidently shutdown (hard shutdown).
After reboot, all Windows VMs had booted with a new network port (same mac address) but as dhcp port, and the old one was hidden by the OS.

Could you help us understand this?

Regards.

 

[leesteken]

Make a kernel (or other) update was waiting for a reboot?

 

[Wodel]

Hi,

Could you explain more?
Do you mean : "I had updates applied but without reboot" ? No, I have not.


Regards.

 

[leesteken]

Could you explain more?
Do you mean : "I had updates applied but without reboot" ? No, I have not.

Then I don't know why Proxmox would rename the network devices. Or did it only change inside the Windows VM? Then I also don't know why WIndows does that.

 

[Wodel]

Proxmox did not create a new interface on the VMs (at least this is what is shown in the WebUI), there was only one NIC per VM and it stayed that way, the problem happened inside Windows VMs.
After the VMs came back, we found that VMs were not reachable, after verification, we found that their NICs has become dhcp configured, and when we tried to configure them back by fixing their IP addresses, Windows displayed a warning saying that a hidden interface has the same IP.

We are worried about this behavior, because it can cause us real troubles.

 

[leesteken]

We are worried about this behavior, because it can cause us real troubles.

Maybe it's something specific to Windows VMs being unexpectedly shutdown hard because i have never seen this with Linux, but maybe other people here know better.
I think the best prevention is to not shutdown Proxmox hard and to prevent unexpected power loss with something like a UPS and proper shutdown (and regular backups via PBS).