xerox445

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by xerox445

  1. https://obscurus.org/unraid-gpu-passthrough-needed-a-tweak/ This is the fix for when you have done everything properly and you still cant get your VM to boot when passing a GPU through. Took me awhile to find it, but this fixed it right away. We need more guys like phil. If you are out there, thank you!
  2. Adding the XML of the VM: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='3'> <name>Windows 10</name> <uuid>14c11b2e-d6a1-87f1-c9e7-e2834d9b0cdc</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='6'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='8'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='10'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/14c11b2e-d6a1-87f1-c9e7-e2834d9b0cdc_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='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.iso' index='2'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <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/virtio-win-0.1.229-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:3f:7b:c1'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-3-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/rtxa2000.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
  3. Hi, I am also having the same issue with my newly build machine. When I start the VM, it pins one core to 100% and will not launch. I have bound iommu groups 22/23 to vfio at boot already, and went through bios to see if there was any relevant settings that could be causing the issue. I oiginally used seabios for the VM, but have since remade it with OVMF. The VM will launch fine and operate with no issues when VNC only is selected as the graphics card, but I can not get this to boot with the rtx a2000. The log is just full of this, 100s of lines: 2023-03-12T01:28:20.846609Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32188, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846615Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32180, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846621Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32178, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846628Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32170, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846634Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32168, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846640Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32160, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846646Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32158, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846653Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32150, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846659Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32148, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846666Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32140, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846672Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32138, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846679Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32130, 0x0,8) failed: Device or resource busy 2023-03-12T01:28:20.846685Z qemu-system-x86_64: vfio_region_write(0000:06:00.0:region1+0x32128, 0x0,8) failed: Device or resource busy otnas-diagnostics-20230311-2018.zip
  4. I am having an issue with unclean shutdowns with S3 Sleep, I made a separate post about it that got no replies, so I searched and found this thread. Here is the link to my original post if anyone could take a look I would appreciate it.
  5. Hello, I recently configured my server to shut off at 7am in the morning, and turn back on at 7pm. I have it functioning with a combo of a shutdown program within my windows 10 VM I am running, the s3 sleep plugin addon to get the server to shut down, and a WIFI plug/timer to kill power a half hour later at 730, and restore it at 700 pm to turn the server back on. Unfortunately, I can not get unraid to shut down cleanly, and it keeps triggering a parity check when it turns on. The VM I have is on a NVME drive, formatted with unassigned devices not in the array. Is there a command I can or need to add to the s3 sleep addon to get this to function correctly? Keep in mind, I want to do a full shutdown, not a s3 sleep. tower-diagnostics-20210622-1136.zip
  6. This is a really common problem I am seeing, and it seems to never get resolved. As soon as I change the MTU on the unraid side, I can no longer access the GUI via the web browser remotely. I too only get 200-250megs transfer speed with a full 10gbe setup. There is something missing here, and SO many people have this problem unresolved.
  7. Update: So I did this, took the USB drive out of the machine, and remade it with the unraid creation tool. Then moved super.dat and pro.key over to the config folder, and started the server again. After reconfiguring the network card so I could get access to the machine via the network and not just my IDRAC, I am having the same issue. Excuse my ignorance, but how do I get "unraid" involved in this, I paid for a pro license and I need "pro" support.
  8. At this point I would like to just reconfigure the entire server. As far as disk data, everything will stay there? If the share assignments are gone, I dont mind that, i would actually prefer that. I just want to have my data safe, and start fresh at this point.
  9. Same thing happens. Uploaded diag again after I created new share and tried transfer. michelangelo-diagnostics-20200210-0904.zip
  10. drwxrwxrwx 1 nobody users 0 Feb 10 08:22 Disk\ Images/ drwxrwxrwx 1 nobody users 6 Apr 20 2019 Documents/ drwxrwxrwx 1 nobody users 59 Jun 12 2019 Downloads/ drwxrwxrwx 1 nobody users 6 Feb 6 09:42 Games/ drwxrwxrwx 1 nobody users 63 Feb 9 22:58 Media/ drwxrwxrwx 1 nobody users 6 Feb 7 19:47 Podcasts/ drwxrwxrwx 1 nobody users 6 Feb 10 08:39 Test/ drwxrwxrwx 1 nobody users 40 Feb 9 22:41 Tester/ drwxrwxrwx 1 nobody users 6 Feb 9 22:50 Utilities/ drwxrwxrwx 1 nobody users 23 May 18 2019 WindowsVMdisk/ drwxrwxrwx 1 nobody users 76 Nov 3 23:03 appdata/ drwxrwxrwx 1 nobody users 20 Feb 6 09:25 domains/ drwxrwxrwx 1 nobody users 6 Jun 8 2019 isos/ drwxrwxrwx 1 nobody users 18 Nov 3 23:03 syncthing/ drwxrwxrwx 1 nobody users 26 Apr 17 2019 system/ root@Michelangelo:~# I have created a new share already and tried that, same thing. "Test, and Tester" I will do it again now and reply back shortly.
  11. Also, it looks like it puts a copy of the file on the share when you do the transfer even though it errors out and you cancel it, but it is corrupted, nothing is there when you click on it. It has the size and file name, but seems like none of the actual data is behind it.
  12. Thank you, I corrected that, did another transfer, and here are the diags. michelangelo-diagnostics-20200210-0823.zip
  13. Is this the correct syntax? Also, when I stopped the array, it said "retry unmounding disk shares", I had to reboot the system to get the array back up. michelangelo-diagnostics-20200210-0815.zip
  14. I also brought my laptop home, and tried to access the shares the same way I do on my main machine. I get the same thing, I can see all the files and have access to them, but when I go to copy a file from the laptop onto the NAS, it just sits at "calculating", then times out and gives an error.
  15. michelangelo-diagnostics-20200209-2208.zip I attached another diagnostic log file, possibly might show if I made some change that I should not have since I started having this issue. I am really at a loss. Should I look into re installing the whole unraid OS? I dont want to loose my data obviously but I really need to get this fixed, so I can start scheduling jobs for handbrake to convert videos in a VM (hence the reason I upgraded to the 2697 V2s.)
  16. Ok, I was able to copy a avi file that was on disk1 to a user share folder via MC. I did /mnt/disk1/media/movies/21 Jump Street/sample.avi copied to /mnt/user/Disk Images/ The file moved over and i can play it when I open the folders from my windows machine that I am still having problems writing files to. The weird thing is, I can make folders, but as soon as I go to add a file, it will not work.
  17. I am sorry, I am not really a linux guy, can you give me the command to copy a file from one dir to another or something like that so I can check it with the console? I also used Unassigned devices to mount a 500gb m.2 sata, and share it, tried to copy files to that also, gave me the same thing. "Error 0x8007003b: An unexpected network error occurred.
  18. Thanks for the response. I can create a folder from the console. I made the "temp" folder in my Media Share with that command. I can also create a new folder in that same share from my windows 10 machine, I named it temp2; but I still can not copy or move files over to any of the share folders.
  19. Update: The "Docker Safe New Perm" is not included with CA, I had to download the "fix common problems" plugin to get it to show up under the tools tab. Again, I ran that, and nothing changed. Do I need to reboot after running this, (on either side)?
  20. As stated prior, I ran under "Tools" then "New Permissions", both now on "Disks" ALL and "User Shares" ALL. Same thing, I can open any folder and view and read the contents, as soon as I try to move a file over, it just says "calculating" for a few min then gives an error, prompting me to try again, skip, or cancel. Is there something else I am missing here?
  21. Hi all, I recently upgraded some hardware on my server, and since then I have not been able to write anything to my shares. I changed out my 2640 v1 to 2697s v2s, added another sata based 500 gig drive (still in unassigned devices), changed my 4 x 1000 copper onboard nic to a 2 x 10gbe and 2 x 1000 copper nic, and added a rx550 video card. I ran the "new permissions" tool, and under disk selected all, but left user shares none. Not sure if I need to do that also if that could be my problem. Any help would be appreciated. michelangelo-diagnostics-20200207-1641.zip
  22. That was it, I got it working with the SeaBios no problem. Thanks
  23. On unraid 6.6.3, that selection is grayed out when you select windows 10 template, you cant select seabios