fabiosun

non credo sia importantissimo anzi forse per te si.. ma la parte platforminfo e' un disastro 🙂

ciao Benvenuto metti in firma il tuo sistema, cosi' chi puo' darà un parere più' mirato in generale comunque tra SSD e NVME per il caricamento di sistema non c'e' grossa differenza La maggiore velocità NVME sarà più' evidente se utilizzi applicazioni audio video che fanno uso intensivo dei dischi In generale il boot su un sistema SSD/Nvme di OSX da quando ti compare la scelta del boot loader dura pochi secondi se il pc e' configurato a dovere

I would like to share something that could be useful for Full PCi tab lovers in about my Mac / System Report /PCI from Proxmox shell (this naming for path is for latest 6.2 proxmox VE installation: nano /usr/share/qemu-server/pve-q35-4.0.cfg you will see: GNU nano 3.2 /usr/share/qemu-server/pve-q35-4.0.cfg #[device "ehci"] # driver = "ich9-usb-ehci1" # multifunction = "on" # bus = "pcie.0" # addr = "1d.7" #[device "uhci-1"] # driver = "ich9-usb-uhci1" # multifunction = "on" # bus = "pcie.0" # addr = "1d.0" # masterbus = "ehci.0" # firstport = "0" #[device "uhci-2"] # driver = "ich9-usb-uhci2" # multifunction = "on" # bus = "pcie.0" # addr = "1d.1" # masterbus = "ehci.0" # firstport = "2" #[device "uhci-3"] # driver = "ich9-usb-uhci3" # multifunction = "on" # bus = "pcie.0" # addr = "1d.2" # masterbus = "ehci.0" # firstport = "4" #[device "ehci-2"] # driver = "ich9-usb-ehci2" # multifunction = "on" # bus = "pcie.0" # addr = "1a.7" #[device "uhci-4"] # driver = "ich9-usb-uhci4" # multifunction = "on" # bus = "pcie.0" # addr = "1a.0" # masterbus = "ehci-2.0" # firstport = "0" #[device "uhci-5"] # driver = "ich9-usb-uhci5" # multifunction = "on" # bus = "pcie.0" # addr = "1a.1" # masterbus = "ehci-2.0" # firstport = "2" #[device "uhci-6"] # driver = "ich9-usb-uhci6" # multifunction = "on" # bus = "pcie.0" # addr = "1a.2" # masterbus = "ehci-2.0" # firstport = "4" # FIXME: Remove this audio0 device at the next possible time # see: https://pve.proxmox.com/pipermail/pve-devel/2019-July/038417.html # https://pve.proxmox.com/pipermail/pve-devel/2019-July/038428.html #[device "audio0"] # driver = "ich9-intel-hda" # bus = "pcie.0" # addr = "1b.0" [device "ich9-pcie-port-1"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.0" port = "1" chassis = "1" [device "ich9-pcie-port-2"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.1" port = "2" chassis = "2" [device "ich9-pcie-port-3"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.2" port = "3" chassis = "3" [device "ich9-pcie-port-4"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.3" port = "4" chassis = "4" ## # Example PCIe switch with two downstream ports # #[device "pcie-switch-upstream-port-1"] # driver = "x3130-upstream" # bus = "ich9-pcie-port-4" # addr = "00.0" # #[device "pcie-switch-downstream-port-1-1"] # driver = "xio3130-downstream" # multifunction = "on" # bus = "pcie-switch-upstream-port-1" # addr = "00.0" # port = "1" # chassis = "5" # #[device "pcie-switch-downstream-port-1-2"] # driver = "xio3130-downstream" # multifunction = "on" # bus = "pcie-switch-upstream-port-1" # addr = "00.1" # port = "1" # chassis = "6" [device "pcidmi"] driver = "i82801b11-bridge" bus = "pcie.0" addr = "1e.0" [device "pci.0"] driver = "pci-bridge" bus = "pcidmi" addr = "1.0" chassis_nr = "1" [device "pci.1"] driver = "pci-bridge" bus = "pcidmi" addr = "2.0" chassis_nr = "2" [device "pci.2"] driver = "pci-bridge" bus = "pcidmi" addr = "3.0" chassis_nr = "3" [device "pci.3"] driver = "pci-bridge" bus = "pcidmi" addr = "4.0" chassis_nr = "4" In there I commented many lines (old USB related) , this to have a better and clean situation in PCI device output in app like dpcimanager or Hackintool My tries it is always related to acquire a perfect functionality on internal audio I miss 😉 with this emu vm config I achieve this: so a bunch of EHCI and UHCI device are not loaded anymore in my system..and functionality of it seems to be the same. From picture above you can see some stuff also passed from the pve-q35-4.0.cfg file, I mean QEMU PCI-Pci bridge.. I am trying if is possible to avoid also some of this loading.You see also other stuff (first 6 lines) it seems not present in this file.. Main task/goal could be to inject here some devices we have in our rig? We will see Previous situation without commenting those lines: here less controllers passed..it is a VM I use to test so I pass few devices! DO NOT DO IT IF YOU PASS USB MOUSE OR KEYBOARD OR OTHER DEVICE AS A SINGLE USB IN WEB INTERFACE

If you have windows installed you can use it in my case I use grub bootloader (proxmox) to boot and decide what I want use you have to find a solution for you better for you I mean 👍

@lvtzi would use a smaller drive for proxmox but it is a your choice as advice starts more simple you can and then when you know what are you doing you can go deeper

proxmox start very fast..and when you have your system well calibrated you can start in automatic way also your VM so you click on your power button and you reach your OSX desktop 🙂 for proxmox I have a SSD Samsung 840 Pro in a cheaper external enclosure 🙂 in my test I have had also for proxmox a cheaper laptop 2.5 '' mechanical hd... in my opinion if you do not use 100000000 VM you can use a small disk for proxmox..so you can also backup entirely in a flash..then you can have different disk with different OSX as a real pc/hack/Mac @lvtz have you a working OSX in this system or it is your first experience?

la tua CPU senza quello 0xF01 verrebbe vista come Sconosciuta mettendo quel type ti da il nome Xeon (che e' presente nei veri mac) La tua cpu non e' utilizzata su un vero mac ma e' solo estetica

Hi @lvtz USB controller is integrated on my motherboard and in the main guide I show where I connect my "proxmox" disk. in 1) and 2) question you mix some different subject.. to install Proxmox you have to create an USB Pen (CD/DVD or what you desire) to install it Then you can choose a disk to install Proxmox (proxmox = linux) I have chosen an external USB disk..why? in this way I have all others controller (sata, NVME, and so on to pass to my VM) Best solution is to have your guest OS system in a separate drive from Proxmox disk ie if you have now a working OSX on your system you can use it with only a proper EFI to boot with it.. if you instead install OSX on a file, you can have it on your Proxmox disk..in my opinion it is better to use Proxmox disk only for few things and leave all other OSX separated from it so you need: 1) an USB/CD/DVD for iso installation file 2) boot from this one and from here you have to configure Proxmox (5 minute of your time) 3) in there you choose disk fr proxmox installation (in my case an external disk on back USB) 4) then you can create following the instructions your VM if you have an existing OSX on a separate disk you can try to "pass" that disk..I did for my NVME High Sierra Be prepared to solve different problems..but when you succeed in this task you will be happy 😉

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: ASRock Incorporation FCH SMBus Controller [1849:ffff] Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e] Kernel driver in use: vfio-pci Kernel modules: amdgpu 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 05:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff] Kernel driver in use: xhci_hcd 23:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e] Kernel driver in use: vfio-pci Kernel modules: amdgpu 23:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 25:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff] Kernel driver in use: xhci_hcd 25:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:d102] Kernel modules: snd_hda_intel 43:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01) Subsystem: Phison Electronics Corporation Device [1987:5016] Kernel driver in use: nvme 44:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242] Subsystem: ASMedia Technology Inc. Device [1b21:3242] Kernel driver in use: xhci_hcd 45:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02) Subsystem: ASRock Incorporation AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1849:d107] Kernel driver in use: atlantic Kernel modules: atlantic 48:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486] Kernel driver in use: xhci_hcd 48:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c] Kernel driver in use: xhci_hcd 49:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: ahci Kernel modules: ahci 4a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: ahci Kernel modules: ahci 4b:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01) Subsystem: Phison Electronics Corporation Device [1987:5016] Kernel driver in use: nvme @Driftwoodin my experience you can pass all of these listed above using previous FLR posted Kernel patch It is also possible to have some problem if you use sata or nvme disk (for proxmox installation)..I use ASMedia usb 3.2 type controller for Proxmox so I do not share with proxmox my sata or nvme controller when VM starts, and I pass entire sata/nvme controllers to boot in "vanilla" OSX/Windows VM I would like also to suggest to comment amdgpu,radeon and nouveau lines in blacklist.conf to have a more friendly AMD system (you can run command from this instead to use another pc/device to modify things) if you try..be prepared to solve possible problems 🙂

