Jump to content

Proxmox VE OSX Guide discussion


fabiosun

Recommended Posts

  • Supervisor
8 hours ago, Driftwood said:

Not getting a Install Mac OS on the OpenCore Boot screen which is really odd. Catalina attempt. both iso's have been uploaded!

conf looks like this:
 

args: -device isa-applesmc,osk="ourhardworkblahblahblah$ smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -cpu Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,check
bios: ovmf
boot: cdn
bootdisk: ide2
cores: 8
cpu: Penryn
efidisk0: local-lvm:vm-100-disk-1,size=4M
ide0: local:iso/macOS86_Catalina.iso,cache=unsafe,size=9G
ide2: local:iso/OpenCore.iso,cache=unsafe
machine: q35
memory: 32000
name: catalina2
net0: vmxnet3=blah:blah:blah:blah,bridge=vmbr0,firewall=1
numa: 0
ostype: other
sata0: local-lvm:vm-100-disk-0,cache=unsafe,size=64G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=blahablahblah...
sockets: 1
vga: vmware
vmgenid: blaha blah blah ....

 

I would like to start from here , to be honest latest post seems to me a bit ungrateful.. I can do a mistake in this...I would like clarify a bit

 

1)

Your problem with 9 Gb full iso..have you read updated part of the guide when we create (@gengik84) new option for VM_Assistant?...I would like also inform you that also nick's site after that updated his site 😉

2)

opencore stuff...If you read always nick's site, maybe you can understand by yourself who discovered that opencore was a better option..overall for initial graphics problem on boot

He forgot to give proper credits for it...and if you read in comment I have remembered him this fact ( I could say also others things but I do not want to polemic more!

3)

all "researches" for understanding boot args part were done in latest December time..from there I have started to test others combinations from Penryn to host CPU and adding some @algrey patches to avoid also in vm initial hang like trx40 users have in "real" hack environment

4)

@PavoGitHub is a great resource for users with a radeon card because he has one and he is trying to resolve annoying reset bug..I have no radeon card (and here we do not ask to send one to solve problems 😛 ). In his GitHub Is also well defined the initial inspiration for his journey in proxmox

5)

this guide is free it is not perfect but it does not hide anything..and if you want you can participate on it with your ideas and your point of you in all aspects you think we can improve (with we I mean you and me in a word community). I appreciate in particular way @iGPUand @AllubzVmessages here

 

No polemic only to clarify things. I am not a hackintosh  Guru and my job is not related to this passion. I hope you understand in a right way this my "clarification" 😉

have a nice day

@Driftwood I quoted you but not for particular problem with you 🙂

 

 

 

  • Like 1
Link to comment
Share on other sites

4 hours ago, fabiosun said:

@Driftwood, @AllubzV take a look to below image..it could solve your missing full ISO icon:

 

1838004626_ScreenShot2020-05-06at08_36_27.png.3680af84c4eed08df57ae3ebc17f540e.png

Thanks fabiosun.  Yeah I did a those arguments & settings first time round. The problem is I tried two full installs - one I originally downloaded from app store with my macbook pro and the other with the VM Assistant but both wouldn't work with OC but did with Clover. The 2gb base DMG did work with OC. Also option 3 on VM Assistant menu return an error for Catalina server querying, where as the VMA command line help variables work. Options 1 HS and 2 for mojave seem to work fine. Maybe (@gengik84) will take a look. Good app though. 

Anyways, I'm in now and analysing devices to pass thru and configs...

BTW I'm very grateful for your guide, Sherlock's guide, Pavos stuff and all the thread members here. It's an amazing resource.

 

Edited by Driftwood
VM Assistant
  • +1 1
Link to comment
Share on other sites

  • Supervisor

@Driftwood

starting from a working full installer (downloaded with Vm assistant or in other ways) is possible to convert rename it in iso with vm assistant tool

you have only to use it as a cd rom image and put that option in vm config when you set full iso disk

basesystem dmg is not a proper iso file so it must used as a normal vm disk with cache=unsafe option.

 

  • Like 1
