Recent content by mhayhurst

  1. Cannot Change Resolution In Windows 10 VM

    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...
  2. Cannot Change Resolution In Windows 10 VM

    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...
  3. Cannot Change Resolution In Windows 10 VM

    After changing to "SeaBIOS" the Windows 10 VM will no longer boot:
  4. Cannot Change Resolution In Windows 10 VM

    Hello everyone, 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...
  5. Passhtrough 8gen intel Nuc

    Thank you for the info! I will give this a try!
  6. Passhtrough 8gen intel Nuc

    Hello everyone, 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...
  7. Configuration file 'nodes/proxmox01/qemu-server/101.conf' does not exist

    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 trick! 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...
  8. Configuration file 'nodes/proxmox01/qemu-server/101.conf' does not exist

    Hi Wolfgang, 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...
  9. Configuration file 'nodes/proxmox01/qemu-server/101.conf' does not exist

    Hello everyone, 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 That...
  10. TASK ERROR: Failed to run vncproxy.

    Glad it worked but this was mentioned in my Post #12: rm ~/.ssh/* I even say: Did you try: "starting with a clean slate" as I discussed and then executing: pvecm updatecerts?
  11. TASK ERROR: Failed to run vncproxy.

    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...
  12. TASK ERROR: Failed to run vncproxy.

    Hello again Stoiko, Believe it or not, starting with a clean slate again and by this I mean: rm ~/.ssh/* rm /etc/ssh/ rm /etc/ssh/ssh_known_hosts rm /etc/pve/priv/authorized_keys rm /etc/pve/priv/known_hosts and then executing pvecm updatecerts created new SSH keypairs as well as symlinked...
  13. TASK ERROR: Failed to run vncproxy.

    Thank you for your reply! Looks like those files are not symlinked: root@proxmox1:/etc/pve/priv# ls -alh total 2.5K 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...
  14. TASK ERROR: Failed to run vncproxy.

    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...
  15. TASK ERROR: Failed to run vncproxy.

    I added some verbosity as it only showed: root@proxmox1:~/.ssh# /usr/bin/ssh -e none -T -o BatchMode=yes 192.168.1.5 /usr/sbin/qm vncproxy 104 Permission denied (publickey). root@proxmox1:~# /usr/bin/ssh -v -e none -T -o BatchMode=yes 192.168.1.5 /usr/sbin/qm vncproxy 104 OpenSSH_7.4p1...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!