Search results

That is the issue: the virtual machine is idle, nothing is eating the CPU, just remote desktop. This seems to be a KVM issue. 81239 root 20 0 32.468g 0.031t 9144 S 206.7 2.5 1742:51 /usr/bin/kvm -id 104 -name FedericoWindows2016 81239 ? Rl 1743:45 /usr/bin/kvm -id 104...

I have a windows server 2016 and the fix does not work, I am still at 130%. Kindly look the image. This is so bad that I am looking for another solution. I have many windows vms.

I checked and I have the fix, but my CPU is still very high, on otherwise idle virtual machines. one of the VMs is Linux, I guess 6 (Mikrotik virtual router)

pveversion -v proxmox-ve: 5.4-1 (running kernel: 4.15.18-15-pve) pve-manager: 5.4-6 (running version: 5.4-6/aa7856c5) pve-kernel-4.15: 5.4-3 pve-kernel-4.15.18-15-pve: 4.15.18-40 pve-kernel-4.15.18-14-pve: 4.15.18-39 pve-kernel-4.15.18-13-pve: 4.15.18-37 pve-kernel-4.15.18-12-pve: 4.15.18-36...

I have only two virtual machines, doing nothing, one windows 2016 and the other one Linux, a Mikrotik virtualized router. Each one shows more than 100% in Top, but virtually nothing inside. What am I doing wrong? The drivers are up to date. How do I fix this and why it is right from the start...

ls /etc/pve/nodes/proxmox/lxc/ 100.conf 101.conf 105.conf root@proxmox:~# mkdir /etc/pve/nodes/proxmox/lxc/demo mkdir: cannot create directory '/etc/pve/nodes/proxmox/lxc/demo': Permission denied root@proxmox:~# chmod 0\7277 /etc/pve/nodes/proxmox/lxc/ chmod: changing permissions of...

I solved it, for the next person. On top of the qemu agent, you need to install the virtio-serial driver. It is found on the same ISO.

It does not work under any condition. If I type qm shutdown XXX, it hangs forever and the VM stays on. It has the Agent installed, and the VM definition has the Agent set. Any idea what am I missing? This is a 2016 server.

Yes, and it does not work for Windows server 2016, 2019 and Windows 10 There are 3 items, neither of them exists. I created the first one, but it still does not shudown the VM. The issue is that if you have dozens of VMs, a user has to go one by one shutting them down manually to avoid crashing...

I can turn-off a Windows Server VM, but shutdown simply does not work. The agent is installed, so what is happening? The VM is Windows Server 2019. Any ideas?

This is a windows server 2016 machine. The machines cannot be rebooted by Proxmox.

I am fully updated, and have a license. But last night it was not updated. How do I know why I am missing this? apt update Get:1 http://security.debian.org stretch/updates InRelease [94.3 kB] Ign:2 http://ftp.us.debian.org/debian stretch InRelease...

I am affected by the issue described below https://askubuntu.com/questions/1033985/kvm-high-host-cpu-load-after-upgrading-vm-to-windows-10-1803 the question is how do I add or change parameters for all my virtual machines in Proxmox. Ideally, the changes would be for all Virtual machines, both...

I need to install a web interface for my SFTP users, who cannot login via shell, only SFTP. I found this software, and don't know how to apply the instructions to the proxmox server https://www.monstaftp.com/guides/how-to-install-monsta-ftp Yours Federico

I installed a third party software on the virtual machine, anydesk, and it works, but I found that the resolution is only 800x600. How do I change to something useful?

I installed Ubuntu Mint as a Virtual machines, but the default resolution is only 800x600. I tried to change the display but there is no option to set a higher resolution. Is there a kernel command line or any other trick to move the resolution to 1280 or higher?

I need to send a link for VNC console access to a VM, to a third party who does not need to login into Proxmox. How can I do that? I tried the obvious, copy and paste the console link for a VM, but of course it says "no ticket found". I don't want the third party to login to Proxmox.

I made it work, partially, buy changing pve-guests.service where it says RefuseManualStart=false to true. It did start manually. Any other service required was running. This is obviously a bug. The service did not start manually, and there was no way to start it by starting any other service...

systemctl status pve-cluster.service * pve-cluster.service - The Proxmox VE cluster filesystem Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-08-01 14:39:59 EDT; 39min ago Process: 122435...

I rebooted the server and Proxmox did not start root@proxmox:~# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION * pve-cluster.service loaded failed failed The Proxmox VE cluster filesystem * pve-firewall.service loaded failed failed Proxmox...