Link to comment
Share on other sites

When you hit the menu option 3 here in UK it doesn't work. Neither does a python s script I tried so it must be country related. 

The arguments work. Just the menu. Just thought I'd note it for you guys 

 

@fabiosun I want to thankyou for all the amazing work you have provided here. Without this 3970x users would be a bit lost. Awesome work and a helluva lot of gratitude to you. 

  • Thanks 1
Link to comment
Share on other sites

Now I move on to getting Radeon VII working and a m2 NVME. I guess I can use the Proxmox working VM as a template for a more thorough install. I know you cant share VMs to the same drive else it will screw up - each needing a separate drive. So I experimented on a SSD got it working, copied over the vanilla working boot EFI to the main drive with this resource's help and a bit of Nick Sherlock stuff in order to begin all the other stuff like kexts, config plists, etc...

 

I keep reading about different setups & ROMs people are using to pass through for the Radeon VII, what is the most reliable found to date anyone?

Link to comment
Share on other sites

  • Supervisor

@Driftwood

in my knowledge Radeon VII could pass without any rom

always in my knowledge it will be affected from reset bug

so when you restart your OS X vm hangs

 

vm subject

usually i copy my working one

rename it ie from 100 to 101

then I modify 101 an do my test

 

may I ask which motherboard do you have?

  • Like 2
Link to comment
Share on other sites

  • Supervisor

Very curious about your audio FireWire card

in my case the only problem I have is internal and usb audio

nvidia dp audio is perfect instead

@iGPU

to test I have inserted my Asus Tb ex3 card

it is  not detected at all

no group available for it

 

  • Like 1
Link to comment
Share on other sites

  • Supervisor

about (my) internal audio problem:

 

23:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487]

passed as hostpciX: 23:00.4 and dpcimanager app see it as below:

1273462766_ScreenShot2020-05-06at15_35_01.png.19ddca87b7bf9087bdb3dd1e997e3273.png

you can also see here a weird audio device:

08086293E (intel related??)

606354678_ScreenShot2020-05-06at15_36_38.png.1337e86b71f8ab98e892018a9b333d74.png

 

if I do not blacklist  blacklist snd_hda_intel  when I boot on proxmox I see a message snd_hda_intel codec not found.

this message seems related to  starship/matisse HD Audio controller (famous 23:00.4)

So or Proxmox Ve associated internal ALC audio to intel codec..or we should think how to eliminate that weird audio device you can see in pictures above

 

If you have some ideas to share it is welcomed as usual 🙂

 

  • Like 1
Link to comment
Share on other sites

  • Supervisor

@Driftwood about VM Assistant

option 2 is not working also here so it is a common problem(maybe some path are changed)

 

  • fabios-iMac:~ fabio$ /Users/fabio/Desktop/VM_Assistant-2 -dcata
  • fabios-iMac:~ fabio$ /Users/fabio/Desktop/VM_Assistant-2 -dhs
  • fabios-iMac:~ fabio$ /Users/fabio/Desktop/VM_Assistant-2 -dmoja

these are the commands to download full iso installer (Catalina, High Sierra and Mojave)

 

@Gengik84will check as soon he can

 

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

  • Moderators
On 5/5/2020 at 3:52 PM, AllubzV said:

When trying to start the VM with the following config I get


kvm: -device vfio-pci,host=0000:4b:00.0,id=hostpci11,bus=pci.2,addr=0x14: vfio 0000:4b:00.0: failed to open /dev/vfio/60: No such file or directory
TASK ERROR: start failed: QEMU exited with code 1

 

So we have exact same issue.

 

I've been trying to attack this problem on several fronts. I'll have another go tonight. I think the problem is that Linux does not natively support Thunderbolt. A key, I believe is in activating TB for Linux. I tried this 2 days ago (and was going to write about it yesterday when I alluded to the complicated reply), but it didn't work out. I've now got a variation to try out and will report if this works.

 

I've been scouring the Internet for Linux/TB and found this one comment about PCI pipes/tubes not being established until TB is authorized.

 

