Jamntoast

Well although I was able to get the installer to run and it went through the process and reboot, now saying there is no network interface card present and says hit any key to restart, restarting vm after verifying card is all check marked in vm edit, getting same problem on startup of vm, hanging at boot or masks.

Thanks toastman!, that did the trick.

I had a windows 10 vm setup and I was unable to make any changes during edit of vm, it would not save and hang, I thought I would be clever and make changes and then switch to form view and save, it seems to have deleted the vdisk for the vm. I have the domains set to cache only so there was no redundancy with with recycle bin plugin added in. Not a big deal as I created a new vm and edit of the vm is working now. Just wondering if anyone else has had the vdisk go missing on a vm while trying to edit?

I've tired OPNsense with the same failed results, no matter what settings I have seabios or ovmf and I ran through all the q35 and i440fx options, install still hangs seabios it hangs at masks and ovmf it hangs at booting during install. I've ran through a few youtube videos of the setup and I can't seem to figure out what is going wrong as I've gone through step by step of the process the same as instructions.

update- looks like there is a new bios for system board to alleviate issues with some Linux distros, will try this evening after work.

I've been trying to get pfsense installed but the install hangs on booting after the cd loads, I have used the free bsd template and tried seabios and ovmf, I've tried different q-35 versions as well but still can't seem to get the install to go through. I have already passed through an Intel I350 and it is showing in the vm setup under other pci devices and I removed the br0 host as well following spaceinvaders tutorial. unraid is running on Strix B350 with a ryzen 1700x. It seems to load the cd install but hangs just after it starts to load pic attached

When I try to change settings on the VM, W10, and I hit update at bottom, it just stays greyed out and does not apply changes. Trying to switch virtio driver iso. nasp-diagnostics-20200115-1426.zip

Well Just an update, it seems to have sorted itself out, been running for a couple days with no interruption. Not really sure what to pin it on but here's what my system has gone through, upgraded unraid from 6.6.6 to 6.7.2 , problem still seemed persistent after that. Windows feature update on vm to build 1903 and I disabled WDM driver in group policy as I was getting the max core error when vm was idle. I just want to say thanks to everyone who contributed and helped out on troubleshooting this issue and bringing to my attention the fix for WDM driver issue. I had been googling for that error but didn't see that fix in results.

I have disabled them yes, but maybe I need to do it through cmd instead of the power profile. I'll try that as well.

Yes, that's what this appears to be, I did update windows and it did the 1903 feature update. I rolled back unraid to 6.6.6 and same problem with the core maxed at 100%. Thanks for reply, I'll look into disabling wdm. I was able to correct the 100% core issue with disabling the wdm driver. Thanks for the link johnnie.black! Ok, so back down to the original issue, I'm still keeping an eye out for the next time it shuts down to grab the log.

I also have a new problem with the vm since upgrading unraid, when the vm is without vnc or rdp connection one of the cores is at 100%, if I log in with rdp or vnc remote it idles back down.

I don't have it running on a schedule. I'd just rebuild the vm at this point but it has a W10 key I paid for on it and I'm not sure how that would work with the hardware profile and activation. The last time I had used it to install the vm I had to call into M$ to get it working, I'm afraid to get it blacklisted to keep reinstalling. The only schedule I know of is parity check every Tuesday at midnight and move daily at 11am.

I recently upgraded unraid from 6.6.6 to 6.7.2 after my first post thinking it may help. unfortunately I'm not seeing the shutdown in the vm log now. -m 8192 \ -realtime mlock=off \ -smp 6,sockets=1,cores=6,threads=1 \ -uuid 7d86d62d-2bc3-936c-fb52-39cbf1ca757d \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=27,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,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device ahci,id=sata0,bus=pci.0,addr=0x4 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ -drive 'file=/mnt/user/domains/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/isos/Windows10x64.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on \ -device ide-cd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 \ -drive file=/mnt/user/isos/virtio-win-0.1.141.iso,format=raw,if=none,id=drive-sata0-0-1,readonly=on \ -device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1 \ -netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=30 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:72:59:9b,bus=pci.0,addr=0x3 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=31,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=0x8 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-08-12 01:25:25.109+0000: Domain id=2 is tainted: high-privileges 2019-08-12 01:25:25.109+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0)

I don't have anything running like that, I have a few community apps installed,

I attached the diags and a screenshot of array, I have the domains, appdata and system all set to cache only. The vm restarted again but it didn't give me the same readout on the vm log so I was unable to see it in the processes, I'll keep an eye out for the next time. nasp-diagnostics-20190812-0121.zip