rpowers Posted August 29, 2017 Share Posted August 29, 2017 Hi, I'm changing my GPU from an Asus Radeon to an Nvidia card for my Windows 10 VM. Everything seem to go well, it recognizes and I can select the card in the VM settings but when I start the VM it gives me a DVI - No Signal on the monitor. I should note that I can see the unraid boot sequence on the monitor when I boot up but when I start the VM the monitor turns off. I'm not sure what to do from here. I've attached my logs, do you need anything else? Thanks in advance, Ryan tower-diagnostics-20170829-1722.zip Quote Link to comment
SSD Posted August 29, 2017 Share Posted August 29, 2017 Did you specify the ROM file in your XML? I have that exact config and works great. Quote Link to comment
rpowers Posted August 30, 2017 Author Share Posted August 30, 2017 (edited) Hi, I'm not sure what's happened. I tried to use VNC Remote I briefly shows boot failed then goes to UEFI Interactive Shell. I've tried typing exit then continue but the same thing happens. Ryan. Edited August 30, 2017 by rpowers Quote Link to comment
rpowers Posted August 30, 2017 Author Share Posted August 30, 2017 As an update, I changed to SeaBIOS but now when I use VNC I get a Not a Bootable Disk error. Any help would be appreciated. Here is my XML in case it helps: <domain type='kvm'> <name>Windows 10</name> <uuid>466957b5-0559-f51d-8fd2-465d9c99de13</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' threads='1'/> </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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.118.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ba:4d:02'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='4'/> </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='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <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> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x070f'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc22d'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0xa070'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Ryan. Quote Link to comment
itimpi Posted August 30, 2017 Share Posted August 30, 2017 You cannot change the BIOS type after the initial OS installation. If you want to change the BIOS type you have to do it at initial VM creation time and then install the OS you want as the BIOS type affects the way the OS installs itself. Quote Link to comment
rpowers Posted August 30, 2017 Author Share Posted August 30, 2017 Hi, I selected the OS install iso and it then launched VNC. It is now going through the Windows setup but the following is happening: I select browse then navigate to "CD Drive (E:) virtio-win-0.1.1" then "viostor" then "w10" (also tried 8.1) then I select "amd64" and I press OK. This shows a driver in the list but when I select next it processes for a sec then an error message pops up saying "No new device drivers were found. Make sure the installation media contains the correct drivers, then click OK." Thanks, Ryan. Quote Link to comment
rpowers Posted August 30, 2017 Author Share Posted August 30, 2017 (edited) I'm going to start again based on what I've read from others with a similar problem. I'll download the latest windows iso and virtio drivers and see what happens. All II wanted was a quieter gpu without all of this nonsense. Should have stayed with AMD I guess. Edited August 30, 2017 by rpowers Quote Link to comment
SSD Posted August 30, 2017 Share Posted August 30, 2017 21 hours ago, rpowers said: Hi, I'm not sure what's happened. I tried to use VNC Remote I briefly shows boot failed then goes to UEFI Interactive Shell. I've tried typing exit then continue but the same thing happens. Ryan. Did you follow the instructions from these 3 videos from SpaceInvader One? https://www.youtube.com/watch?v=miYUGWq6l24 https://www.youtube.com/watch?v=A2dkrFKPOyw https://www.youtube.com/watch?v=mM7ntkiUoPk Quote Link to comment
rpowers Posted August 31, 2017 Author Share Posted August 31, 2017 Hi, I've managed to get Windows installed by using the latest version of Windows and Virtio drivers. I looked at the video regarding passing through an Nvidia card and decided not to bother. I'll return the card and get a quieter Radeon card. My old card works again (albeit noisily). Thanks for the help! Ryan. Quote Link to comment
SSD Posted August 31, 2017 Share Posted August 31, 2017 The pass through of the nvidia card is not difficult. I had issues with an AMD card drivers, and much prefer the nvidia. First, with no drivers installed, the AMD card did not function at all. So installing the drivers required a remote connection (I used splashtop desktop but vnc might also work). And second, the AMD driver install crashed, and although the card worked, I was unsure what didn't install. YMMV, but I returned my AMD card ahs kept the nvidia. What is daunting about follow the instructions? Took me only a short time. I can share my ROM file if we have the same card. I have the EVGA 1050TI SC. Quote Link to comment
rpowers Posted August 31, 2017 Author Share Posted August 31, 2017 Ok, well I was able to edit the ROM file no problem. Do I only need to edit the one ROM and then move on to the next step? He edits 2 ROM files in the video and then edits the XML files for both as well. Is this because he has 2 cards installed? Sorry for my lack of knowledge, I'm not well versed in these things and don't like to bother people with questions which are probably obvious to more advanced users. Ryan. Quote Link to comment
SSD Posted August 31, 2017 Share Posted August 31, 2017 If you are passing through just one video card, you only need to concern yourself with one. Quote Link to comment
rpowers Posted August 31, 2017 Author Share Posted August 31, 2017 One more question for you if you don't mind, once I edit the rom file do I change the extension from .rom to .dump? Quote Link to comment
SSD Posted August 31, 2017 Share Posted August 31, 2017 Don't think it matters - when you add the rom file to the XML, you just have to specify the correct extension. Mine has a ".rom" extension. 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.