If I cannot authorize my card, then I'll ask you to try and authorize your un-flashed card. (I'll write in detail how; there are a few tools to install and a couple of odd-ball commands.) If you can then authorize, then I'll know my problem is failure to authorize due to flashed firmware. In which case I'll re-flash my card, authorize and try again to pass-thru TB.

 

In any event, I'll report back later.

Edited by iGPU
Link to comment
Share on other sites

  • Moderators

I'm still having issues with TB: I'll work on more tomorrow.

 

Tonight, the extra DDR4 finally arrived, so total is now 128GB running XMP. I also switched out the Vega 56 for a Radeon VII... so tonight I I ran tests. The Radeon VII benefits from a modified CMMChris kext and DevProperty SoftPowerPlayTable injection (and I disable WEG as it does not play nicely with the Radeon VII---at least on the Z390 buld).

 

GeekBench-4: CPU, OpenCL and Metal

Spoiler

GB4-3970X.jpg.b1aaef98be8a3754ced058cf21f9c22b.jpg

 

GB4-OpenCL.jpg.0a7c66e4c0386a337da386fad1f45411.jpg

 

GB4-Metal.jpg.3ba25fee4d4259fd8ab454e9b917a833.jpg

 

 

 

LuxMark v3.1: GPU and GPU+CPU

Spoiler

LuxMark-GPU.jpg.36ab09c1801a09a59a89653ce2bb99d8.jpg

 

1223099883_LuxMark-CPUGPU.jpg.732de3b6acee44e22b20099f9a3a2d38.jpg

 

 

Cinebench-15

Spoiler

CB15-3970X-RadVII.jpg.b05fa29426ae748160bf8dad3eecf8d9.jpg

 

Cinebench-20

Spoiler

CB20-3970X.jpg.3da108b5f12cfeb9ffb64dceebe490fc.jpg

 

 

Corona

Spoiler

Corona-3970X.jpg.17195ef95ff710033ebe03ff5a0608b2.jpg

 

***

 

Attached is the CMMChris kext file used for the above tests. This kext file also inject AGPM and works with almost all AMD GPUs (see internal info.plist file).

 

And in below Spoiler is OpenCore DeviceProperties code for speeding up the Radeon VII as well as keeping voltages as low as practical. The code also  populates the Syst-Info/PCI section.

 

Do note, however, that the PCIRoot(...) address will need changing for any other mobo. Use Hackintool' to determine for your mobo if different and ProperTree to copy and paste.