Se ti vede le usb hai raggiunto il massimo che puoi fare senza avere periferiche thunderbolt. poi se ti vuoi divertire scarica dcpimanager e prova a vedere se vedi qualcosa in pci device non credo ma è inutile in generale in quanto non hai le periferiche

si no 🙂 scherzi a parte io non avevo thubdebolt (periferiche) avevo la tua stessa scheda thunderbolt Ho messo il driver in windows messo sl0 in bios potevo far partire osx anche dalla sua USB e vedevo in ioreg qui da te non mi pare di vedere niente ah chiaramente sempre il thunderbolt attaccato e do per scontato che non sia rotta per prova puoi metterci una penna usb qualsiasi anche usb se la hai e vedi che accade ma se non la registry in windows non credo la vedrai mai il driver fa qualcosa..che se cerchi te lo spiegano bene

si dici che capisci bene ma non mi leggi bene 😛 se non ci attacchi thunderbolt (periferiche non vedrai mai niente in PCI Se ci vedi qualcosa puo' essere ssdt tarocco cmq nel bios delle mie precedenti schede madre x99 ed x299 la scheda andava montata su slot specifico e nel bios in security bisognava mettere SL0 prima di questo la scheda andava attivata in windows altrimenti su osx nisba questo e' quello che so.. poi se posti un ioreg qualcuno lo guarderà 🙂

no da quello che sapevo io senza periferiche non vedi nulla di base servirebbe un IOREG..e gengik84 che te lo controlla ma senza periferiche tb non fai nulla in pratica ssdt serve per fare vedere le periferiche anche dopo che sei partito , a caldo, a fereddo collegandole e scollegandole etc..ma se non le hai che provi?

@Driftwood I asked before post if you want your vm config your lspci -nnk output your modules file your kvm.conf file..and all thing could be useful motherboards are different and you have a radeon which could be more problematic...but solutions could be similar for others controller.. Stay for now with Imacpro1.1 @AllubzV I think did an example to explain that more GPU are possible also in real Mac (and obviously in our hackintosh)

in security level 0 o simile poi la scheda va attivata regolarmente da windows mettendo i suoi driver.. e poi serve il famoso ssdt miracoloso hai periferiche da provare thunderbolt? le usb dovrebbero andare facile

ok a big improvement for me.. trying to solve audio problems I have had an idea to try to pass impassable USB controller in my case they had an id like this: 10:22,148c so I asked @Pavoto compile for me new kernel adding this patch: diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index 308f744393eb..9806bff34b9b 100644 --- a/drivers/pci/quirks.c +++ b/drivers/pci/quirks.c @@ -4999,6 +4999,9 @@ static void quirk_intel_no_flr(struct pci_dev *dev) DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_intel_no_flr); DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_intel_no_flr); +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_intel_no_flr); +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_intel_no_flr); + static void quirk_no_ext_tags(struct pci_dev *pdev) { struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus); -- 2.24.1 He compiled it successfully and I have inserted in my Proxmox now all controller are passed under vfio driver (in my case no need to declare it on vfio.conf or block any drivers) Pavo added this patch in his GitHub . I think this could also be useful to pass other problematic controllers (ie thunderbolt?? ) 🙂 below my passed controller now: 04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 23:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 46:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 46:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c] Kernel driver in use: vfio-pci for now I haven't tested if I have additional problem using this patch.... we are on the bleeding edge..using not tested hardware for our task 😉

