guest-network-get-interfaces' failed - got timeout

[openaspace]

Hi.
I'm experiencing some problems.. after some hours the VM became slow with network also really slow..

after some minutes of connections attempts I read this log:
Dec 23 11:51:08 v3 pvedaemon[30667]: VM 102 qmp command failed - VM 102 qmp command 'guest-network-get-interfaces' failed - got timeout

and the VM return to be fast.

Also if I reboot the VM return to normal speed.
Please help.

Where I'm wrong?

Thanks.

 

[Stoiko Ivanov]

Try to upgrade the qemu guest agent inside the vm to the latest available version
which version of pve are you running? (pveversion -v)

 

[openaspace]

Hi , thanks for the help.
I have already tried to upgrade.. but was already on the latest version.

pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.10-1-pve: 5.3.10-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-3-pve: 5.0.21-7
pve-kernel-5.0.21-2-pve: 5.0.21-7
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
pve-zsync: 2.0-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

 

[openaspace]

I'm trying to update now the host to the latest kernel

 

[openaspace]

Changing the hardware ethernt card from virtio to E100? no?

after restart the host with new kernel all appear to works correctly....
but this was already happened time ago..

How I can test and reproduce the error and avoid to have it when the VM is important that works correctly?

Can be a wrong network configuration in the main host?

 

[openaspace]

...and.. it's normal that with this ubuntu vps the xterm.js console it's not active?
the guest agent is now working correctly.

 

[Stoiko Ivanov]

How I can test and reproduce the error and avoid to have it when the VM is important that works correctly?

Does the error reoccur if you boot into the old kernel?
Else - try upgrading a node without any critical VMs first and see if it's stable

.and.. it's normal that with this ubuntu vps the xterm.js console it's not active?

the xterm.js console for VMs works via a serial console inside the VM:
* create a serial device for the VM (in the Hardware Tab in the GUI)
* configure a serial-getty inside the VM (see e.g. https://wiki.archlinux.org/index.ph...onfigure_console_access_on_the_target_machine) for a howto

I hope this helps!

 

[openaspace]

The latest was the second time the problem was occurred with the old kernel.
I will monitor with the latest installed now.

Thanks for the support!!

 

[openaspace]

After 24 hours with the latest kernel, the VM became slow with low network speed, after reboot return to normal operations.
Now I have changed from HOST to KVM64 .. what I can see to discover some causes? Attached some images of the actual configuration.

Thanks for the support and great holidays!!!

 

[openaspace]

Does the error reoccur if you boot into the old kernel?
Else - try upgrading a node without any critical VMs first and see if it's stable


the xterm.js console for VMs works via a serial console inside the VM:
* create a serial device for the VM (in the Hardware Tab in the GUI)
* configure a serial-getty inside the VM (see e.g. https://wiki.archlinux.org/index.ph...onfigure_console_access_on_the_target_machine) for a howto

I hope this helps!

After 48 hours, without using "host" virtualization mode and switching to kvm64 , it appear to works correctly.