SpaceballOne

Duh... I'm a dolt. I did not notice this nor did i try clicking on it...

Hi, I am having an issue with one of my shares that I use for storing Plex Media. I'm unable to write or make any changes to this folder due to a permissions issue. I've gotten to the point of installing the Fix Common Problems plugin and now i'm trying to run the New Permissions tool. On the Fix Common Problems page, I selected all shares except the one for Plex Media in order to exclude them. Then I go back to Tools > New Permissions and click the start button. And... nothing happens. No popups, no new windows, no notifications.. Nothing. First off - I'm doing this in the Docker-safe way, right? Second - what can i do to get the tool to run? Thanks in advance!

Yeah, it would be cool if the GPU could multi-task, but from other stuff I've come across while getting my unraid rig going I kind of assumed this would be the case. Again thanks for the clear answers!

Oh my gosh, I feel like a moron. How did I not think to try this.. . I wasn't finding much of anything in the google machine, but your two posts give me plenty to look into. Thank you very much! One other item that I'm kind of wondering about.. I have an integrated GPU in my i7 processor that I'm using to handle Plex transcoding. - Is it possible for this GPU to be used for the gaming side of things while also supporting Plex? - Can it handle both tasks simultaneously, or can it only do one at a time? (disregard this question if it's answered within the links you sent)

I was wanting to try to set up a VM for my kids to use to play some games. Not sure if my rig has the horsepower to do what they want, but it's worth a shot before we spend $$ to build a PC or upgrade a laptop. The first hurdle is how to allow them access to the VM without having to go through the Unraid UI. Is there a way to just assign a static IP to a VM so that they get to it? Or is there some other way to do this?

Woohoo! The 64 bit iso did the trick. It looks like I'm up and running. I'm surprised that wasn't mentioned in the video I watched. Perhaps this could be added in one of the manuals or guides? In any case, thanks everyone!

Ok I will try getting the 64-bit iso. I got my iso file from Microsoft, but I did the 32-bit version because I wasn't sure if 64-bit would work, or if I even needed it. Will try again in a few hours, thanks!

That didn't do it either, and for some reason i don't have a "bootx64.efi" file in that directory. I do have one called "bootia32.efi" and I tried running that, but it just went to another command prompt and nothing happened

How would I change the boot index? There isn't an option for this in the VM setup. Would this be in the virtual BIOS?

Thanks for the suggestion. I followed all of your settings and startup, and I'm still not seeing any boot prompt. I think my next step is to try a fresh download of the iso. The only other thing I can think of is that there is something in my BIOS that isn't set correctly. Would anyone happen to know the right settings to do on my Mobo? I have an ASRock B365M Pro4.

Well, I started from scratch again, and I still can't get the VM to get to the 'boot from cd/dvd..' prompt. The only thing i can do is get to the UEFI Shell by clicking 'VNC Remote' here: Restarting the VM has no effect in my UI or in the UEFI Shell. The line referenced above that showed a PCI device (built-in audio) bound to the VM is no longer in my log file, so that has been corrected. As a side note, I do have a docker container with Plex running on my NAS. I did go through the process of setting up QuickSync to handle transcoding, but I have a hard time thinking that this would prevent UnRaid from booting a VM. I'm really stumped here as this behavior does not seem to be something that very many people have run into. Here are my VM Settings: CPU Mode: Host Passthrough (Intel® Core™ i7-9700K) Logical CPUs: CPU7 Initial Memory: 4096 MB Max Memory:4096 MB Machine: i440fx-5.1 BIOS: OVMF Hyper-V: Yes USB Controller: 2.0 (EHCI) OS Install ISO: /mnt/user/isos/Windows 10/Windows.iso OS Install CDRom Bus: IDE VirtIO Drivers ISO: /mnt/user/isos/virtio-win-0.1.190-1.iso VirtIO Drivers CDRom Bus: IDE Primary vDisk Location: Auto /mnt/user/domains/Windows 10/vdisk1.img Primary vDisk Bus: VirtIO Graphics Card: VNC VNC Video Driver: QXL (best) VNC Keyboard: English-United States (en-us) Sound Card: None

I think that I may indeed have bound the audio device. I'm guessing that i should try un-unbinding this for the initial boot/os install, so I'll give that a try a little later. In fact,, I may as well just start from scratch with a new vm..

So I started the machine, and opened the VNC prompt, then tried a reset. The green 'play' icon briefly changes state, but I don't get any other response. The logs say "Cannot reset device.. no available reset mechanism." I'm guessing that the 'press any key...' prompt should show up in the vnc session? Here's the log for the VM, BTW... -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=31,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 virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows 10/Windows.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:03:3b:3f,bus=pci.0,addr=0x3 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=34,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 vfio-pci,host=0000:00:1f.3,id=hostdev0,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-08-13 23:01:36.616+0000: Domain id=9 is tainted: high-privileges 2021-08-13 23:01:36.616+0000: Domain id=9 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2021-08-13T23:01:36.917533Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. 2021-08-13T23:01:36.917607Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism.

Hi all, I've created a Windows 10 VM using the SpaceInvaderOne guide on Youtube. This includes getting the iso file, selecting and installing a VirtIO driver and so on. In all of the videos that I've seen, the VM's go right into the installation of Windows when they start. Mine does not. All I can do is click on the VM icon, and select 'VNC Remote'. When I do this, I get a UEFI Shell window, sticks there and doesn't proceed with the install of Windows. I can interact with this screen, but can't get past it. I typed 'exit' and got to a screen where I was able to select a boot device, but none of them ever got to the point of starting the windows install. I've done lots of searching, and it doesn't seem like this is very common. Any help is appreciated.. Here's my system info: M/B: ASRock B365M Pro4 Version BIOS: American Megatrends Inc. Version P4.40. Dated: 05/29/2020 CPU: Intel® Core™ i7-9700K CPU @ 3.60GHz HVM: Enabled IOMMU: Enabled Cache: 0 KiB, 0 KiB, 0 KiB Memory: 16 GiB DDR4 (max. installable capacity 64 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.10.28-Unraid x86_64 OpenSSL: 1.1.1j

I know that your post is more than a year old, but I can't thank you enough. I've used Plex a long time, but I'm new to Unraid and I barely know anything related to Linux. Your post is so clear and easy to follow that I got this done and working on the first try. My CPU was running at about 40% load on a transcode and now it's at about 3%. Excellent!