allora puo' andare..ma e' un campo abbastanza complesso

@paul lo hai il Thunderbolt header sulla piastra madre? altrimenti per farla funzionare e' un delirio vero... @iCanaroha una Asus Thunderbolt 3 Ex ma se non ha l'header la piastra meglio non pensarci per nulla

@AllubzV yes i think so for internal device..also i have bought a cheaper USB audio device and it has the same problem For your problem try to see if you have your KVM.conf file (MSR related) in my case that was the problem

Hi 1) yes you can use it* 1b) no no clean installation is required 2) if you want to use an exist OSX instalaltion yes, if you use a disk in a virtual file no 3) success dipend from your skill and patience. It is not simple but many users with your same rig (a vanilla Patches supported system) are trying proxmox having less problem with compatibility for app (0 problem) and better gpu performances It is Tricky but it could work 🙂 * you have to pass your disk controller or single disk (SATA, NVME..) To have a detailed answer you have to read all the post here and also in main guide.. you can also check @Pavo GitHub , there you will find a system more similar to yours

@Driftwood if better results are obtained with a VM file disk..they are not accurate (sorry for this 🙂 ) if instead they are achieved with a passed drive or entire controller...are very good almost impossible but very good @iGPUyou can use multiple gpu (not in crossfire or SLI), software like davinci resolve and other have a great benefit with dual gpu system

I have had also before more than 10 pci device passed i do not see big improvement for us backup your main proxmox config files in my case I have updated via shell then I did also a fresh installation with new iso without problems

Hi Paul, this "hole" for audio related part is a bit risky by now. Internal audio of TRX40 mb is bridged (maybe) with usb controller so this for now it is problematic I have bought also a cheap USB sound adapter and also this has problems. Display Port audio from my Nvidia GFX is perfect and I have tested with it audio features ( I am not an audio expert) but I can affirm which Proxmox/osx you can use any plugin without problem if this plugin works well in OSX Proxmox/osx installation is not affected from problem you may have with Vanilla patches method..

@paulthesparkywelcome here yep I did test you said without screen software recording I have 580 tracks as I said in this thread or in the main guide thread 🙂 take a look if you want also in this channel: FYI we have here this system working from first days of February 🙂 so a bit first of Theresa 😛 we did a free guide to build from yourself if you have one 🙂 🙂

@iGPU I monitor my temps with my motherboard led code display in bios there is an option to monitor temps trulyspinach app does not work one kext seems to output a missing cpu Id in verbose