-
Posts
173 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Leoyzen
-
-
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.
-
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...
- 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.
-
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.
-
On 4/24/2020 at 7:44 PM, ghost82 said:
Hi, anyone knows what is the correct way to update the OVMF firmware in Unraid?
I'm able to compile OVMF from github and I tried the following:
1a- copy edk2/Build/OvmfX64/FV/OVMF.fd to /usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd (renamed)
1b- copy edk2/Build/OvmfX64/FV/OVMF_CODE.fd to /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd (renamed)
1c- copy edk2/Build/OvmfX64/FV/OVMF:VARS.fd to /usr/share/qemu/ovmf-x64/OVMF_VARS-pure-efi.fd (renamed)
The VM doesn't boot
2- copy edk2/Build/OvmfX64/FV/OVMF.fd to /usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd (renamed)
The VM seems ok and it boots
Is it correct to replace only OVMF-pure-efi.fd?
UPDATE: it doesn't seem to be the correct way, since the vm is using the code and vars files...
UPDATE2: partially solved..I needed to check permissions on files, I copied the new OVMF_VARS.fd to /usr/share/qemu/ovmf-x64/ and /etc/libvirt/qemu/nvram; I copied OVMF_CODE.fd to /usr/share/qemu/ovmf-x64/; set permissions 666 to OVMF_VARS.fd in /etc/libvirt/qemu/nvram, 644 to OVMF_VARS.fd and OVMF_CODE.fd in /usr/share/qemu/ovmf-x64/
VM is now pointing pflash at /usr/share/qemu/ovmf-x64/OVMF_CODE.fd and nvram at /etc/libvirt/qemu/nvram/OVMF_VARS.fd
However the NOOPT version doesn't run, also the DEBUG version doesn't run, I'm able to work only with the RELEASE version
I know that probably it is not persistent after a reboot, but I think I know how to make it persistent.
This because sometimes it can be that opencore log to file is broken and I was asked to compile OVMF NOOPT with serial debug.
This was the case of broken AudioDXE driver, only if compiled as DEBUG, as the RELEASE version worked fine.
2nd part: once OVMF is compiled and replaced in Unraid, anyone knows how to work with serial debug?
@Leoyzen ?
Sorry to directly tag you but I know you are more expert in these things and probably you already replaced the Unraid OVMS firmware.
Here the steps to compile edk2 directly from sources in mac os (release build, X64):
git clone https://github.com/tianocore/edk2.git cd edk2 git submodule init git submodule update cp OvmfPkg/OvmfPkgX64.dsc OvmfPkgX64.dsc <-- I had an error of file not found without manually copying it --> cd OvmfPkg ./build.sh -a X64 -t XCODE5 -b RELEASE -p OvmfPkg/OvmfPkgX64.dsc
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
-
6 hours ago, ghost82 said:
Hotkeys don't work for me...
I tried 0.5.6 stable from official acidanthera and also Leoyzen EFI/config 0.5.6 from his github.
The only way to access the boot picker for me is with the esc key.
No luck...
Can this be related to the keyboard itself?
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.
-
@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 hours ago, Critica1Err0r said:
vfio-pci 0000:0c:00.4: not ready 1023ms after FLR; waiting
ive had it appended like this and it still shows the same thing
Use the latest one I've uploaded and try again. The earlier version doesn't have support of pcie_no_flr kernel option.
-
@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
- 1
-
@Critica1Err0rDo you use this kernel?Is your motherboard AMD?
-
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
-
2 hours ago, Critica1Err0r said:
Did you get audio and usb passed through? I have the same board and I'm struggling to get anything working.
This kernel will make it work too.
-
@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>
- 2
-
@chalbolySo, did it work or not?
-
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?
-
13 hours ago, david279 said:
Updated yesterday no problem. Also updated to 0.5.7 opencore too.
Can u make a pull request in git using 0.5.7?I can't boot with 0.5.7
-
@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.
-
@MetallusTry add 'video=efifb:off' to your boot-args, also add your graphic to vfio-pci.
-
@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.
-
@chalbolyDid you passthrough your usb controller using bus 0x0/slot 0xy instead of bus0xy/slot 0x0?
-
@chalbolyNot required. But I'd prefer add it in order to staying the same with standard hackintosh procedure.
-
Finnally got irregular number of cores assignments work. Details can be foud in git issues. I will update the manual and config.plist later.
3-cores/6-threads
<vcpu placement='static' current='6'>8</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no' order='1'/> <vcpu id='1' enabled='yes' hotpluggable='yes' order='2'/> <vcpu id='2' enabled='yes' hotpluggable='yes' order='3'/> <vcpu id='3' enabled='yes' hotpluggable='yes' order='4'/> <vcpu id='4' enabled='yes' hotpluggable='yes' order='5'/> <vcpu id='5' enabled='yes' hotpluggable='yes' order='6'/> <vcpu id='6' enabled='no' hotpluggable='yes'/> <vcpu id='7' enabled='no' hotpluggable='yes'/> </vcpus> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='14'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='15'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='13'/> </cputune> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='2'/> </cpu>
5-cores/5-threads
<vcpu placement='static' current='5'>8</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no' order='1'/> <vcpu id='1' enabled='yes' hotpluggable='yes' order='2'/> <vcpu id='2' enabled='yes' hotpluggable='yes' order='3'/> <vcpu id='3' enabled='yes' hotpluggable='yes' order='4'/> <vcpu id='4' enabled='yes' hotpluggable='yes' order='5'/> <vcpu id='5' enabled='no' hotpluggable='yes'/> <vcpu id='6' enabled='no' hotpluggable='yes'/> <vcpu id='7' enabled='no' hotpluggable='yes'/> </vcpus> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='14'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='15'/> <vcpupin vcpu='4' cpuset='8'/> </cputune> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu>
- 1
- 1
-
-
@fr05tySeems navi/vega reset bug.You can try using the cusotm kernel.
** Hackintosh ** Tips to make a bare metal MacOS
in VM Engine (KVM)
Posted
That seem good, will try later