-
Stuck in shell-loop/BIOS setup of Windows 10 VM
I just got unRAID yesterday and so far my experience has not been great. Since I'm new here, I won't be able to supply you with advanced/hidden logs or stats. All I can provide is text, screenshots and clumsy pictures, because I am not yet familiar with the system, sorry. My goal: Get my previous installation of Windows 10 running as VM from an SSD. My Setup: CPU: Intel® Core™ i5-6400T CPU @ 2.20GHz MB: MSI H170M PRO-VDH (MS-7982) , Version 1.0, American Megatrends Inc., Version 2.C0, BIOS dated: Fri 30 Dec 2016 12:00:00 AM PST unRAID: Unraid OS Basic, 6.10.3 (web GUI), 5.15.46 (local terminal) Disk 1 (Array): TOSHIBA_DT01ACA100_X393ZLDMS - 1 TB (sdc) Disk 2 (Array): WDC_WD5000AAKS-75V0A0_WD-WCAWFA546319 - 500 GB (sdb) Dev 1: SanDisk_SSD_PLUS_480GB_182146800632 (sdd), contains old WIndows 10 GPU: GeForce GTX 760 (rev a1) iGPU: Intel Corporation HD Graphics 530 (rev 06) Yes my setup is old, but that should not stop me from using unRAID. My issues: I configured a VM with the following parameters: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>7a4f06c8-699a-5708-a951-a9441d570601</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7a4f06c8-699a-5708-a951-a9441d570601_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='3' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.221.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/sdd'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='usb' index='0' model='nec-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:59:86:6d'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='de'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Already i can't understand why my graphics card isn't listed. It only displays the VNC option. If i start the VNC session, I end up in a "UEFI Interactive Shell", which I read posts about. However, the common solution of typing "exit" and then selecting a boot option does not work, since all options return immediately to the boot setup or to the UEFI shell. As far as i understand unRAID it took control over the external GPU and now there's no usable GPU left for any VM. If i tell the BIOS to first start the internal GPU, then the external one never gets started and I end up with the same problem but with the internal GPU. In the native BIOS of the machine I set graphics options to "PEG" and to check i hooked up an old VGA-based monitor to the internal GPU and a DP-based monitor to the external GPU. As expected, the DP-monitor shows the unRAID shell and the VGA-monitor is blank but backlit, which tells me that it is receiving a signal. Is every VM bound to an individual GPU? If so, that would be a harsh hardware-requirement which I didn't notice to be listed anywhere. Is unRAID even usable with just one GPU? I read about starting headless, but that is some advanced stuff and there's a chance that I'll lock myself out of the system if the network fails. Maybe I expected something from unRAID which it isn't and a multi-boot service would have been a better choice. I hope that I can make it work, since I'm also interested in NAS and docker-containers. EDIT: This assumes that the GPUs are the culprit of this problem. Maybe it is something entirely else?
jat
Members
-
Joined
-
Last visited