VM - Amount of Disk Used and IP Information Not Available

Hi,

For IP information you need a qemu-guest-agent installed in the VM and the agent flag must be set in the options tap.
 
We need to install on the VM we have created or we need to install on pve

you have to install in inside the VM (most distributions have it on their repositories), and activate the 'Guest Agent' option in the VM configuration on PVE
 
yes. also inside your VM, start the qemu-ga service and enable it
 
please DO NOT send screenshot from simple text error messages, just send the text - much easier to follow.

[root@master /]# service qemu-ga start
Redirecting to /bin/systemctl start qemu-ga.service
Failed to start qemu-ga.service: Unit not found.

[root@master /]# systemctl start qemu-guest-agent
A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details.
 
A dependency for qemu-guest-agent.service failed. See 'journalctl -xe' for details

what does journalctl -xe say?
 
A dependency for qemu-guest-agent.service failed. See 'journalctl -xe' for details

what does journalctl -xe say?


journalctl -xe
Nov 20 19:12:04 master.eselax.com sshd[21208]: Received disconnect from 49.88.112.68 port 43698:11: [preauth]
Nov 20 19:12:04 master.eselax.com sshd[21208]: Disconnected from 49.88.112.68 port 43698 [preauth]
Nov 20 19:12:04 master.eselax.com sshd[21208]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.68 user=root
Nov 20 19:12:04 master.eselax.com sshd[21206]: Received disconnect from 49.88.112.68 port 63716:11: [preauth]
Nov 20 19:12:04 master.eselax.com sshd[21206]: Disconnected from 49.88.112.68 port 63716 [preauth]
Nov 20 19:12:04 master.eselax.com sshd[21206]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.68 user=root
Nov 20 19:13:01 master.eselax.com systemd[1]: Started Session 252 of user root.
-- Subject: Unit session-252.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-252.scope has finished starting up.
--
-- The start-up result is done.
Nov 20 19:13:01 master.eselax.com CROND[21241]: (root) CMD (/etc/nginx/utilities/https_vhosts.sh >> /dev/null 2>&1)
Nov 20 19:13:07 master.eselax.com PAM-hulk[21249]: Brute force detection active: 580 LOGIN DENIED -- EXCESSIVE FAILURES -- IP TEMP BANNED
Nov 20 19:13:07 master.eselax.com unix_chkpwd[21252]: password check failed for user (root)
Nov 20 19:13:07 master.eselax.com sshd[21249]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.68 user=root
Nov 20 19:13:07 master.eselax.com sshd[21249]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
Nov 20 19:13:08 master.eselax.com PAM-hulk[21247]: Brute force detection active: 580 LOGIN DENIED -- EXCESSIVE FAILURES -- IP TEMP BANNED
Nov 20 19:13:08 master.eselax.com unix_chkpwd[21254]: password check failed for user (root)
Nov 20 19:13:08 master.eselax.com sshd[21247]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.68 user=root
Nov 20 19:13:08 master.eselax.com sshd[21247]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
Nov 20 19:13:09 master.eselax.com sshd[21249]: Failed password for root from 49.88.112.68 port 54388 ssh2
Nov 20 19:13:09 master.eselax.com PAM-hulk[21249]: Brute force detection active: 580 LOGIN DENIED -- EXCESSIVE FAILURES -- IP TEMP BANNED
Nov 20 19:13:09 master.eselax.com unix_chkpwd[21256]: password check failed for user (root)
Nov 20 19:13:09 master.eselax.com sshd[21249]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
Nov 20 19:13:09 master.eselax.com sshd[21247]: Failed password for root from 49.88.112.68 port 34236 ssh2
Nov 20 19:13:10 master.eselax.com PAM-hulk[21247]: Brute force detection active: 580 LOGIN DENIED -- EXCESSIVE FAILURES -- IP TEMP BANNED
Nov 20 19:13:10 master.eselax.com unix_chkpwd[21258]: password check failed for user (root)
Nov 20 19:13:10 master.eselax.com sshd[21247]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
Nov 20 19:13:11 master.eselax.com sshd[21249]: Failed password for root from 49.88.112.68 port 54388 ssh2
Nov 20 19:13:12 master.eselax.com PAM-hulk[21249]: Brute force detection active: 580 LOGIN DENIED -- EXCESSIVE FAILURES -- IP TEMP BANNED
Nov 20 19:13:12 master.eselax.com unix_chkpwd[21260]: password check failed for user (root)
Nov 20 19:13:12 master.eselax.com sshd[21249]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
Nov 20 19:13:12 master.eselax.com sshd[21247]: Failed password for root from 49.88.112.68 port 34236 ssh2
Nov 20 19:13:12 master.eselax.com PAM-hulk[21247]: Brute force detection active: 580 LOGIN DENIED -- EXCESSIVE FAILURES -- IP TEMP BANNED
Nov 20 19:13:12 master.eselax.com unix_chkpwd[21262]: password check failed for user (root)
Nov 20 19:13:12 master.eselax.com sshd[21247]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
Nov 20 19:13:13 master.eselax.com sshd[21249]: Failed password for root from 49.88.112.68 port 54388 ssh2
Nov 20 19:13:13 master.eselax.com sshd[21249]: Received disconnect from 49.88.112.68 port 54388:11: [preauth]
Nov 20 19:13:13 master.eselax.com sshd[21249]: Disconnected from 49.88.112.68 port 54388 [preauth]
Nov 20 19:13:13 master.eselax.com sshd[21249]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.68 user=root
Nov 20 19:13:14 master.eselax.com sshd[21247]: Failed password for root from 49.88.112.68 port 34236 ssh2
Nov 20 19:13:14 master.eselax.com sshd[21247]: Received disconnect from 49.88.112.68 port 34236:11: [preauth]
Nov 20 19:13:14 master.eselax.com sshd[21247]: Disconnected from 49.88.112.68 port 34236 [preauth]
Nov 20 19:13:14 master.eselax.com sshd[21247]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.68 user=root
 
please try starting the guest-agent service again, and then checking journalctl -xe right after you do that.
 
there has to be some error output in the journals about qemu guest agent. try to find it and investigate
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!