ghost82

Members
  • Posts

    2049
  • Joined

  • Last visited

  • Days Won

    12

Community Answers

  1. ghost82's post in Home assistant vm wont start after multiple things. need help sorting this out. was marked as the answer   
    See if this helps:
    https://forums.unraid.net/topic/123419-functionnal-vm-wont-boot-anymore-stuck-on-autoboot/
     
  2. ghost82's post in iGPU acceleration for RDP on VM was marked as the answer   
    If you google enable gpu acceleration over rdp you will find solutions for discrete gpu by tweaking the windows registry if I remember well..this could work also for the igpu...or not...
    I know you are now thinking, if you don't know why you reply?
    I would not consider RDP at all for your use, if you passthrough a gpu/igpu you are enabling hardware acceleration, so your apps/games should use hardware acceleration but rdp will render the screen output and it will send it over the network; this is how rdp works, vnc for example works in a different way.
    I would consider parsec or any other protocol studied for game streaming and avoid rdp, and obviously with a passed through gpu/igpu.
  3. ghost82's post in ServerCore VirtIO driver install was marked as the answer   
    modify it manually instead of with the gui.
    Switch to xml view on your vm settings (top right), find the network block, here an example:
    <interface type='bridge'> <mac address='aa:aa:aa:aa:aa:aa'/> <source bridge='br1'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Change model type from virtio or virtio-net to e1000-82545em, save and boot the vm.
     
    Post your diagnostics if you have issues.
  4. ghost82's post in Boot Order Messed Up was marked as the answer   
    https://forums.unraid.net/topic/123300-vm-bios-change/
  5. ghost82's post in Trouble creating new VM from existing Windows 10 disk img was marked as the answer   
    Since you have a dos partition table I think it was a legacy bios installation and not uefi, which requires gpt.
    Moreover the 3 partitions reflect that of a legacy bios installation, system, windows, recovery.
    Simply use seabios to boot that disk, instead of ovmf.
  6. ghost82's post in Random hang on shutdown/reboot if msi enabled on gpu [Windows 11]? was marked as the answer   
    Nevermind, it was a placebo effect, it seemed it didn't crash for several reboots, then it crashed again.
    Thanks to an app to analyze the memory dumps (WhoCrashed) I was able to identify the culprit: it's a driver power failure of my mellanox infiniband card.
    It's a very old card, worked well in windows 7, survived windows 10, but it seems it has issue in windows 11. Luckily I don't use it very much and I can disable the card and unloading the driver (ibbus.sys) before rebooting/shutting down.
  7. ghost82's post in VM won't start after 'vm' update was marked as the answer   
    Change from this:
    <driver name='qemu' type='raw' cache='writeback'/> To this:
    <driver name='qemu' type='qcow2' cache='writeback'/>  
  8. ghost82's post in Glitchy texts and strange lines. Only on GPU-passthrough'd Windows VMs. was marked as the answer   
    I would try to switch from i440fx to q35.
    You can create a new q35-5.1 vm (ovmf) pointing to actual vdisk, so no need to reinstall windows.
  9. ghost82's post in Execution Error Help Please Passing Through Quad Intel 82580 Gigabit Network Card was marked as the answer   
    I would suggest to backup your current unraid usb key and upgrade to the latest 6.10.0 RC3.
    Apply the same boot arg and see if it gets solved, I wouldn't see any reason to not being able to solve this.
    In case of troubles just restore the backup.
  10. ghost82's post in Not being able to passthrough Gigabyte RTX 3060 was marked as the answer   
    Yes, as you can see:
    Mar 3 08:50:30 TheWall kernel: pci 0000:01:00.0: BAR 1: assigned to efifb Mar 3 08:52:02 TheWall kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x4000000000-0x43ffffffff 64bit pref] ... ... BAR 1 is already in use by efifb, so you need to not make it to attach, or detach on the fly.
     
    append initrd=/bzroot video=efifb:off  
    Check also your vbios, best way is to dump from linux, but gpu-z is also fine, the important thing is that you do not download one from internet.
    If dumped with gpu-z remove the header.
  11. ghost82's post in Unraid crashes when Windows VM (AMD GPU passthrough) reboots (sometimes while Start/shutdown) was marked as the answer   
    For example, for this:
    <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev>  
    You have first block with source address 03:00.0
    You have second block with source address 03:00.1
    You have first block with target address 03:00.0
    You have second block with target address 04:00.0
     
    This is wrong.
     
    To fix it, you add multifunction='on' in the first block, and you change in the second block, bus, slot and function, so that it has the same target bus and slot, but different function:
    <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev>  
    Yes
  12. ghost82's post in Atheros AR9280 Wireless Card BAR error was marked as the answer   
    In that discussion, some user is reporting it working with the following mod, try to add custom qemu arg at the bottom of your xml, before </domain>.
    From your picture your pci passthrough should have the alias hostdev1.
     
    ... ... <qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.hostdev1.x-msix-relocation=bar2'/> </qemu:commandline> </domain>  
  13. ghost82's post in Primary RTX 3080 does not appear in the VM's graphic card dropdown (GPU passthrough) was marked as the answer   
    You should have something like this in your bios:
    Advanced/AMD PBS/Enumerate all IOMMU in IVRS
     
    Change that setting (ENABLE IT) and see if all iommu groups are enumerated
     

    (image taken from internet)
     
    As you can see, if it's disabled, only devices attached to the primary cpu die will be mapped.
    If enabled, devices attached to both dies should be enumerated, in fact now, your iommu groups lack some more devices, not only that gpu.
  14. ghost82's post in UNRAID 6.9.2 GTX970 was marked as the answer   
    Yes, exactly what I was asking.
     
    Back to the issue, as I suspected, in your log:
    0000:0a:00.0: BAR 3: assigned to efifb 0a:00.0 is your gpu:
    0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] [1462:3160] Kernel driver in use: vfio-pci  
    Even if attached to vfio at boot, the host is using it for efifb.
     
    In unraid gui go to Main - Boot Device - Flash - Syslinux Configuration, you will see several blocks, one with a green label, that is your predefined boot.
    You need to modify in this block the "append line", by adding video=efifb:off
    For example, for the "unRAID OS" label it becomes:
    append initrd=/bzroot video=efifb:off  
    Reboot unraid and try to start the vm.
     
    IMPORTANT NOTE: when you reboot unraid, unless you are using another gpu for unraid, if your monitor is attached to the gpu you want to passthrough, the screen will freeze, but unraid is not hanging, connect to unraid from an external device and manage unraid remotely.
  15. ghost82's post in Running passed NVME Linux installation as VM was marked as the answer   
    First settings are correct: q35+ovmf (you have fs0 on hd).
    You need to create a custom entry in ovmf.
    Start the vm and press esc to boot into the ovmf bios settings, create a new entry for boot, point it to the efi file, adjust boot order, save and reboot.
     
  16. ghost82's post in Can i use DDR3 vbios for DDR5 gpu? was marked as the answer   
    This is the best choice you have.
     
    Probably it would fail, one of the things to consider when you use a different vbios is to use one with the exact same memory.
  17. ghost82's post in New Windows VM goes to UEFI Interactive Shell was marked as the answer   
    I understood....You need to be fast enough to press any key when the vm boot.
    Once in uefi shell, type exit and press enter, then you will see a message to press any key to boot from the dvd, so press any key and the vm will boot from the iso.
  18. ghost82's post in Unraid 6.9.2 - Windows 10 - NVIDIA 3060Ti GPU passthrough was marked as the answer   
    yes inside windows.
  19. ghost82's post in Radeon RX6600 Graphics name in System Information on Monterey VM and UnRaid 6.9.2 was marked as the answer   
    12.1 was released on 13 december 2021, so it's available.
  20. ghost82's post in [SOLVED] Can't passthrough 980 TI to Win 10 VM was marked as the answer   
    I assume the vm is 'Streaming VM'?
    Set it multifunction:
    <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/NVIDA 980TI dump.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/> </hostdev>  
    Dump your own vbios.
     
    Jan 16 21:15:11 ETHAN-UNRAID kernel: pci 0000:03:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window Probably in use by efifb
     
    --> modify your syslinux config and add in the append line:
    video=efifb:off  
  21. ghost82's post in I need help getting nVidia passthru for windows VM was marked as the answer   
    Correct, just add that bit to existing one and edit the correct "block", that with the green label (unraid with gui in this case); note that unless you have another primary gpu for your unraid, if you use attach vfio at boot, you will have no video output, if this is the case you may consider to boot unraid without gui (?)
     
    You need to add the multifunction to the video portion, that with the source function at 0x00; then you need to change the bus of the audio portion, to be the same as that of the video, and you need to change the function of audio too, so that you have both video and audio on the same bus and slot, but different function.
     
    Correct, no gui for unraid if you attach to vfio at boot, you can try without attaching to vfio at boot, it may work!
    However I'm not sure what happens if you disable efifb, be prepared to have no video output for the unraid gui.
     
     
  22. ghost82's post in Display resolution issues (800x600) with Nvidia 2070s GPU Passthrough was marked as the answer   
    Did you installed the nvidia proprietary drivers?
    Newest drivers allow consumer cards to be used in a vm.
  23. ghost82's post in [Solved]VM stuck in D3 after a while was marked as the answer   
    I think this was the most important thing you did, since you have that errors not on boot, but after a xx amount of time the vm was running, apparently random.
    Anyway, glad that you (hopefully) solved your issue.
  24. ghost82's post in Crashes after attempting GPU pass through. was marked as the answer   
    It seems hardware related, I would investigate ram as a first step.
  25. ghost82's post in Booting into shell after moving HAOS image on Unraid VM was marked as the answer   
    No no no...sorry, just saw the other thread and you must change on vm xml from type raw to type qcow2.
    Everithing will be fixed.