failed to query local AF_VSOCK CID

[informant]

Hi i have since last proxmox update in one vm following error:

what is it, it dont comes before. i have solve as workarround it with
nano /etc/default/grub
systemd.ssh_auto=no
update-grub
reboot

any ideas?

 

[j.theisen]

Hi @informant

thanks for posting on the forum!

Do these messages cause any issues for your VM or are they "just" annoying?

Have just booted up a test VM of mine and saw the same messages in the journal.

Best regards
Jonas

 

[informant]

Hi at moment i have found this message only on 1 vm, i see it on start console.

 

[AlexanderB]

Having the same issue on one VM. I don´t know if this will cause an issue in the future.

 

[jelzin]

Same here, 2 new debian 13 vm's installed, on both consoles the messages below:

systemd-ssh-generator[1416]: Failed to query local AF_VSOCK CID: Cannot assign requested address


The command 'lsmod | grep vsock' generates this output:

vsock_loopback 12288 0
vmw_vsock_virtio_transport_common 61440 1 vsock_loopback
vmw_vsock_vmci_transport 45056 0
vsock 61440 3 vmw_vsock_virtio_transport_common,vsock_loopback,vmw_vsock_vmci_transport
vmw_vmci 110592 1 vmw_vsock_vmci_transport

btw: Proxmox VE 9.2.20 and i've just updated it.

 

[major caveira]

Same message here

 

[lukeh990]

I've seen the same message on some of my VMs. Doesn't seem to affect anything though.

 

[pugglewuggle]

Same here. This is new with the new update. Any news?

 

[t-nician]

Hi @informant

thanks for posting on the forum!

Do these messages cause any issues for your VM or are they "just" annoying?

Have just booted up a test VM of mine and saw the same messages in the journal.

Best regards
Jonas

I'm also getting this issue on a fresh Debian 13 VM that I setup a couple of hours ago.

It causes the RAM usage stat to become inaccurate

 

[Neobin]

Has nothing to do with PVE specifically:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137216

It causes the RAM usage stat to become inaccurate

I doubt that...