All VM can't accessible after kernel UPdate of the nodes?

ArnOCP

Member
Aug 2, 2023
13
0
6
Good morning,
My VM said are start but i cannot access them through ssh, gui, services......>_Console.
Please can you helping me?
 
You did not give many details about your system. By far too few.

So you get only a very sparse reply: check your NIC names and verify the network settings.
 
  • Like
Reactions: floh8
Sorry, i was in a big stress^^
seems it because of the new kernel 6.8.12-29-pve, on PVE 8.4.19
I revert to 6.8.12-28-pve and it appear to be ok the VM are now accessibles, I cross fingers
 
Last edited:
Hello,
I confirm with the old kernel 6.8.12-28-pve all VM's Worked (during day and 18 hours the VM's are ok)
So there is a problem with the new 6.8.12-29-pve kernel on proxmox 8.4.19 VE?
 
these are still too little facts. how does your setup look like? what do you mean exactly with 'aren't accessible' (not reachable via network?, don't start?) ?
the logs from the two boots would be interesting but the most important part was already mentioned by @UdoB :

check your NIC names and verify the network settings.
 
Hello,
Thx for replies.
how does your setup look like?
I have an 3 nodes architectures and a SAN to hosts VM's attached in ISCSI.
The PVE is in 8.4.19 version on the 3 nodes.

what do you mean exactly with 'aren't accessible' (not reachable via network?, don't start?) ?
The VM are for the essentials Debian web servers, if i start the PVE on the new kernel the vm are shown as started in the PVE GUI but i cannot acces them neither via web, ssh or via the VNC console in the pve gui.

check your NIC names and verify the network settings.
The NIC names in the PVE are eno1, eno 2...vmbr0 for the bridge. for example
1780640856373.png
I was surprise that with the kernel 6.8.12-29-pve the troubleshoot occurs despite with the kernel 6.8.12-28-pve all is working?

Regards,
 
can you post the journal/dmesg from both the working and the non working state?
 
Here are the boot log of working kernel, i cannot find the not working log ?!?
you have to boot the server with the not working kernel and run the commands again
 
you have to boot the server with the not working kernel and run the commands again
That's what I was afraid of^^
I can't do it right now, because the PvE servers are hosting functional servers.