Installed kali, pfsense, and now I cannot install any other Vm......

[Jrivera]

Hi guys new to proxmox and came from oracle VM, I cannot install any VM anymore because i keep running into the NO VNC could not connect to server error- even to install windows on a VM, dont know what to do, have tried what google has to offer but thought I would ask here......please feel free to recommend me stuff to try out.....


root@pve:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
root@pve:~#

 

[dylanw]

Hi,

Does this happen for every VM? Could you post the config of on of the VMs (qm config <VMID>)?
Is there an entry in the task log for the failure. If so, please post the task log also.
Finally, could you use the following command to print incoming system logs in real-time, then attempt to open the console. With this we can see if any useful errors are printed: journalctl -f

Note: You can use the "Code" formatting option when posting command output, for better readability in the forum.

 

[Jrivera]

where would the VMID be located or stored?

also the weird part is that this kinda all started happening after Pfsense was set up and installed on a VM


pfsense has not crashed or giving me any issues and its up and running but even installing windows on a VM fails, tries to lauch it from boot, I get to see the windows log loading but then boom get the failed to connect to server happens and fails to go thru installation....

I wanted to uninstall pfsense and keep installing the rest of vms but took me a minute to get it set up honestly and dont just want to remove it.

any help would be appreciated.




journalctl -f results after ran one of the VMs and failed.

-- Journal begins at Sat 2022-04-09 13:17:00 EDT. --
Apr 12 09:40:03 pve systemd[1]: 102.scope: Consumed 46.600s CPU time.
Apr 12 09:40:04 pve pveproxy[69521]: problem with client ::ffff:10.0.0.218; Connection reset by peer
Apr 12 09:40:04 pve pvedaemon[63752]: <root@pam> end task UPID:pve:00012DA0:00311795:62558109:vncproxy:102:root@pam: OK
Apr 12 09:40:04 pve pvedaemon[63752]: <root@pam> starting task UPID:pve:00012E06:00312874:62558134:vncproxy:102:root@pam:
Apr 12 09:40:04 pve pvedaemon[77318]: starting vnc proxy UPID:pve:00012E06:00312874:62558134:vncproxy:102:root@pam:
Apr 12 09:40:04 pve qmeventd[77317]: Starting cleanup for 102
Apr 12 09:40:04 pve qmeventd[77317]: Finished cleanup for 102
Apr 12 09:40:05 pve qm[77320]: VM 102 qmp command failed - VM 102 not running
Apr 12 09:40:05 pve pvedaemon[77318]: Failed to run vncproxy.
Apr 12 09:40:05 pve pvedaemon[63752]: <root@pam> end task UPID:pve:00012E06:00312874:62558134:vncproxy:102:root@pam: Failed to run vncproxy.
Apr 12 09:40:58 pve pvedaemon[61761]: <root@pam> end task UPID:pve:000125A1:002FD716:62557DD4:vncproxy:101:root@pam: OK
Apr 12 09:40:58 pve pvedaemon[61761]: <root@pam> starting task UPID:pve:00012E95:00313DA9:6255816A:vncproxy:101:root@pam:

 

[Jrivera]

Update= tried runnign alien vault and OSSIM and seems to go thru but I have tried other ISOs and fails....

 

[dylanw]

where would the VMID be located or stored?

Apologies for my lack of clarity. The VMID is just the number assigned to the VM, which from the system log (journalctl) seems to be 102.

journalctl -f results after ran one of the VMs and failed.

Just to confirm, was VM 102 still running when you accessed the console. The system logs suggest that it wasn't meaning the issue could be with the VM itself failing:

Apr 12 09:40:05 pve qm[77320]: VM 102 qmp command failed - VM 102 not running

I wanted to uninstall pfsense and keep installing the rest of vms but took me a minute to get it set up honestly and dont just want to remove it.

I don't think pfsense should be the problem here.

What kind of storage are your ISOs stored on (e.g., lvm-thin, NFS, ZFS, etc.)?

Could you post:

• Output of: qm config 102
• The task log from starting VM 102 (seen either at the bottom of the GUI or in <NODE> -> "Task History" after running the VM).

 

