Installing Kali VM

fwr

New Member
Dec 8, 2024
7
0
1
Hi. I'm new to Proxmox and after installing Kali I received this error when I start the machine. I would appreciate some input so I can troubleshoot this problem. Also, Can I find these kind of information on Proxmox documentation? Thanks
 

Attachments

  • Kali VM error.png
    Kali VM error.png
    8.4 KB · Views: 15
Hi. I'm new to Proxmox and after installing Kali I received this error when I start the machine. I would appreciate some input so I can troubleshoot this problem. Also, Can I find these kind of information on Proxmox documentation? Thanks
Hello the attachment is empty (at least on my side). Please post the error and the config of the vm with qm config VMID
 
Hello the attachment is empty (at least on my side). Please post the error and the config of the vm with qm config VMID
Hi, I apologies for the mistake.

1733778915304.png
1733778951952.png

I also just noticed this, could be possibly a problem or the problem.

1733779383956.png
 

Attachments

  • 1733779366813.png
    1733779366813.png
    12.2 KB · Views: 7
Last edited:
Hi,
does Kali Linux come with a signed kernel? Otherwise, you can't use the pre-enrolled-keys setting for the EFI disk.
 
  • Like
Reactions: Kingneutron
Kali does not come with signed kernel. But I found this issue while troubleshooting and so far I have not found a fix for it.

1733866932639.png

I reinstalled and tried to start again and receive this error:

1733867713258.png
 
Last edited:
Kali does not come with signed kernel. But I found this issue while troubleshooting and so far I have not found a fix for it.

View attachment 78919

I reinstalled and tried to start again and receive this error:

View attachment 78921
Is this inside the VM? Did you enable the guest agent in the VM configuration and apply the change (shutdown+start the VM or use the Reboot button in the UI, reboot from inside the guest is not enough)? If that doesn't help, please share the full journal for that boot.
 
Hi Fiona,
I only now was able to troubleshoot this problem. I went through some of your post related to qemu but nothing worked. Here is the logs from my proxmox:

root@homserver:~# apt install qemu-guest-agent
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
qemu-guest-agent is already the newest version (1:7.2+dfsg-7+deb12u7).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@homserver:~# systemctl start qemu-guest-agent
A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details.
root@homserver:~# journalctl -xe
Jan 07 18:15:16 homserver systemd[1]: Started user@0.service - User Manager for UID 0.
░░ Subject: A start job for unit user@0.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit user@0.service has finished successfully.
░░
░░ The job identifier is 1283.
Jan 07 18:15:16 homserver systemd[1]: Started session-9.scope - Session 9 of User root.
░░ Subject: A start job for unit session-9.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-9.scope has finished successfully.
░░
░░ The job identifier is 1383.
Jan 07 18:15:16 homserver login[5001]: ROOT LOGIN on '/dev/pts/0'
Jan 07 18:15:56 homserver systemd[1]: Expecting device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent.0...
░░ Subject: A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has begun execution.
░░
░░ The job identifier is 1581.
Jan 07 18:17:01 homserver CRON[5305]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 07 18:17:01 homserver CRON[5306]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 07 18:17:01 homserver CRON[5305]: pam_unix(cron:session): session closed for user root
Jan 07 18:17:27 homserver systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed ou>
Jan 07 18:17:27 homserver systemd[1]: Timed out waiting for device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent>
░░ Subject: A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has finished with a failure.
░░
░░ The job identifier is 1581 and the job result is timeout.
Jan 07 18:17:27 homserver systemd[1]: Dependency failed for qemu-guest-agent.service - QEMU Guest Agent.
░░ Subject: A start job for unit qemu-guest-agent.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit qemu-guest-agent.service has finished with a failure.
░░
░░ The job identifier is 1484 and the job result is dependency.
Jan 07 18:17:27 homserver systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
Jan 07 18:17:27 homserver systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed w>
lines 3759-3805/3805 (END)

1736291937049.png

1736291961648.png

Any ideas what am I missing?
Thank you.
 
Hi Fiona,
I only now was able to troubleshoot this problem. I went through some of your post related to qemu but nothing worked. Here is the logs from my proxmox:

root@homserver:~# apt install qemu-guest-agent
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
qemu-guest-agent is already the newest version (1:7.2+dfsg-7+deb12u7).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@homserver:~# systemctl start qemu-guest-agent
A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details.
root@homserver:~# journalctl -xe
Jan 07 18:15:16 homserver systemd[1]: Started user@0.service - User Manager for UID 0.
░░ Subject: A start job for unit user@0.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit user@0.service has finished successfully.
░░
░░ The job identifier is 1283.
Jan 07 18:15:16 homserver systemd[1]: Started session-9.scope - Session 9 of User root.
░░ Subject: A start job for unit session-9.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-9.scope has finished successfully.
░░
░░ The job identifier is 1383.
Jan 07 18:15:16 homserver login[5001]: ROOT LOGIN on '/dev/pts/0'
Jan 07 18:15:56 homserver systemd[1]: Expecting device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent.0...
░░ Subject: A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has begun execution.
░░
░░ The job identifier is 1581.
Jan 07 18:17:01 homserver CRON[5305]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 07 18:17:01 homserver CRON[5306]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 07 18:17:01 homserver CRON[5305]: pam_unix(cron:session): session closed for user root
Jan 07 18:17:27 homserver systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed ou>
Jan 07 18:17:27 homserver systemd[1]: Timed out waiting for device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent>
░░ Subject: A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has finished with a failure.
░░
░░ The job identifier is 1581 and the job result is timeout.
Jan 07 18:17:27 homserver systemd[1]: Dependency failed for qemu-guest-agent.service - QEMU Guest Agent.
░░ Subject: A start job for unit qemu-guest-agent.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit qemu-guest-agent.service has finished with a failure.
░░
░░ The job identifier is 1484 and the job result is dependency.
Jan 07 18:17:27 homserver systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
Jan 07 18:17:27 homserver systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed w>
lines 3759-3805/3805 (END)

View attachment 80362

View attachment 80363

Any ideas what am I missing?
Thank you.
You need to install the QEMU guest agent inside the guest, not on the host. If the host is not virtualized itself, you should uninstall the guest agent from the host too.
 
I found out what I was doing wrong. I was using a qcow2 file and I was trying create a VM the same way I created Linux Debian and it does not work the same way. I really appreciate your input. Thank you!