Spoiler

			<key>PciRoot(0x1)/Pci(0x1C,0x0)/Pci(0x0,0x0)</key>
			<dict>
				<key>@0,name</key>
				<string>ATY,Adder</string>
				<key>@1,name</key>
				<string>ATY,Adder</string>
				<key>@2,name</key>
				<string>ATY,Adder</string>
				<key>@3,name</key>
				<string>ATY,Adder</string>
				<key>AAPL,slot-name</key>
				<string>Slot-1</string>
				<key>ATY,EFIVersion</key>
				<data>
				MDEuMDAuMzE4MA==
				</data>
				<key>PP_DisablePowerContainment</key>
				<integer>1</integer>
				<key>PP_FuzzyFanControl</key>
				<integer>0</integer>
				<key>PP_PhmSoftPowerPlayTable</key>
				<data>
				wgYLAALCBjQIAACkNQAAfAAJAAAAGkUBRQFFAQAAAAB2
				AAELAAAACQcAAG4EAADMAwAAzAMAAMwDAADoAwAAyQQA
				AG4EAABuBAAANAQAACoDAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAALwCAABmAQAANgEAADYBAAA2AQAAXgEAACYCAABm
				AQAAZgEAAJMAAAAOAQAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAABDgAAAAEBAQEBAQEBAQEBAQEBAAAAAAAAAAAAAAAA
				AAAAAAAAHQAAAJ4HAACeBwAAngcAADMEAACeBwAAMwQA
				AJ4HAAAzBAAATAQAABQAAAAKDwAAKAoAAF8AAABuAAAA
				AgAAAAAAAAABAAAAAQAAAAEAAABfAAAAZAAAAF8AAABk
				AAAAXwAAAGQAAABfAAAAZAAAAF8AAABkAAAAAAAAAAAA
				AAAAAAAAKAMAACgDAAAoAwAA4gIAACgDAADiAgAAKAMA
				AOICAABeAQAAFAAAAMIBAADCAQAAGQAAADIAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAABkAAAAUAAAAGQAAABQAAAAZ
				AAAAFAAAABkAAAAUAAAAGQAAABQAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAwAAAP/v9DkAAAAARQEAAAAAAAAA
				AAAAAAAAAEUBAAAyAAAASgEAAGQAbgBeAHMAcwD/////
				//8AAAAAAAAAAAEAcwAAAAAAAAAAAFQLIAvMEDARJgAA
				AAEBCQAAAAAAAAAAAFuxvz7sUfi+ZRlSPwABCABkO58/
				Ft6lvQAAAAAAAAAAAAAAAAABCAA1Xpo/jzYuPgAAAAAA
				AAAAAAAAAAABCABpb7A/SDMWPQAAAAAAAAAAAAAAAAAB
				CADlYaE/EvdYvQAAAAAAAAAAAAAAAAABAwC1FYM/wt0Z
				PgAAAAAAAAAAAAAAAAABCACGOIY/Dr4wPgAAAAAAAAAA
				AAAAAAABCACDwFo/TaHzPQAAAAAAAAAAAAAAAAIBCAAA
				AAAAAAAAAKRwjT/kFIW/1ecyPwIBAwAAAAAAAAAAAAAA
				AAAAAAAA1ecyPwEBCAAAAIA/AAAAANGR/D4fhSu/Mnd1
				P7wCKANuBFwFCgaTBtUG7QaeBwAAAAAAAAAAAAAAAAAA
				ZgHmAWsC9AJSA8wDbgRuBDYBkAEMAmsCqAL0AlIDzAM2
				AZABDAJrAqgC9AJSA8wDNgEMAjcCawKoAvQCUgPMA14B
				IANMBEwEJgJiArIC+AJmA8ADOATJBGYBxgE3AqgC9AJS
				A8wDbgRmAcYBNwKoAvQCUgPMA24EkwDyAFgB5AEVAqoD
				EwQ0BA4BHAIqAwAAAAAAAAAAAAAJB24EzAPMA8wD6ANu
				BG4ENAQqA8kEAADIACwBYAnwCigDAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAJ4HAQAAAAAAAAIGBlAANAEAAAAAAAAA
				AAAAAACQAZABkAGQAZABkAGQARQAKApUCwoPXwAAAAAC
				AAAAAAAAAAAAAQAAAAAAAFCNlzwK16M7AAAAAOqymDyH
				okA9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAABAAAA
				AAAAAKAAAAAIEAIQGgRMBOgD6APoA+gDAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAACGCyILVAsAAJABkAE4AAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
				AAAAAAAAAAAAAAAAAAA=
				</data>
				<key>device_type</key>
				<string>Display Controller</string>
				<key>hda-gfx</key>
				<string>onboard-2</string>
				<key>model</key>
				<string>Radeon VII 16GB (Vega 20)</string>
				<key>name</key>
				<data>
				QVRZLEFkZGVyUGFyZW50
				</data>
			</dict>

			<key>PciRoot(0x1)/Pci(0x1C,0x0)/Pci(0x0,0x1)</key>
			<dict>
				<key>AAPL,slot-name</key>
				<string>Slot-1</string>
				<key>device_type</key>
				<string>Multimedia Controller</string>
				<key>model</key>
				<string>Radeon VII HDMI Audio (Vega 20)</string>
			</dict>

 

 

RadeonBoost-v1-4.kext.zip

Edited by iGPU
added code and kext
Link to comment
Share on other sites

  • Supervisor

@iGPU

have you tested that Kext in a real applications?

I mean in app like DaVinci Resolve or others?

I my opinion and in our tests it improves Geekbench benchmarks but it has no other real application benefit in using osx with AMD gpu card.

