Thanks for your reply,is there any option that only affect that particular vm rather than host server. what will be the impact of update cluster nodes as you said. does this update need to restart nodes after update?
Here is the vmid.conf file
i have 3 Host cluster, in which only 1 VMs is triggering this events.
the link you have provided is showing following resolutoin, but i am scared to do this reason is i have no idea what will be the outcome of this after this. these hosts are in production.
Disable Large Receive...
Thankyou for your reply, i have found out that below logs are also relates to this. what are the reasons and solution for this please help
Aug 7 12:08:21 server1 qm: <root@pam> starting task UPID:TES-HS03:0001192F:107E79E0:5B694565:qmstart:108:root@pam:
Aug 7 12:08:21 server1...
i am receiving attached error logs on one of my proxmox host. i have check it via migrating all the VM's to seperate host and same errors was generated on different host. after finding now i know that these logs are due to only 1 VM's machine. i am not able to diagnose it further why...
i am trying to install Windows Sever 2016 on Proxmox 5.0.31 and 5.1-46, but not able to provide virtio drivers.
i had added virtio-win-0.1.141 drivers but intallation is not able to show any storage. and showing following error.
i have a PVE 5 server which is hosted 7 VMs, which as working fine since few months. but now from last few days different VMs are hanging and also Host server is crashing. found below logs. please help
Mar 13 09:44:05 kernel: NMI watchdog: BUG: soft lockup - CPU#36 stuck for 23s...