Recent content by Lioh

Okay. In the meanwhile I have found the relevant Backup logs as well: INFO: creating vzdump archive '/mnt/pve/../dump/vzdump-qemu-221-2021_02_06-06_37_47.vma.zst' INFO: issuing guest-agent 'fs-freeze' command INFO: issuing guest-agent 'fs-thaw' command INFO: started backup task...

For SSH it's not really an issue as we are limiting to key based access. Console login and gui is what it's about. So I am going to try to disable the root pw on Linux and see where the telephone will fall from the table

We are using only dedicated user accounts with 2FA. I would like to disable/remove the root account because it is not associated to a user. If deleting is not supported, disabling would be also an option.

Sounds like a lot of overhead to me ;) The question is: is the root account a built-in or is it not there by default. If it's a built-in account, is it safe to remove/disable it within the gui (as long as there are other accounts with similar permissions available of course). Greetings Lioh

Hi all, is it safe to disable the Root Login in the Proxmox GUI? Or maybe even deleting it there completely? Greetings Lioh

This is the only thing I have found in the syslog at the relevant time: Feb 6 16:30:17 pvestatd[2972]: VM 220 qmp command failed - VM 220 qmp command 'query-proxmox-support' failed - unable to connect to VM 220 qmp socket - timeout after 31 retries Feb 6 16:30:18 pvestatd[2972]: status update...

Thanks, here is the VM configuration. The Backup Log has been deleted during the Backup Share cleanup. Not sure if it has also been written to syslog somehow. agent: 1 bootdisk: scsi0 cores: 8 hotplug: disk,network,cpu ide2: none,media=cdrom memory: 197636 name: vapp-220-sql net0...

If you tell me how, sure ;)

Hi all, we are backing up our VMs on a NFS storage. Recently this backup target was running full and in consequence not reachable for some time: Feb 6 16:27:33 kernel: [5717717.340258] nfs: server x.x.x.x not responding, still trying Feb 6 16:27:33 kernel: [5717717.340268] nfs: server...

Yes, that's clear. Thanks. The question was related to the Logical Processors per Socket/Numa split. It seems that on 10 vCPUs it splits like 6:4 instead of 5:5 which might be related to the fact that it only splits on even numbers. So on 12 vCPUs it would probably split 6:6

Does Hot-Unplug also works for you like this? CPU Hotplug works fine with the suggested fixes, but unplug doesn't here.

But why not 5/5. Does it only work with even numbers, like 6/6?

Hi again. we have configured it accordingly and Qemu Guest Agents are running inside the VM (Note: it's a Windows Server 2019 VM, not Linux). I have then increased the number of vCPUs while the VM is running but the change is not reflected within the Windows VM (still sees the old number). Am...

Hi all. I have set up the following processor settings on a Windows VM: And wonder why the Cores are split 6:4 instead of 5:5 Greetings Lioh

Thanks. Does it require NUMA to be enabled in order to work?