[Jrivera]

deleted the 102 but here is a similar one that cannot end the installation either and fails everytime, most of them fail at (Select and install the software step)

qp config 100

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Apr 13 10:36:07 EDT 2022 on pts/1
root@pve:~# qm config 100
boot: order=scsi0;ide2;net0
cores: 4
ide2: local:iso/kali-linux-2022.1-installer-amd64.iso,media=cdrom
memory: 4096
meta: creation-qemu=6.1.0,ctime=1649859435
name: kali
net0: virtio=C2:4E:8B:9A:1D:88,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-lvm:vm-100-disk-0,size=8G
scsihw: virtio-scsi-pci
smbios1: uuid=e367b0eb-f693-4f74-af6f-8691a002fd8b
sockets: 1
vmgenid: 5e65e07f-625f-4fc2-853b-d302864ec958
root@pve:~#

most VMS I try to install fail at this one step.....and there is space but not sure what the cause might be..

 

[Jrivera]

Apologies for my lack of clarity. The VMID is just the number assigned to the VM, which from the system log (journalctl) seems to be 102.


Just to confirm, was VM 102 still running when you accessed the console. The system logs suggest that it wasn't meaning the issue could be with the VM itself failing:

Apr 12 09:40:05 pve qm[77320]: VM 102 qmp command failed - VM 102 not running

I don't think pfsense should be the problem here.

What kind of storage are your ISOs stored on (e.g., lvm-thin, NFS, ZFS, etc.)?

Could you post:

• Output of: qm config 102
• The task log from starting VM 102 (seen either at the bottom of the GUI or in <NODE> -> "Task History" after running the VM).

yes VM was running, weird in my opinion right?

 

[Jrivera]

appreciate you giving me a hand on this, btw is there a support line where to call and get some remote support, I'd like to see if I am doing it all the wrong installation but I have followed same steps as others to install and keeps failing...

 

[dylanw]

most VMS I try to install fail at this one step.....and there is space but not sure what the cause might be..

In this particular case, it could be failing because the VM doesn't have enough disk space assigned. Kali recommend a minimum of 20Gb in their installation guide[1], and since it contains a massive amount of packages by default, including a desktop environment, I'm not sure 8Gb would be enough. However, to properly pinpoint the reason for failure, you can follow Kali's installation troubleshooting guide [2] to get logs.

This lack of storage could have also been an issue with the Windows install. Although I believe the Windows installer is generally uninformative about reasons for failure..

Note: It's good practice to set the VM's CPU type to 'Host' so that it can make use of all your CPU's features. This may even be a necessity to get Windows 11 working, but I have heard mixed reports. There are only few cases in which you should select the default (kvm64), such as when you must guarantee compatibility between cluster nodes with differing CPUs.

appreciate you giving me a hand on this, btw is there a support line where to call and get some remote support, I'd like to see if I am doing it all the wrong installation but I have followed same steps as others to install and keeps failing...

No worries, we appreciate your interest in the products! We do offer enterprise-level support, with guaranteed initial response times and remote support via SSH (for Standard and Premium subscription level) [3]. Any level of subscription also grants access to our Enterprise repository, which contains the most stable and tested software. Unfortunately, phone support is not covered as part of the subscription agreement [4]. If you'd like to find out more, you can take a look at our website [3].


[1] https://www.kali.org/docs/installation/hard-disk-install/
[2] https://www.kali.org/docs/troubleshooting/troubleshooting-a-kali-linux-install/
[3] https://proxmox.com/en/proxmox-ve/pricing
[4] https://proxmox.com/en/downloads/item/proxmox-ve-subscription-agreement

 

[Jrivera]

Thank you very much! will give it more space and see how it goes....

 

[Jrivera]

@dylanw, just wanted to thank you, I think disk space was the issue the whole time, for windows 12GB was good to get going, for Kali gave 24 GB and good to go....

 

[dylanw]

No problem, I'm happy to hear you found the problem! Would you mind marking the thread as "solved", so that others with similar issues can find the solution more easily?