Rookie Posted March 15, 2018 Share Posted March 15, 2018 (edited) so I am new to unraid, had it for a little over a week now. I spent four days trying to get a VM up and running and at present I have nothing. I started with Mac OS X...and lets just say I picked a wring starting point, as I've not even gotten one to boot up (high sierra, sierra, or el capitan, in that order.) so I moved on to windows 10. I followed space invaders you tube video and I got it loaded. Next natural progression was to pass though the graphics card (once again followed space invaders video). At lunch I went home to check out my new VM. booted up and started just fine, so I plugged a mouse and a keyboard in and discovered that neither functioned. So remotely logged in and went to device manager just to verify that the graphics card got passed though. Sure enough it was. SO I left the keyboard and mouse plugged in and told the vm to restart, hoping that it would see the mouse and keyboard and work. instead I got a BSOD (attachment 1). I played with it for a while and decided to just return the vm to vnc and not use the graphics card until I could do more research.....still get the BSOD. After making those changes I restarted the server just incase it needed a fresh start (like a newbi I forgot to grab the logs before then, but I do have a screen grab of part of it. (attachment 2)) I am also including my VM XML just in case it helps (attachment 3). Machine: Asus Prime b350-plus Ryzen AM4 AMD Ryzen 5 1600 Nvidia Quadro k2000 (crappy I know but I'm waiting for new GPUs this summer) Windows 10 VM VML.txt Edited March 15, 2018 by Rookie adding xml Quote Link to comment
Rookie Posted March 16, 2018 Author Share Posted March 16, 2018 (edited) So I just spent the last two hours building a new Windows 10 VM from the ground up. I followed the instructions, step by step from space invaders video (The best way to install and setup a windows 10 vm as a daily driver....(youtube.com/watch?v=miYUGWq6l24). literally ever freaking step....to include his optional ones. Just to eliminate any issue. My plan was to make a master VM that I could clone and slowly do stuff with (ie add graphics card etc.). get the whole machine up and running then power it down. For good measure I start the VM one last time just to make sure its good.......BSOD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! @alkiax - just so you can follow LOGs: qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 12018-03-16T01:20:39.131814Z qemu-system-x86_64: warning: guest updated active QHqxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 1qxl_cursor: not implemented: type 12018-03-16T01:25:33.928603Z qemu-system-x86_64: warning: guest updated active QHqxl_cursor: not implemented: type 12018-03-16T01:25:47.443363Z qemu-system-x86_64: warning: guest updated active QH2018-03-16T01:26:00.158278Z qemu-system-x86_64: terminating on signal 15 from pid 20209 (/usr/sbin/libvirtd)2018-03-16 01:26:00.402+0000: shutting down, reason=shutdown2018-03-16 01:29:18.308+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: WOPRLC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=W10VMv2,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-11-W10VMv2/master-key.aes -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/dc622893-eceb-93db-7b10-b7e705a7cb24_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 10,sockets=1,cores=10,threads=1 -uuid dc622893-eceb-93db-7b10-b7e705a7cb24 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-11-W10VMv2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,ad -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-11-W10VMv2/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on2018-03-16 01:29:18.308+0000: Domain id=11 is tainted: high-privileges2018-03-16 01:29:18.308+0000: Domain id=11 is tainted: host-cpu2018-03-16T01:29:18.360431Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)2018-03-16T01:30:58.325390Z qemu-system-x86_64: terminating on signal 15 from pid 20209 (/usr/sbin/libvirtd)2018-03-16 01:30:58.572+0000: shutting down, reason=shutdown2018-03-16 01:31:54.244+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: WOPRLC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=W10VMv2,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-12-W10VMv2/master-key.aes -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/dc622893-eceb-93db-7b10-b7e705a7cb24_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 10,sockets=1,cores=10,threads=1 -uuid dc622893-eceb-93db-7b10-b7e705a7cb24 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-12-W10VMv2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,ad isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-12-W10VMv2/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on2018-03-16 01:31:54.244+0000: Domain id=12 is tainted: high-privileges2018-03-16 01:31:54.244+0000: Domain id=12 is tainted: host-cpu2018-03-16T01:31:54.295574Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)2018-03-16T01:32:32.373526Z qemu-system-x86_64: terminating on signal 15 from pid 20209 (/usr/sbin/libvirtd)2018-03-16 01:32:32.611+0000: shutting down, reason=shutdown XML: <domain type='kvm'> <name>W10VMv2</name> <uuid>dc622893-eceb-93db-7b10-b7e705a7cb24</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/dc622893-eceb-93db-7b10-b7e705a7cb24_VARS-pure-efi.fd</nvram> </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' check='none'> <topology sockets='1' cores='10' 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/isos/W10VMv2/W10VMv2/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/W10VMv2/Windows.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/W10VMv2/virtio-win-0.1.141-1.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:fe:44:73'/> <source bridge='br0'/> <model type='virtio'/> <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='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> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> I'm at a loss..... @gridrunner can you provide any insight. Not having a VM is not an option for me and I fear I'm like to have to get rid of unRAID by weekends end if I can't get something up and running and I'll just have to make the server a PC instead. Edited March 16, 2018 by Rookie adding a friend that might find this info useful Quote Link to comment
Squid Posted March 16, 2018 Share Posted March 16, 2018 Try switching the VM to only use a single core, and start in safe mode (Windows 10 IIRC after 3 times failing to boot will automatically offer you that option) You can see why windows blue screened via it's event viewer (start, type in event) My causes of BSOD's are bad memory. Add a VM to the mix, and you also need to make sure you're running the latest virtio drivers and bios versions for your motherboard Quote Link to comment
Rookie Posted March 16, 2018 Author Share Posted March 16, 2018 (edited) @Squid so BSOD...then it restart and I get this screen (untitled2) once I pick a keyboard I get this (untitled 3) so I choose not to power it off and instead click "trouble shoot" which gives me this (untitled 4). selecting "system restore" give me (untitled 5) selecting "system image recovery" gives me (untitled 6) selecting "Startup Repair" reboots the machine and gives me a screen that says it could repair my pc and lets me either go back into advanced options or just shut down. Command prompt just brings me to the command prompt. I have not option to start in safe mode. I'm currently sitting at the command prompt incase there is a trick I can type here to fix this. Edited March 16, 2018 by Rookie Quote Link to comment
Rookie Posted March 17, 2018 Author Share Posted March 17, 2018 SOLVED!!! So First I want to say I am a little disappointed in the Forum. I've had one reply to my problem and while I do want to thank @Squid for attempting to provide help, I'm a little disappointed that only one person was willing to provide assistance. However thanks to Google, I found the problem. Bottom Line Up Front: Close all your GUIs...then play with VMs So as new user of unRAID, I have been very excited to get thing set up. What that means is, I have a mini-pc at home (it was in charge of my NAS that I left to try unRAID), a Mac Book Pro (still haven't successfully attempted to install Mac OS, however what I discovered might by one of the reasons), a surface pro, and an iPhone. When I was at home I would work on the mac book and the surface to get the server set up, but when I was at work I would bounce between my surface and my iphone when ever I had time. Fast foward a couple of days and you have my previous posts. Late last night I was looking though all my xml files, watching spaceinvaders video's for the 1000th time trying to figure out what I had done wrong, why did my windows vm keep giving me the BSOD. all the while I was cussing at @alkiax for talking me into switching to unRAID. during all of my research I starting coping logs like it was my job. I was monitoring this post waiting for someone to rescue me and I wanted to be capable of providing as much research documents as possible so they could tell me where I went wrong. So at one point I started looking a the logs for the server it self. It was glowing red with errors. So in all my unRAID expertise I went to work...you should start laughing at me now. I am not a programmer...no even a little. I've had no training other than my own fooling around. However if your screen is glowing red and I notice the words "preclear" (not availble in community plug ins) and I happen to now that I recently told the "preclear" plug in to update, well then the obvious solution is there is a problem with preclear. Turns out not some much! Once I removed the plugin the entire log turned red. In addition to seeing preclear a ton I notice another ip address. In a panic I did't pay much attention to the address (if I had I would have noticed quickly that it started with 192.168 which would have told me that it was on my side of the modem). So I stopped all my dockers...screen still red. So I stopped the array....screen still red. Finally I stopped all the plugins, at this point I was sure that I had downloaded something and I was being hacked because the logs where still glowing red and continuing to grow. Once again I called up my buddy @alkiax and at this point I was ready to kill him, what had he gotten me into? So I did what every reasonable person would do, I grabbed a beer and opened Google and started searching. My VM troubles were a thing of the past at this point I wanted to save the server. Then i stumbled across a post where @gridrunner asked a question about a "wrong card token message" which happened to be part of the glowing red error messages going across my log screen. Thankfully @itimpi had responded to gridrunner and told him that "The wrong card token message occurs when you have a browser window still open to the unraid GUI from before the last boot of unRAID." I had two instances up and running! one on my mac...the one that I was trouble shooting with, and one on my surface, the one I was watching the logs with. That got me thinking, I checked my phone, sure enough it was on the GUI and my other PC, the one that I remoted into while at work was on the GUI. With fingers crossed I closed all the GUIs, save one. The one remaining GUI I used to tell the server to reboot and then I closed it as well. Once the server restarted I logged back into the GUI (on just one computer this time) and sure enough the logs where clean. This got me thinking, I wonder if this was the problem with my VMs. One GUI shows they aren't started, one shows they are start and the other shows that I just shut it down. I'm not sure how all the 1's and 0's talk to each other but it was all I could hope for. So today after work, I sat down and built another VM (I had deleted the others at some point last night while the logs where glowing red...becuase one of the scripts glowing read referred to the "VM"). I got ridiculous and made three copies, one of the VM the moment I built it, another after I started to update the drivers from the built in windows ones to the virtio drivers, and another after I had installed splash top desk top. I was a little worried I'd have another crash. But I am proud to report, I have a VM that is up and running! I even managed to play a game on it for a little while. Tomorrow I will take one of the copies and pass though a USB control, and if that works I'll pass though my GPU. 3 Quote Link to comment
CHBMB Posted March 17, 2018 Share Posted March 17, 2018 I'm a little disappointed that only one person was willing to provide assistance. I think that comment is a little off, firstly maybe nobody else had any ideas for you, secondly bear in mind this is support from the community, nobody has any obligation to post, or help anyone. We do so in our free time, without recompense. However, as it seems you think it's an obligation to post to help other. I trust we're going to see you become another one of our prolific posters helping people regularly? I happen to know that gridrunner, who you pinged, has been busy with stuff in real life recently, which rightly so has taken precedence over providing free support on the Unraid forums, meaning he hasn't been seen around so much. Sent from my LG-H815 using Tapatalk 2 Quote Link to comment
landS Posted July 6, 2018 Share Posted July 6, 2018 Thanks @rookie for this followup post as i just ran into the exact same issue on what had been a stable system. Turns out I had a GUI session open in my Android phones Chrome beta tab. We had storms which triggered my ups to shutdown the server When it came back up, I too kept getting the windows failed to boot message when passing though the GPU. Restarting my phone actually allowed the VM to startup as it has for --- well over a year --- trouble free. Quote Link to comment
Rookie Posted August 8, 2018 Author Share Posted August 8, 2018 (edited) On 3/17/2018 at 5:48 AM, CHBMB said: I'm a little disappointed that only one person was willing to provide assistance. I think that comment is a little off, firstly maybe nobody else had any ideas for you, secondly bear in mind this is support from the community, nobody has any obligation to post, or help anyone. We do so in our free time, without recompense. However, as it seems you think it's an obligation to post to help other. I trust we're going to see you become another one of our prolific posters helping people regularly? I happen to know that gridrunner, who you pinged, has been busy with stuff in real life recently, which rightly so has taken precedence over providing free support on the Unraid forums, meaning he hasn't been seen around so much. You are exactly right CHBMB, it was a little off. I was so frustrated with this problem that I was not in my right mind. I would love to offer a better argument but I don't have one. my apologies. Edited August 8, 2018 by Rookie Quote Link to comment
skidaddl3 Posted October 12, 2020 Share Posted October 12, 2020 Unraid 6.8.3 Since it was made available, my Windows 10 Pro version 1909 has been attempting to install either the upgrade to Windows 10 version 2004 with no success, or the automatic updates (where I believe it is failing on the update patch for the Meltdown/Spectre vulnerabilities). I have tried to use the Windows Update Assistant several times. I have downloaded separate ".msu" packages and attempted the same update with the same failure. Please see my server board and cpu (dual cpu) set up: The VM is on a separate "Unassigned Devices" SSD to which I also tried to update the VirtIO drivers from Linux Fedora: The VM has the following configuration: I had more recently reconfigured it not to have my Nvidia GTX660 included as a graphics card, because Windows Driver Manager wasn't starting the driver correctly anyway (probably a UEFI thing) Any suggestions are greatly appreciated. Quote Link to comment
JorgeB Posted October 13, 2020 Share Posted October 13, 2020 7 hours ago, skidaddl3 said: Any suggestions are greatly appreciated. Try doing the update with just one core assigned to the VM. 1 Quote Link to comment
skidaddl3 Posted October 21, 2020 Share Posted October 21, 2020 On 10/13/2020 at 5:30 PM, JorgeB said: Try doing the update with just one core assigned to the VM. It worked. Thank you for the suggestion. Now for Unraid to solve this problem without the need for searching outdated issues. 👍 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.