I did a status check on two vms to show the status worked on one and not the other. The one it didn't work on is the one that didn't reboot. Whether rebooting or checking the status it says it can't find the configuration file.
Your timeout error is between your client and PVE machine.
QM command only operates on VMs that are local to the host where you execute the QM. It seems like one of the hosts in your cluster is down.
Blockbridge : Ultra low latency all-NVME...
Tried this as a workaround:
# ssh pve-c qm status 220
ssh: connect to host pve-c port 22: Connection timed out
Was surprised to see it timeout. Have been using this setup for over a year.
Could it be that the host name not resolving is the...
I guess I should have read the "fine print" instead if relying on the GUI.
It would be very helpfull, if the setttings would be backed up automatically before being overwritten! Or at least a warning could pop up referring to your link above...
You are trying to stop VM 220, and then status check 221
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
root@pve-node0:~# ip route show
default via 10.9.9.1 dev vmbr0 proto kernel onlink
10.10.9.0/28 dev vmbr0 proto kernel scope link src 10.10.9.10
10.10.9.16/28 dev nic0 proto kernel scope link src 10.10.9.20
10.10.9.32/28 dev nic1 proto kernel...
Very offen, like pvps1 says, due to the high grade of automation in our environments.
This also has the benefit, that "unfamiliar" cluster user with restricted priviledges, can not forget to set the correct vlan in the network configuration of...
Am working on a script to reboot all vms with a certain tag.
Writing the script is going well, but right off encountered an error (see title).
Error encountered with:
qm reboot 220
The vm is there. I can right click and reboot it. (also...
Ten (twelve!) years ago : 2).
For better visibility. But at that time, a pve reboot was needed after any vmbr / bond creation...
Nowadays : 1).
Easier to manage...
Christophe.
Non graphical version hangs as well.
Yes, virtualization is enabled. As I mentioned, I have VMWare ESXi up and running with no issues. Had several VMs and containers running on it. I keep hearing that Proxmox is great, so far, not impressed.
When I was installing on my UM790Pro, I remember I faced a similar situation and the non GUI option did it.
I hope you ensured that you enabled virtualization in the BIOS as well.
Yes, that thread is the one I linked in my OP. It has you download & install mft-4.22.1-11-x86_64-deb.tgz, which worked great on my PVE 8.3 install (and has since been upgraded). It just wasn't working out for the fresh PVE 9.1 install.
Thanks...
When I was installing on my UM790Pro, I remember I faced a similar situation and the non GUI option did it.
I hope you ensured that you enabled virtualization in the BIOS as well.
I have a new PBS server for an offsite sync job. I'm using WAN because it's 13TB of data and VPN is too slow. I set up my ACL rules and everything however, when i start the sync job, it runs for about 10-15mins then it just times out. I tried...
Well, it looks like it's my own problem, even I did not find the issue yet, but the connection to shop.proxmox.com on https times out, when the firewall is in use.
root@server:~# wget https://shop.proxmox.com
--2026-02-12 18:14:50--...