Search results

I set it back to x86-64-v2-AES. I can't remember if I tried host or not, but it should work.

I had a hell of a time upgrading a Win 10 VM (Work PC) to 11,but in the end, changing the CPU type to qemu64 and the machine version to q35 v9.0 worked for me. I also installed the latest virt IO drivers. but that wasn't enough to make it work. Had to use qemu64.

Look all the way right. Login name root. Click that and you'll see a menu option gear for my settings.

I pinned the previous kernel on reboot. Everything came back up as normal. Then rebooted again to use the newer kernel and now it's working. I'm confounded.

Seeing this in journalctl: Jul 29 11:05:25 m90q pvedaemon[1199]: <root@pam> successful auth for user 'root@pam' Jul 29 11:05:25 m90q login[6445]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0) Jul 29 11:05:25 m90q login[6445]: pam_systemd(login:session): Failed to...

I was just updated my 1st node, rebooted and was updating some VM's on my other node and suddenly my 1st node is showing question marks for all the other nodes. I logged into the 2nd node and it can see everything. I rebooted the 1st node again and it still shows question marks for all others...

Try replacing PVE-IP with the IP address of your Proxmox server.

Getting the same on one of my nodes. 4 nodes, 3 backed up fine, 1 failed to same NAS. Running latest pve with all patches.

I had upgraded my qnap nas on the same day and I think they screwed something up with SMB/CIFS. I saw that the files being written on the qnap had a guid for an owner while older backups had usernames that I had set up for the shares. Something is borked. To work around it, I created a NFS...

I run weekly backups to my qnap via samba/cifs. I have a cluster with 2 nodes and 2 standalone Proxmox servers. All have begun to have failures on this weekends backup jobs. I've rebooted the QNAP nas, and rebooted the proxmox nodes as well for good measure. Assuming it might be something on...