network disconnect windows 10 client

[tecniche]

I have a recurring but infrequent problem.
It happens on both proxmox version 6 and version 7.
Some Windows 10 VMs suddenly lose connectivity and the solution to restore it is to disable and re-enable the network adapter from the proxmox console.
There is no information about this in the windows event viewer.
There are no details in the proxmox logs either.
I have tried both the e1000 driver and virtio.
I also tried updating the drivers but that didn't help.
Has anyone encountered a similar problem?

 

[Moayad]

Hello,

What is the Windows ISO installed? it's German ISO?
Have you tried to update the VirtIO to the latest stable version?
Did you see anything interesting in the syslog or the Event Logs in the Windows VM itself?

 

[tecniche]

Hello, the iso used is in Italian.
The VMS are at version 22H2 of windows 10.
The virtual machines we create, are restored from an initially saved dump, we don't always use an iso.
I tried to update the drivers to the latest version.
Unfortunately, there is no trace of the problem in the logs.
This condition also occurs with windows server.
While with linux, of any distribution, it has never occurred.
Thank you.

 

[OliviaBurns]

I have a recurring but infrequent problem.
It happens on both proxmox version 6 and version 7.
Some Windows 10 VMs suddenly lose connectivity and the solution to restore it is to disable and re-enable the network adapter from the proxmox console.
There is no information about this in the windows event viewer.
There are no details in the proxmox logs either.
I have tried both the e1000 driver and virtio.
I also tried updating the drivers but that didn't help.
Has anyone encountered a similar problem? apk mod getmodnow is not only a platform providing Mod APK, but also an open community for everyone to share the same passion.

Check the network configuration in Proxmox.
Make sure the VM has enough resources to allocate.
Monitor for Proxmox and Windows 10 updates.
Double check the network driver type (e1000 or virtio).
Turn off the security software or the firewall in the VM.
Check the VM's log in Windows.
Verify network hardware status.
Use a monitoring tool to monitor network resources and activity.
Consider using Wireshark to monitor network communications.
Try to run the standalone VM to see if the documentation issue is related to the interaction between the different VMs.

 

[Dirky_uk]

Hi, did you ever solve this? I have started using Windows 10 on Proxmox 8.1.4 and noticed this exact thing.
At first I thought it was the host pc as I was using a Lenovo Thinkpad with an external USB3 adaptor which contained ethernet.
I moved the VM to my trusty core i7 desktop but the problem is occurring there now.

One thing I noticed in the eventwr logs at the very time it went off is

Successfully scheduled Software Protection service for re-start at ..... Reason: RulesEngine

Any clues as where to look to resolve this?
Thanks

 

[Dirky_uk]

Ok, did a bit more reading about this and realised I was using the Intel E100 emulated driver. It seems better performance is seen with the VirtIO driver. I downloaded that for Windows installed it and changed the network type on the host. Will see how this hold up.