Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Leoyzen last won the day on March 5

Leoyzen had the most liked content!

Community Reputation

65 Good

1 Follower

About Leoyzen

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

899 profile views
  1. @semaphoreI don't have any Navi cards, so I'm not quite familiar with AMD reset bug.(Instead I have a RX580 and it works fine now). You may asking at Level1Tech vfio forum to see if anyone could help.
  2. @bastl 2020-04-25T15:24:26.974831Z qemu-system-x86_64: vfio: Cannot reset device 0000:23:00.4, depends on group 39 which is not owned. This means there are other devices in the same IOMMU, so you must apply the ACS patch to split them away and then try again.
  3. The replacement is correct, but that did not mean that the "NOOP" nor the "Debug" version of opencore will work ,because from the github, it only for debug purpose, which mean it did not resolve the bug, but the way to get more debug information
  4. I'm not quite sure.I tested it with external usb keyboard(not the one qemu added). It also quite tricky to triger bootpicker, you must enter the key(option/esc) multiple times when the uefi logo appears.
  5. @ghost82Yeah, hotkey works for me both with KVM and m920x.I'm not trying upgrade to the latest opencore until the opencore is stable.The 0.5.7 is quite buggy for me.
  6. Use the latest one I've uploaded and try again. The earlier version doesn't have support of pcie_no_flr kernel option.
  7. @Critica1Err0r Use this one instead. And add your audio id(for example:15b7:5002) to boot-args like this: append pcie_no_flr=15b7:5002 initrd=/bzroot 6.8.3-5.5.8-2.zip
  8. I add a new branch with latest opencore build and kexts. It is not recommanded to update(there still have bugs in latest opencore), so this is for testing purpose. https://github.com/Leoyzen/KVM-Opencore/tree/feature/opencore-0.5.8
  9. @chalbolyIt is quite strange because I may find the root cause but your is working.Maybe you did not truely update to 0.5.7 but using 0.5.6? Also to all: I recommand to switch EFI qcow2/img to usb, this make my bootcamp works(but not work for MacPro7,1, it required no external disk injected.) <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/mnt/user/domains/Catalina/opencore.beta.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='usb'/> <address type='usb' bus='0' port='1'/> </disk>
  10. I found it won't boot when I set Target=83(logging to file), it is strange. Can someone test it and give some feedback?
  11. Can u make a pull request in git using 0.5.7?I can't boot with 0.5.7
  12. @chalbolyWe can't map virtual usb ports now.(I can't find a way to do that like standard usb3 ways).So the bluetooth we passthrough is not recoginized as internal which may cause problem.Try using usb bluetooth instead.