• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Leoyzen

  1. @bonienl @uldiseOk I got it. I haven't noticed that before, but it is quite strange after upgrading 6.10...Maybe some behaviors have been changed as the status of io-waits which makes me feel "different" between 6.9.2 and 6.10. I will stay tuned.
  2. But it is not as much as graph in dashboard. (Average about 10%~15% in htop but 30%~70% in dashboard). I don't think it is about "Medium Load on **single process** (Emby with 35%)"
  3. @uldise I'm not sure it is about iowait..... @-Daedalus I agree. I don't care about IO wait at all....And it is quite annoying when using the dashboard for monitoring. I didn't notice whether it exists before 6.10 releases....
  4. After upgrading to new 6.10 version, everything works fine except the monitoring of dashboard. The screenshots describe the problem: It shows heavy load on cpu but actually it is not. I don't know what's wrong.
  5. Does anyone have problem with 10gb nic card driver? I don't know what happened but kernel panic with my 10g nic and SmallTree8259x.kext(3.8.6) drivers, I can't find any information about it.
  6. I'm back now.Changing my work company almost killed me.Finnally get some time to continue the work. Seems my VM brokes somehow, I have to catch up the latest changes and create the VM again, hope there is no more issues...
  7. @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.
  8. @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.
  9. 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
  10. 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.
  11. @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.
  12. Use the latest one I've uploaded and try again. The earlier version doesn't have support of pcie_no_flr kernel option.
  13. @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
  14. 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
  15. @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>
  16. 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?
  17. Can u make a pull request in git using 0.5.7?I can't boot with 0.5.7
  18. @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.
  19. @MetallusTry add 'video=efifb:off' to your boot-args, also add your graphic to vfio-pci.
  20. @chalbolyNo, it not related to ACPI name. USBInjectAll find the device by vendor_id and device_id.You should check whether your usb controller (8086_8d2d) is supported by USBInjectAll.kext.
  21. @chalbolyDid you passthrough your usb controller using bus 0x0/slot 0xy instead of bus0xy/slot 0x0?