Oh! No! My AMD GPU dataland RX460  passthough failure in ubuntu, centos and macos.

Show the same log：

2019-10-31T13:49:52.289412Z qemu-system-x86_64: vfio_err_notifier_handler(0000:03:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest
2019-10-31T13:49:52.289500Z qemu-system-x86_64: vfio_err_notifier_handler(0000:03:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest

 

@Young_Max see here 

 

10 hours ago, Young_Max said:

I have a little question, how to @ someone, I'm not familiar with this , thank you

Press the @ key and then start to type the person's user name. When you have entered enough you will be able to choose it from a floating menu that appears.

5 hours ago, Young_Max said:

I have the same problem. Have you solved it？

The solutions to most of your problems are in this thread. Try updating the docker container.

HAHAHA I'm stupid 

12 hours ago, Leoyzen said:

@Young_Max see here 

 

Change RX460 to the first slot ，but my second slot only pcie 3.0 x4, how much this would affect my other graphics card, the gtx1060

@Young_Max Benchmark yourself to see the difference. I have no idea how much it is.

@Leoyzen Thanks ， I will try it

Edited November 1, 20196 yr by Young_Max

@Leoyzen AMD RX 460 passthough black screen, Is there any solution? Only add 'pci=noaer'. 

 

2019-11-01 06:14:24.178+0000: Domain id=6 is tainted: high-privileges
2019-11-01 06:14:24.178+0000: Domain id=6 is tainted: custom-argv
2019-11-01 06:14:24.178+0000: Domain id=6 is tainted: host-cpu
char device redirected to /dev/pts/2 (label charserial0)

 

@Young_MaxThe log is normal.

Just add latest Lilu and WEG to make your graphic work, there is no relation between "pci=noaer" and your black screen.

You can read this post first.

 

23 hours ago, ghost82 said:

It means your processor doesn't support that args, so you can delete them from the vm xml (xsave, avx, xsaveopt): I don't know if that args have important impacts on your vm; anyway these are "warnings", so if your vm performs well, you can delete them, as I explained, from the xml, your vm will run the same as now and the warnings will disappear.

Ah thanks! It seems to be performing better now without the arguments present.

but now looks like i had other error messages
 

2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: high-privileges
2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: custom-argv
2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
usb_desc_get_descriptor: 1 unknown type 33 (len 10)
usb_desc_get_descriptor: 1 unknown type 33 (len 10)

think this might be do do with bios settings on the r710 from what google said,
 

Quote

enter the BIOS setup and enable "SR_IOV Global Enable" option under "Integrated Devices".

thaqnks for the help

1 hour ago, MDHMatt said:

2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: high-privileges

2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: custom-argv

2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: host-cpu

If I'm not wrong there's nothing bad in that three notices, it means that kvm/qemu is started with a not standard configuration.

Edited November 1, 20196 yr by ghost82

@SpaceInvaderOne Can I customize this file clover.qcow2? Or are there other sources of access？I want to custom clover

23 minutes ago, Young_Max said:

@SpaceInvaderOne Can I customize this file clover.qcow2? Or are there other sources of access？I want to custom clover

Boot into VM using it. Mount it in Mac and use your favorite tool to configure it. I do most of my work with clover configurator.

1 minute ago, david279 said:

Boot into VM using it. Mount it in Mac and use your favorite tool to configure it. I do most of my work with clover configurator.

I know, but I want to custom clover.qcow2. Do you have some idea?

1 minute ago, Young_Max said:

I know, but I want to custom clover.qcow2. Do you have some idea?

Boot up the VM. When in the VM mount the efi partition. You can use clover configurator to mount the efi. Go into the efi partition and edit the config.plist using clover configurator. Thats how you edit clover. You might want to make a backup of the qcow2 file just in case you break something. 

2 minutes ago, david279 said:

Boot up the VM. When in the VM mount the efi partition. You can use clover configurator to mount the efi. Go into the efi partition and edit the config.plist using clover configurator. Thats how you edit clover. You might want to make a backup of the qcow2 file just in case you break something. 

Yes, after configuring clover file, backup it into clover. qcow2 file. Is this all right?

Just now, Young_Max said:

Yes, after configuring clover file, backup it into clover. qcow2 file. Is this all right?

I would backup the qcow2 file before even booting the VM. That way if you mess it up you can just go back to the original.

5 minutes ago, david279 said:

I would backup the qcow2 file before even booting the VM. That way if you mess it up you can just go back to the original.

Sorry, what do you mean？The custom clover has been saved clover.qcow2? 

@SpaceInvaderOne Not sure if i read over it somewhere , but what exactly is custom about the 2 ovmf files ? Is it just the unraid 3.1 version but with preset screen resolution or is there more modified ? 

 

Second (not specific to this docker), when i use vnc the 1920x1080 works fine and i see all boot logs ungarbled , but when i replace it with my vega 56 , its all garbled after the initial clover boot disk selection part. Tried changing the resolution on clover side and bios side to 2560x1440, but cant seem to get it to work so i can read the debug logs. Is there a limit in the bios to only be able to use 1920x1080 during boot or can it also work in a different resolution with connected monitor/gpu.  (due to the reset bug its not easy to just test all combination as have to reboot the whole server everytime, but a few tries failed so before i spend 5 days trying all combos i thought i would ask how you do it)

 

Tnx again for the cool docker.

Edited November 1, 20196 yr by glennv

6 minutes ago, glennv said:

@SpaceInvaderOne Not sure if i read over it somewhere , but what exactly is custom about the 2 ovmf files ? Is it just the unraid 3.1 version but with preset screen resolution or is there more modified ? 

 

Second, when i use vnc the 1920x1080 works fine and i see all boot logs ungarbled , but when i replace it with my vega 56 , its all garbled after the initial clover boot disk selection part. Tried changing the resolution on clover side and bios side to 2560x1440, but cant seem to get it to work so i can read the debug logs. Is there a limit in the bios to only be able to use 1920x1080 during boot or can it also work in a different resolution with connected monitor/gpu.  (due to the reset bug its not easy to just test all combination as have to reboot the whole server everytime, but a few tries failed so before i spend 5 days trying all combos i thought i would ask how you do it)

 

Tnx again for the cool docker.

Not running this docker but i have been using mac vms for a while now and i keep VNC and GPU versions of my Mac VMs. Testing things in a VNC vm is a lot safer with the reset bugs. I run 1440p myself and i set the bios at 1440p and just keep the clover resolution at 1080p, the apple logo is a bit garbled at boot but the resolution clears up before the desktop shows up. Make sure you use updated Lilu and Whatevergreen kext too. It helps with the GPU.

15 minutes ago, david279 said:

Not running this docker but i have been using mac vms for a while now and i keep VNC and GPU versions of my Mac VMs. Testing things in a VNC vm is a lot safer with the reset bugs. I run 1440p myself and i set the bios at 1440p and just keep the clover resolution at 1080p, the apple logo is a bit garbled at boot but the resolution clears up before the desktop shows up. Make sure you use updated Lilu and Whatevergreen kext too. It helps with the GPU.

Tnx, yeah that second question was not specific to this docker (just played with this docker for fun to see if it behaves different to my exsiting OSX VM's). Will try and play with it by just changing the bios rez. Already had just created 2 identical VM tempates pointing to the same vdisks etc, one with VNC and one with GPU so i can play and experiment without every time having to boot the server. 

 

edit: just changed only the bios to 2560x1440p and it worked. Not sure what i did wrong the last time. Tnx 

Edited November 1, 20196 yr by glennv

may a question what this error means when i want to remove the vm

 

 

as it was a nice test with macos but really doesnt fit here with no rdp solution i d like to remove the vm.

I'm running Catalina I get it it to work no issue unless I try to passthough my Vega 64

Here's my XML and error code

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacinaboxCatalina</name>
  <uuid>d8007f5a-4f30-4f7d-a330-6084f401f8a1</uuid>
  <description>MacOS Catalina</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="/mnt/user/domains/MacinaboxCatalina/icon/catalina.png" os="Catalina"/>
  </metadata>
  <memory unit='KiB'>32505856</memory>
  <currentMemory unit='KiB'>32505856</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='4'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='5'/>
    <vcpupin vcpu='4' cpuset='2'/>
    <vcpupin vcpu='5' cpuset='6'/>
    <vcpupin vcpu='6' cpuset='3'/>
    <vcpupin vcpu='7' cpuset='7'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/d8007f5a-4f30-4f7d-a330-6084f401f8a1_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'/>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <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='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Clover.qcow2'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Catalina-install.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/macos_disk.img'/>
      <target dev='hde' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <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'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:b6:3b:64'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x28' 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='0x28' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0x0a5b'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0781'/>
        <product id='0x5596'/>
      </source>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0d8c'/>
        <product id='0x0005'/>
      </source>
      <address type='usb' bus='0' port='4'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1b1c'/>
        <product id='0x0c09'/>
      </source>
      <address type='usb' bus='0' port='5'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x264a'/>
        <product id='0x1fa5'/>
      </source>
      <address type='usb' bus='0' port='6'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
  </qemu:commandline>
</domain>
 

 

heres the error 

 

 

internal error: process exited while connecting to monitor: 2019-11-01T17:59:00.116312Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2019-11-01T17:59:00.117124Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2019-11-01T17:59:00.117952Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2019-11-01T17:59:00.118800Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2019-11-01T17:59:00.119605Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2019-11-01T17:59:00.120768Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2019-11-01T17:59:00.121598Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]

Edited November 1, 20196 yr by Xylter
Fixed the osk key issue sorry about that

4 hours ago, alturismo said:

i d like to remove the vm.

It's covered in the video, near the end. There's an nvram file defined and you have to undefine it before you can remove the VM.