oh-tomo Posted March 30, 2019 Share Posted March 30, 2019 (edited) Amidst initial Windows 10 setup of VM over VNC, went to Device Manager and selected Display adapters / Update drivers / Browse to drive E: for virtio-win disk and VNC connection aborted after selecting OK with reconnection refused. update: tried restarting VM which caused it to stop, so restarted VM and went through the Display adapter steps in top paragraph only to end in same VNC connection aborted scenario. Edited March 30, 2019 by oh-tomo Quote Link to comment
Squid Posted March 30, 2019 Share Posted March 30, 2019 Why not use RDP (remote desktop) after the initial setup. Far, far far more efficient at rendering and much closer to feeling like you're working with an actual monitor Quote Link to comment
oh-tomo Posted March 30, 2019 Author Share Posted March 30, 2019 48 minutes ago, Squid said: Why not use RDP (remote desktop) after the initial setup. Far, far far more efficient at rendering and much closer to feeling like you're working with an actual monitor Installing the virtio-win display driver is triggering the vm to crash -- neither Chicken of the VNC nor the unRAID built-in VNC viewer can log in. Is the crash because I installed my LSI 9300-8i card in the 8x slot where graphics cards usually go and the display driver setup is confused? Quote Link to comment
jbartlett Posted April 1, 2019 Share Posted April 1, 2019 You should be able to novlc into the VM during the bootup process to watch. You can even see the BIOS screen. If you can't even get that, you've got something else going on (bad RAM/drive/corrupted vdrive?) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.