try ie CAndle test benchmark in DaVinci and you will see it is useful or not

Spoiler

Corona test

 

1695966574_ScreenShot2020-05-07at10_52_36.png.332eb4460a9caba1bad38ccf2e8fe099.png

 

  • Like 1
Link to comment
Share on other sites

  • Supervisor
  • Moderators
4 hours ago, fabiosun said:

@iGPUlink posted it is useful for windows to update drivers in it?

it not seems bios related

Or maybe I miss something?

 

 

The new 1.0.0.5 Microcode can be applied to CPU directly via Windows. When AMD updates microcode, the mobo manufacturers will usually update their BIOS at a later date to include this microcode as well as make any changes they see fit (MSI has updated some mobo for X570 style). When the microcode is made available, it can be flashed independently of the BIOS. If later the BIOS is updated to same microcode, then nothing changes with the microcode.

 

It is probably safer to simply wait for manufacturer's updated BIOS. (I've never flashed microcode before.)

Link to comment
Share on other sites

  • Moderators

Modest update on TB.

 

While I still don't have it fleshed out, it does look promising if I can get the 'bridge' portions (addresses 49:00 and 4a:00 passed through), I truly think it will work. The problem is on the Linux/Proxmox side.

 

In the screen shots below of IORegistryExplorer, I used a very modified SSDT to change the USB section and it worked, perfectly generating the USB section. This now shows up in the Sys Info/PCI section as well as in Hackintool. Unfortunately, hot-plugging a USB or TB drive does not yet mount, but this is not surprising since the whole TB tree is not present.

 

 

IORegistryExplorer:

Spoiler

 

Before custom SSDT:

GB-TRX40-D-TR-PCI.jpg.766c50c05c49f9b27ba911207ac9c996.jpg

 

 

With custom SSDT (only for USB section, so starts at DSB2, not usual UPSB):

 

480034873_ScreenShot2020-05-07at12_17_14PM.jpg.5c4727fefccfd9214b8a0f4569a6b214.jpg

 

 

System Information / PCI Section:

Spoiler

59806896_ScreenShot2020-05-07at11_45_22AM.jpg.37614beb32fda949be0190b62078907a.jpg

 

 

Hackintool USB Section:

Spoiler

1128119269_ScreenShot2020-05-07at11_43_01AM.jpg.8f2991268c2e5bff8eb4d4610c32526b.jpg

 

Edited by iGPU
Link to comment
Share on other sites

  • Moderators

I was monitoring Proxmox on a Mac laptop: when running Cinebench 20, there is an expected increase in CPU usage over that during idle stand-by.

 

Idle:

Spoiler

VM-Idle.jpg.78cdc9dba34084d4c35e6ee0f4a68a9f.jpg

 

Cinebench 20:

Spoiler

VM-Cinebench-20-Load.jpg.8a6a129eccf96b24253bc95a6e0b5733.jpg

Edited by iGPU
Link to comment
Share on other sites

On 5/5/2020 at 7:37 PM, AllubzV said:

The difference is  that I am now passing through the entire NVME Controller (43:00.0) rathern than /dev/disk/by-id, which you can see in my previous

post. Perhaps there lies the difference.

 

Good tips in here about finding out the NVME controller device settings.

 

Edited by Driftwood
Link to comment
Share on other sites

  • Supervisor
10 hours ago, iGPU said:

 

The new 1.0.0.5 Microcode can be applied to CPU directly via Windows. When AMD updates microcode, the mobo manufacturers will usually update their BIOS at a later date to include this microcode as well as make any changes they see fit (MSI has updated some mobo for X570 style). When the microcode is made available, it can be flashed independently of the BIOS. If later the BIOS is updated to same microcode, then nothing changes with the microcode.

 

It is probably safer to simply wait for manufacturer's updated BIOS. (I've never flashed microcode before.)


my microcode is 1.0003 patch c

i see some gigabyte /asus mb have 1.0003 patch b

i do not know if this difference could create problem for our task

in my case I have flashed back bios to test

i haven’t see any difference doing this

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.