Alex8464

Members
  • Posts

    12
  • Joined

  • Last visited

Alex8464's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hello, I wanted to report back once again. After a long time back and forth thinking I come to the decision to opt for the 6700 XT. I´ve been read many forums around these problems with AMD graphics cards (also the 6000 series). So there are apparently manufacturer specific problems with resetting AMD graphics cards or also known as "AMD Reset Bug". https://forum.level1techs.com/t/6700xt-reset-bug/181814/6 To the background: I have a 5700g as main processor. The internal GPU I cant use for it . So I can't avoid to buy a graphics card, because I want to use Unraid as hypervisor for my Windows VM. Two graphics cards came into the closer selection in terms of price. My requirement was, that I can play the MS Flight Simulator 1440p smoothly in the VM. Basically I came up with the idea to use a 3060 Ti or a 6700 xt. Because of the increased memory of the 6700 XT, my first choice was this graphics card. But now that I have enough experience with AMD graphics cards in combination with Unraid. I changed to the Nvidia camp because of the "Reset Bug" problem. The advantages of DLSS are also advantages that you don't want to miss. Furthermore the quality of the NvEnc encoder seems to be better and offers more picture quality with more performance. I will probably get over the 4 GB less VRam and go for the 3060 TI after careful consideration.
  2. Thank you very much for your reply. I was just wondering because the reset bug is actually an absolute nogo for the VM. However, I see the 6700 xt even a bit ahead of the 3060 TI. Are there already people who have made run it?
  3. Hello Dear Unraid Community, I have a question, because I want to buy a graphics card. What matters to me is the compatibility of the graphics card to be able to pass through to a Windows VM. I would choose between the Geforce 3060 TI and the AMD Radeon 6700XT. Which card is better suited to pass through to Windows? I ask because AMD is affected by the AMD reset bug. Should this still be the case, I would have to go to Geforce. thank you for your answers, Alex
  4. Thank you very much for your help! today i will try this way. I made a small thoughts about the adressing. As you can see, I really try to understand the XML-Startup script. One Question about the alias adress types, can they be assigned as i want? For example I tried differend settings for the Bus and yes it where be assignt in the VM. And also i´ve no idea about the "function=0x0" command. In the end my last hope is that i will work with the SEABIOS installtion. And I forgot to assign a "vendor_id value", Maybe thats the tipping point... Thanks to all! and ofcourse to chaosclarity and Name_0901. You did a good work by explaining everthings 🙂
  5. ofcourse for sure 🙂 <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 11</name> <uuid>6a699403-4459-35c8-01a4-c0c0b1d78598</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>17301504</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='10'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='12'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='14'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/6a699403-4459-35c8-01a4-c0c0b1d78598_VARS-pure-efi-tpm.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='4' 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 11/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 11/Windows11.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.221-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:e0:cc:57'/> <source bridge='br0'/> <target dev='vnet0'/> <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/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 11/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> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <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/disk1/isos/VBIOS/vbios_1638.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>
  6. That sounds very good. So for me, the graphics card seems to be free in any case and I can dedicate myself to the VM settings. Again, I can boot into my Windows VM and connect via RDP. In the hardware overview I can see that the APU is detected. Driver is installed (RADEON) and also the RadeonResetBug is installed. Unfortunately I had already looked at the configuration of the startup script several times and tried to make changes. I don't have deep knowledge for resource addressing. I only know that there is a hardware resource whose values I can't change logically. And then there are addresses to the devices (graphics & Sound-Cards), which are more or less aliases for the VM. These seem to be redirected to the hardware addresses.Right? Here I need a wokshop unfortunately I can't figure out Spaceinvader One's instructions. Okay, I also installed the VM as OVMF. Here are some explanations about that... https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF I think the Windows 10 VM works for you, because you started it as SEABIOS and so without TMP. Windows 11 also requires TMP without Tweak. Maybe you could tell me if you start via the SEABIOS.
  7. I think the release of the internal graphics (APU) does not work properly in most cases correctly. This initiated my consideration in the sense, if a decontrol of the GPU will be engaged. If the boot post freezes and is still displayed on the monitor, then it probably worked. If the boot post hangs and leaves a blinking cursor, then probably not. Let's look together for a solution to support the AMD 5000G CPU family.
  8. Thank you very much for your reply. I give me a second try until i got no dedicatet graphics card
  9. I was able to test this weekend once and followed your instructions. And I am first of all happy to be able to say that I am once again a step further. The Radeon graphics was found in the hardware management and I was able to install the AMD driver. However, I still have one main problem, namely error 43. This means apparently, that not cleanly to dei graphics card was passed. I have also entered the syntax according to the instructions, so that Ubnraid really staret headless and also releases the graphics card. Here I found a problem. Unraid starts clean (headless) but I still see a blinking cursor in the post. Is this an indicator that the graphics card is still in use? I had already read that an image or the last image in the framebuffer of the graphics card is still in use. image which is in the framebuffer of the graphics card freezes on the monitor. The boot post ends with me a graphics card output and does not go far, only the flashing corsor unsettles me. I also have a question about the addresses for the devices. You write that soundcard and graphiccard should get the same bus. I would like to understand which syntax is responsible for which things. i always get confused. one time we have the physical device and another time a "virtual address", so this one i can apparently adjust or/and change myself? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/Win10TV/Cezanne.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> What does the beginning in the line domain mean? and what does the prefix function mean? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> Maybe I can post my settings here once and you can help me. Thank you guys! and thanks for any feedback. Alex
  10. Thank you for this detailed guide. I had the same problem that it didn't work. I'll try it today to see if it works with my Asrock Board and then report back here. Great thing that it works for you!
  11. Hello dear Unraiders I've been running Unraid on my Asrock 550 mITX with Ryzen 5700g (APU) for a few days. I'm also trying to get the APU to work under a Windows VM and wanted to go through a few things here. This is how I started Unraid Headless and already installed the Windows VM. Unfortunately I hadn't had any success with it pass through the APU. So far I have already dissolved the corresponding iommu groupings and the APU graphic card is individually in it´s own single group (Marked by a green spot). Unfortunately I don't get a picture at the HDMI output after the start with the transfer to the graphics. I also linked the V-Bios beforehand. It's not clear to me why the output isn't on the HDMI switch. Maybe I can post my settings and someone can help me.