mSedek
-
Posts
120 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by mSedek
-
-
On 4/1/2021 at 1:04 PM, pavo said:
This will never work because macOS kernel nor the hypervisor for macOS support AMD-V (SVM) cpu feature. Basically put, anything that uses macOS's hypervisor requires Intel's vmx cpu feature.
Never say never.. say "up until now is not available"... anyways just downloaded genymotion (virtualbox based) and is working like a charm for my android studio high end SENIOR LEVEL development..
-
1 hour ago, Jagadguru said:
Here is my qemu args line:
<qemu:arg value='-cpu'/> <qemu:arg value='IvyBridge,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,+vmx,check'/>
And I am able to run nox player without a problem on my Catalina VM
do you have a ryzen cpu?
-
Nvidia yesterday released a driver that unlocks gpu virtualization so, what do i need to do to share my 2070 super tu multiples vms at the same time??
-
On 3/29/2021 at 9:04 PM, Jagadguru said:
Add +vmx and make sure kvm nested is on. Works for me on Intel.
does not works, as soon as I pass the flag +vmx the network card stops working and also that video seems outdated and over complicated for something that should be overly simple..
anyways, I dont think is something about IF i am able to run nested VMS as I don't have any issue running nested vms in Windows or linux, my problem is with macOS and so my first question remains unaswered
-
Im trying to use the android emulator from Androidstudio as I do develop android apps.. under linux and windows vms I can do it no problem but macos reports "YOUR CPU DES NOT SUPPORT VT-X" Im running my VMs on threadripper..
any tip to make it work? im passing this qemu params
<qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-cpu'/> <qemu:arg value='Skylake-Server,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2'/> </qemu:commandline>
-
-
Have tested so far Ubuntu 18, Ubuntu 20, Linux Mint 20.1, Pop OS! and in every version from time to time the screen blinks, goes black then turns on again after couple of seconds..
the exact same XML works for windows no issues at all and I am also running a 5700XT with macOS no issues at all, also If I run the Linux VMS with the 5700XT no issues at all, only the 2070 super blinks from time to time and only with linux.. meeting apps with video like zoom, meets and telegram seems to exacerbate the issue and it is really annoying, any help?
I am on 6.9.0-rc2 and here is my xml.. dont know what other log I could post
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Devbuntu</name> <uuid>bdb2797b-63ac-2335-661a-b5d0518d3b80</uuid> <description>Development</description> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='26'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='28'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='30'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='32'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='34'/> <vcpupin vcpu='10' cpuset='12'/> <vcpupin vcpu='11' cpuset='36'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/bdb2797b-63ac-2335-661a-b5d0518d3b80_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='6' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <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='raw' cache='writeback'/> <source file='/mnt/user/domains/Devbuntu/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </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'/> </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='pci-root'/> <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='pci' index='3' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='4' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </controller> <controller type='pci' index='5' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </controller> <controller type='pci' index='6' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0d' function='0x0'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:05:ea:9e'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 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='0x21' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/EVGA.RTX2070Super.headerless.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x3'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x1a' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain>
-
6 hours ago, ghost82 said:
No, there isn't.
Java 8 is working for me.
sry couldnt reach out yesterday.. okay maybe they fixed. gonna try it
-
2 minutes ago, giganode said:
before you start complaining later that your system does not boot or anything like that.. If you have the nvidia plugin installed, remove it. Compile with vendor-reset and nvidia support combined.
In case of Java8... did you try this?:
yes Java 8 does installs but theres something about the enviroment and no framework recognizes it
-
1 hour ago, ich777 said:
Basically yes and no.
May I ask if you have already sold your 5700XT? If you don't sold it yet, simply follow the instructions and install the patch and you can shutdown/restart/force stop your VM's and the card will just reset fine.
That's because the 6000 series is not affected by the reset bug, if a 6000 card is not working on OSX this is a whole different story... I think the card that you are using (5700XT) is made for a PC and not for OSX or does it have a sticker on it that it is compatible with OSX? Only because it works on OSX it doesn't mean that it works completely flawlessly and a complete different story is when you are Virtualizing OSX (first because the Apple EULA says that you are allowed to virtualize OSX but only if the host is also on OSX...).
That's the question what you are using the card for, consumer cards are not strictly speaking designed for use in a VM, they are designed for desktop use (you can use it in a VM but who says that you not run into troubles, that's basically the same as I wrote above with OSX and the 5700XT).
If the manufacturer says we don't make a patch for that because it's not intended for that usecase you are out of luck and then such awesome people like gnif comes around and even AMD collaborates with him and try to solve the issue.
There are many other things to consider...
Exactly and that's why I think you should write your frustration somewhere on the AMD forums.
NO, I havent sold my 5700XT yet. my issues are none related to the cards or macOS, my 5700XT works perfect in Catalina and BIG SUR, the problem is that at the moment BIG SUR has no support for JAVA 8 and IF i sell my 5700XT to get a 6800 (which is highly available here in my country) just to have a RESET BUG free experience, then I lose my ability to develop in macOS as 6000 series ONLY works in BIG SUR.. either way im screwed lol..
gonna try the patch and see whats the thing.. I dual monitor one with the 5700XT and macOS and one with ubuntu and a NVIDIA 2070 SUPER (which works FLAWLESS), hope that patch does not cause any issue with my setup
-
1
-
-
2 minutes ago, giganode said:
That has nothing to do with amd!!!!!!!
man it has everything to do with AMD, why would the 6000 series work OTB no reset bug and 5000 series plagged with it??? whos the responsible for a patch??? a firmware level or driver level update?? none of us is an AMD hardware engineer or AMD drivers developer
-
4 minutes ago, giganode said:
big navi is the rx 6000 series. The fix is simply that big navi follows the pcie specifications for flr (function level reset).
language barrier??? in order to boot vms with a 5700xt seamlessly include the vendor-reset to the unraid build.
If you need java 8 and big sur does not work with that choose another os for your work.
AND YES... they helped! They talked a lot with customers and developers.
Polaris cards work with the vendor-reset, aswell as the navi cards.
the "other OS" I use is Catalina.. but 6000 series does not work in catalina
-
21 hours ago, giganode said:
First of all, they did not refuse. Instead gnif and amd had a few conversations and with others on reddit etc. as well..
Secondly they fixed the issue on big navi cards... So they definetly heard what the costumers said.
Can't tell you if or when Big Sur will run with 6000 cards.. @derpuma told me that they is already something in big sur that belongs to big navi..
Nevertheless my 5700xt just runs fine in Big Sur...
my 5700xt runs fine in big sur but big sur DOES NOT works with JAVA 8, I am a java developer and no JAVA 8 = no BIG SUR for me... so I need to be able to reboot my mac VM seamless.. so I solve nothing by selling my 5700XT to get a 6700/6800 and not being able to run JAVA 8 in BIG SUR... my only option for now is to pray for the reset bug to go away..
And no AMD did not help by "fixing" the bug in 6000 series.. they should provide a real solution for ALL the affected cards series(400/500/5000)
-
Does amd series 6000 works only on big sur?.. If not, Id sell my 5700XT, this amd reset but got me almost to the madness.. I need to reboot or restart my mac vm without having to restart the whole server, I got 10 others vms running at the same time with services that I can not stop, but at the same time, I need to work with java 8 and big sur was not working with it.
I dont get whats the problem with AMD, why they refuses to help solve this issue.
-
Does anyone has an issue where you cant update Xcode to the latest?.
that update has been stuck there for some time now
-
8 minutes ago, ich777 said:
I hope you know that this is not a Unraid issue only...
The problem with the patch (gnif/vendor-reset) is that it is not mature enough and has some issues also there are different versions of the patch available on github.
Have you tried to build a custom version for RC2 only takes about 15 minutes and a reboot of the server.
Just be sure to turn off all VM's and Dockers when you are building the images.
EDIT: It's really simple, just read the description and the post that I've linked.
yes I know the fault is not on the unraid side.. will take the time tomorrow and test.
-
1
-
-
7 hours ago, ich777 said:
This should work now please see this post here from @giganode on the Unraid-Kernel-Helper thread (btw you don't have to add the Variable manually anymore it's now in the templat itself just set the gnif/vendor-reset to 'true' and also click on 'Show more...' and at gnif/vendor-reset Branch set it to 'feature/audio_reset'):
Will unraid EVER seamless make the 5000 series work like nvidia does? not adding any flags or wierd stuff but just plug and play our navi? I need at least Catalina as big sur is BIG $h!t with older versions of JAVA so I can not develop there and I already have my 5700XT which i like ...
maybe RC3? im running RC2 and still got the bug and I can not go all bleading edge on unraid (those rare branches and stuff ) as I do my job with my VMS
-
11 hours ago, Shinobi said:
Not sure if it is news anymore, but happened to hear from wendell@level1techs that AMD has fixed the PCI reset bugs in the Big Navi cards.. Radeon 6800 & 6800XT & they seem to work perfectly out of the box in Ubuntu 20.04
Some enthusiastic quotes:😂
"PCI Express reset, 100% "
"My day is perfect! & my excitement is immeasurable!"
"For anybody that is super into VFIO the 6800 or the 6800xt, that's your card"
"AMD has absolutely completely nailed it !just for the PCIE reset issue & other quality of life improvements"
"Best GPU on linux that I have used since the Matrox Millennium 2"
'If having a relatively open GPU, is important to you for the Linux platform, it doesn't get any better than this!"
"I have done intentional crashes, I've injected errors into the platform basically, and the card has been able to recover every single time"
"It is rock solid!"
For those who are stuck with the earlier versions of the cards, gnif@level1techs, has something decent cooking. Like Jesus, gnif, cried to AMD for all of us VFIO-kind & someone from AMD has shown him the light
mm what about 5700XT?
-
On 7/23/2020 at 2:37 PM, djrico20one1 said:
https://github.com/P3R-CO/openrgb-container
This one is now available in community apps it wraps openRGB mentioned above, just got it running on my server, So far I've got Mobo and AIO control, still working on getting the ram and graphics rgb controlIn My case I just want to turn off all the rgb, I install the docker and it wont start..
-
1 minute ago, WeiYanZhen said:
OK, i use the passthroug config you posted,but it's not worked
It's still show the missing GOP issue, I think this error message is opencore or qemu cannot find the GPU?
My vbios is downloaded from the website Techpowerup
I wonder if you have any good ideas, thanks alot?
try all the bios if none of them works use the tool to download the rom from your card.. and do not make changes to the passthrough with multifunction..
-
1 hour ago, WeiYanZhen said:
Thanks for reply, next time i will post the xml like the code.
What do you mean when I don’t have a passthrough GPU?
I have just set the Graphics Card use form view and use the user script to correctly the config, like the pic
I have tried the same situation regardless of whether the ROM BIOS is configured or notAnd the whatevergreen config "adgpmod=pikera" is already set in opencore config.plist
I have tried many opencore configurations related to AMD GPU, all of which came from google search, but it seems to be useless at present
I also tried to use Tools->System Device to block GPU-related IOMMU, but it didn’t work.
And Tried the append the vfio-pci.ids on the syslinux.cfg
kernel /bzimage append vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream,multifunctio vfio-pci.ids=1002:7340,1002:ab38,1002:1479 video=vesafb:off,efifb:off initrd=/bzrootFinally, attach my passthrough xml config again, thx
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox BigSur</name> <uuid>2537655f-133c-4b04-abea-7c4141cfaa6a</uuid> <description>MacOS Big Sur</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="BigSur.png" os="osx"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/2537655f-133c-4b04-abea-7c4141cfaa6a_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <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> <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'/> </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='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </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='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='6' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </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:53:c4:0e'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x03' 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> <rom file='/mnt/user/isos/Sapphire.RX5500XT.8192.191212.rom'/> <address type='pci' domain='0x0000' bus='0x04' 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='0x05' slot='0x00' function='0x0'/> </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='************************'/> <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>
In the xml you posted the video card passthrough didnt show up,
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x28' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/Sapphire.RX5500XT.8192.191212.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </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='0x05' slot='0x00' function='0x1'/> </hostdev>
change your passthrough to this and also
which .rom are you using? get your own or try with others from the same card at tech powerups
-
8 hours ago, steveBBB said:
Just wondering if anyone knows what i need to put in at the end of the xml if i have applied the ryzen patch to opencore?
Gathering i don't need all the cpu features as the patch passes through ryzen features?
Thanks in advance
Yo need to add the "special" apple string if you are using the custom ovmfs
Forgot yo mention before that an xml tag device, the Apple string is a device
-
10 hours ago, WeiYanZhen said:
Does anyone have problems with the pass-through GPU card?
My environment is：
UNRAID: 6.9.0 RC-1
CPU: Ryzen 5 3600
MB: MSI B450M Mortar MAX
GPU: Radeon 5500XT (just one GPU card)
MacOS VM: BigSur, Catalina
Then follow the video of @SpaceInvaderOne to create a new MacOS VM, and finally I can successfully log in to the OS in VNC mode and put in the EFI configuration file.
But when i shutdown the VM and edit the VM setting to passthrough GPU and GPU's audio, it's bring the black screen to me.
When my monitor is black, I can only use the WebGUI on the docker of macinabox to check the situation, and it's will show some error msg.
And at this time, there will be a situation where a CPU core is fully loaded.
I don’t know if it’s the macinabox problem or the opencore problem, because the clover version of macinabox can passthrough GPU normally.Hope someone can help me, or is there a way to go back to the clover version of macinabox, thank you.
First when posting your xml, post it as code here and not as attachment for kindness to those willing to help
second you are not passing through the gpu
Third you need to add to your config.plist vía opencore configurator in the nvram tab a boot arg from the whatevergreen agdpmod=pikera
-
successful install from scratch then used my timemachine to migrate all my apps and data from the old catalina.. thanks @SpaceInvaderOne
-
1
-
passthroug moderboard wi-fi + BT module
in VM Engine (KVM)
Posted
yes, everything works perfectly..