Wow, same here! Your suggestion worked but if I reboot the Windows 10 VM it defaults back to the 800X600 resolution. And here's the worst part for me: in order to access the OVMF UEFI I must remove my external USB HDD I have set to passthrough from the Hardware section of the VM but I can...
Yes, you are correct. I get the resolution I want using RDP but I'm using NoMachine for my VM remote connections as it's convenient having everything accessible through "one pane of glass". I've seen where using "SeaBIOS" allows one to change the resolution but this would require a reinstall...
I have a Windows 10 VM (with the latest updates) running on Proxmox [pve-manager/6.1-5/9bf06119 (running kernel: 5.3.13-1-pve)]. I've gone into the OVMF EFI settings and adjusted the resolution to 1920x1080 but booting back into Windows 10 I'm still stuck at the 800x600...
Would anyone be able to provide an update on this matter? I'm still unable to get IGD passthrough to work on an Intel NUC8i7BEH with the latest Proxmox (6.0-11) but is it confirmed this will work in kernel 5.1? I thought about using passthrough on the Thunderbolt port but have...
I removed the disk from VM 101 through the UI and then executed: rbd rm cephfs_vm/vm-101-disk-0 which seems to have done the
Doh! You were correct! I was copying the VHDX from an external USB drive plugged into Proxmox1 but VM 101 was sitting on Proxmox4. I thought since everything...
It's actually VM 101 (vm-101-disk-0) I'm working with...vm-100-disk-0 is attached to another VM that is irrelevant. I created VM 101 and by default vm-101-disk-0 was created in the cephfs_vm pool. I'm now trying to import a converted VHDX file of the same name (vm-101-disk-0) to...
I'm trying to import a VHDX file which was converted to RAW into a Ceph pool (cephfs_vm) but receive the following error:
root@proxmox01:/mnt/pve/cephfs# qm importdisk 101 ./vm-101-disk-0 cephfs_vm
Configuration file 'nodes/proxmox01/qemu-server/101.conf' does not exist
Yes, you've been a great help...thank you!
I believe that's initially what put me in this dilemma. I understand I could delete the offending key but I never put that key in there, it appears executing: pvecm updatecerts and a combination of SSH or logging into the Web UI did all of that. So...
Hello again Stoiko,
Believe it or not, starting with a clean slate again and by this I mean:
and then executing
created new SSH keypairs as well as symlinked...
Thank you for your reply! Looks like those files are not symlinked:
root@proxmox1:/etc/pve/priv# ls -alh
drwx------ 2 root www-data 0 Dec 19 2017 .
drwxr-xr-x 2 root www-data 0 Dec 31 1969 ..
-rw------- 1 root www-data 1.7K Dec 19 2017 authkey.key
-rw------- 1 root www-data...
I apologize it's taken so long to get back to this but I was able to dedicate some time yesterday to troubleshooting this but the issue still remains.
I decided to start fresh so I set both Proxmox1 and Proxmox2 to allow password login: PasswordAuthentication yes. I then deleted everything in...