cat2devnull

Members
  • Posts

    98
  • Joined

  • Last visited

Everything posted by cat2devnull

  1. These are not errors, they are warnings that the CPUs you are passing to the VM don't support the functions represented by bit 16 (FMA4) and 17 (PCID). You see each warning twice because you are passing 2 CPUs. They are not the cause of your issues.
  2. The thing to keep in mind is that databases are great for storing data and filesystems are great for storing files. It is possible to store files directly in a database but it's efficient. It's much better for the database to hold a pointer to the file location on the filesystem and then additional metadata about the file. So if you create a file directly on the filesystem without going through the NextCloud web or client interface then NextCloud won't know that the file has been added. There may be a way to get NextCloud to scan over the filesystem and add missing files but I don't know how it would handle the missing metadata such as who owns the file, when it was added, etc. If you want to be able to interact NextCloud like a traditional filesystem then install the client software and you won't need the web interface. I have the client software setup on multiple Macs at home so that the Documents directory is actually the NextCloud filesystem. That way anything added to it, is automatically synced across all my machines and the server is backed up remotely.
  3. Hi @EnemyLemon, I'm not trying to be snarky but to use an analogy, what you have said is... "I want to speak Italian but I don't want to have to go to any classes or learn the language." Macinabox is a fantastic solution that lowers the bar to get into Hackintosh but is unavoidably brittle due to the constantly changing environment of hardware, software and MacOS versions. My honest advice to most people who actually want to run MacOS long term is allow yourself the time to build your Hackintosh from scratch using the OpenCore Install Guide. But in your case, if you have managed to get any version of MacOS to boot in a VM then you have already solved 90% of the problem. Getting iMessage to work once you have a booting system is pretty straight forward. Without knowing the exact nature of your issue here is some generic advice that should get you over the line; So the definitive guide for getting iMessage working is from the OpenCore team. Just keep in mind that it was not written with Unraid virtualization in mind so you need to make some adjustments. Step 1: Make sure your interface en0 is "built-in". The only sane way to do this is to move it to bus 0x00 (the internal virtual PCIe bus). You can find more information about how to check and correct it in this post. Don't use the OpenCore technique because this is only necessary if you have physical hardware that you can't just remap in a VM. Step 2: Make sure the MAC address (ROM) of your virtual ethernet card is from a valid range that is in use by Apple in the real world. I use 60:03:08:xx:xx:xx but you can use any Apple range (change the xx to something random). Don't use the Macinabox default. This then needs to be updated in both your VM XML and your EFI config.plist file. Step 3: Generate your own serial number and check it against the Apple Check Coverage page to make sure it is not valid. There is often confusion around the serial number requirement. Contrary to the guide and public opinion, there is no requirement to have a valid serial number. The options are; Valid Purchase date - This means the serial number is real and has been registered to a real machine. If you use it, then many things will break for you and the other user who owns the machine, which is bad and will draw attention to you and the Hackintosh community as a whole, so don't do it. Purchase Date not Validated - This means that it is a valid serial number that has not (yet) been registered as purchased. It may be attached to a machine in the future and then it will break as per above. We’re sorry, but this serial number isn’t valid - The serial number is not real and thus can never be assigned to a real machine. Currently Apple do not check the validity of serial numbers so this is the best option. Of course this could change in the future but for now it works so this is what you should use. The wording of the Dortania guide is just a bit confusing. Now, although Apple don't check the validity of serial numbers, there are things they do check. The serial number is not random, it is calculated via a formula that incorporates the machine model and date of manufacture. So you need to use a tool such as GenSMBIOS to generate an appropriate serial for the type of machine you are virtualizing (use iMacPro1,1 unless you know what you are doing). Make sure to use the matching MLB, SystemProductName, SystemSerialNumber and SystemUUID that GenSMBIOS generates and add to your config.plist So if you step through the OpenCore guide with the above 3 points in mind, you should be able to get iMessage working without any real issues. As for your stretch goal of Airdrop, this can also work but it needs a compatible Broadcom WiFi/Bluetooth card. The gotcha with this is that the WiFi will connect over PCIe but the bluetooth requires a little cable connecting to a spare USB port. Hope this helps.
  4. So my understanding of what these errors are indicating is that the Unraid Linux kernel is trying to request access to the card on bus 0x04 and pass it to the VM. For what ever reason this process is failing. This is either a hardware/firmware issue with the motherboard, PCIe bus, video card or a kernel/QEMU software issue. So just to confirm you have tried the following; - Cold boot - AMD Reset Patch - Pulled the bios from your own card (not downloaded from the internet) - Tried the VM while passing the bios and without - Tried with the card stubbed and not stubbed - Corrected your XML as per my earlier post to include the multifunction section If none of this helped then you have hit all the low hanging fruit. Next things to try... - Can you get the card to work at all? Try and pass the card to a Win10 VM? - Try a more recent virtual machine (I'm using Q35-5.1) - Try a more up to date OVMF (this fixed some weird issues for me) - Try a motherboard bios upgrade (early AMD bioses did have issues with PCIe management) - Try a video card bios upgrade (if there is one available from the card manufacturer, some video card bioses break PCIe passthrough) I see you have 3 video cards in this machine (Nvidia, AMD and iGPU). This in itself can cause problems. - Try switching the video card into different PCIe slot (is it in a slot connected directly to the CPU or via the chipset? Is it the primary display or not?) This is now getting beyond what this thread is intended for. Next step would be to move your request over to the VM ENGINE (KVM) forum. FYI I get how frustrating this type of error can be. I've hit video passthrough faults (this exact error) on three occasions and each one has required a different fix. Hang in there.
  5. These are the lines of interest; 2022-03-20T10:47:08.718811Z qemu-system-x86_64: vfio_err_notifier_handler(0000:04:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest 2022-03-20T10:47:08.718907Z qemu-system-x86_64: vfio_err_notifier_handler(0000:04:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest So QEMU is reporting that it cannot gain access to the video card on bus 0x04. You may be hitting the AMD reset bug. It would be interesting to see if a cold reboot (turn off power at the wall for 5-10 seconds) makes it work temporarily. If so, you may need the AMD Reset Patch which can be installed as an App from the Unraid GUI. Also upgrading to 6.10 RC3 may help with stability as it has some improvements for this. From the release notes: "Added support for gnif/vendor-reset. This simplifies @ich777's AMD Vendor Reset plugin which permits users to get their AMD video cards to reset properly." Also how did you go with all the things I mentioned when we chatted last month? As before if you need more help, you will need to provide more information. - The motherboard, CPU and video card(s) details. - Also the relevant logs from the Unraid OS and VM. - Include a copy of your System Devices (Tools -> System Devices)
  6. Take a look here for a detailed explanation of the tips and tricks to get iMessage etc working. It's not as hard as it sounds. I advise against using any OpenCore plist hacks to make the Mac think the en0 is built-in. You should move it in your VM config to be on bus 0x00 as it would be in a real Mac and you will have less issues. It may not be initialized correctly because it is not a configuration that any Mac natively supports. I know that you can pass options to WhateverGreen to enable display outputs. Your best bet might be to have a bit of a look through their support pages and maybe ask the question on one of there support forums.
  7. No, can't say I've had anything to do with it.
  8. Checked both permissions and scanned the array and cache for filesystem errors. All is good. I installed unBalance and that worked fine to move the files. It's a functional work around but would be nice to have the native system work.
  9. You didn't mention what the actual issue is... What the VM does or doesn't do. Just having a quick look at your config I can see the following; It probably should be; <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/AMDRX580.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev> You need the multifunction option and must put both devices onto the same bus but different functions, as per the real devices. In your case, bus 0x04 function 0x00 and 0x01 to bus 0x05 function 0x00 and 0x01. If still no luck, have a look at my earlier troubleshooting post.
  10. Fair thought, but I have already checked for that. The files in question have never been on the array. To be sure I even checked with; ls -laR /mnt/disk* | grep show1.mkv <- Returns nothing vs ls -laR /mnt/cache | grep show1.mkv <- Returns one file
  11. I will start this issue as I always do, by saying this is probably a PEBKAC issue. I have a pretty standard unraid setup with a cache (SSD) and an array (disks). I have media files that live on a share on the cache (Data) that once I have watched, I copy onto a share (Media) that should exist on the array. I have the Data share's cache set to "prefer" and Media set to "yes". When I copy files from the Data share to the Media share the files go from; /mnt/cache/Data/show1.mkv to /mnt/cache/Media/show1.mkv Then when I run mover (which I believe should move the file to /mnt/diskX/Media/show1.mkv It just spits the following error; Mar 17 11:22:59 NUC move: file: /mnt/cache/Media/show1.mkv Mar 17 11:22:59 NUC move: move_object: /mnt/cache/Media/show1.mkv File exists It looks like it is trying to copy it over itself. Why?
  12. I haven't gone through your config line by line but a couple of issues jumped out; - I don't believe you can pass through a video card and keep your VNC config at the same time. The code you pasted still has the VNC XML but I don't immediately see any iGPU passthrough. It would be helpful to include your System Devices List so we know what iommu group your iGPU is in. - You have your virtual ethernet on bus 0x01 which will break iCloud/iMessage because only bus 0x00 is "built-in" You will find this a good discussion about bus configuration here.
  13. So the short answer to your question is Yes. So you need to carefully follow the Dortania guide Fixing iMessage and other services with OpenCore. There is often confusion around the serial number requirement. Contrary to the guide and public opinion, there is no requirement to have a valid serial number. The options are; Valid Purchase date - This means the serial number is real and has been registered to a real machine. If you use it, then many things will break for you and the other user who owns the machine, which is bad and will draw attention to you and the Hackintosh community as a whole, so don't do it. Purchase Date not Validated - This means that it is a valid serial number that has not (yet) been registered as purchased. It may be attached to a machine in the future and then it will break as per above. We’re sorry, but this serial number isn’t valid - The serial number is not real and thus can never be assigned to a real machine. Currently Apple do not check the validity of serial numbers so this is the best option. Of course this could change in the future but for now it works so this is what you should use. The wording of the Dortania guide is just a bit confusing. Now, although Apple don't check the validity of serial numbers, there are things they do check. The serial number is not random, it is calculated via a formula that incorporates the machine model and date of manufacture. So you need to use a tool such as GenSMBIOS to generate an appropriate serial for the machine you are virtualizing. Make sure to use the matching MLB, SystemProductName, SystemSerialNumber ant SystemUUID that GenSMBIOS generates. There are also many other gotchas to watch out for; 1) The MAC address (ROM) you use in your VM XML template and the OpenCore config.plist must match. 2) The MAC address must be from a valid Apple MAC address range. 3) The en0 interface must be "builtin" to the machine. Macs consider any device connected to PCIe bus 0 to be builtin and anything else to be external. This has been discussed at length by @ghost82. He has also explained how to build your PCIe layout to avoid problems. If you follow the Dortania guide and keep the above in mind then you should be able to get iMessage, working without any issues. I hope this helps... And once you have iMessage working, you can come back and we can help you with Handoff and DRM. 😀
  14. I sound like a broken record... A few people have got things going following the details in one of my earlier posts. If that doesn't work you will need to send us; - The motherboard, CPU and video card(s) details. - Also the relevant logs from the Unraid OS and VM. Also you may need the AMD Reset Patch which can be installed as an App from the Unraid GUI to avoid the AMD Reset Bug.
  15. You should be able to pass through a PCIe USB card pretty easily as long as you stub the card and assign it to the VM. My actual config is included below. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <alias name='FL1100 USB Card'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev>
  16. Save you needing to dig back a few pages, I've covered some of the tips/tricks for getting video card pass through working here; https://forums.unraid.net/topic/84601-support-spaceinvaderone-macinabox/?do=findComment&comment=1094263
  17. So I don't use Macinabox but it seems that the custom ovmf file is missing off your drive. I can't tell you if it is just that it never copied or has ended up in a different location. You could just see if it is somewhere under your appdata/Macinabox folder or just download it. https://github.com/SpaceinvaderOne/Macinabox/tree/master/ovmf The location specified in the VM configuration has to match the location it is stored on your drive and you should be good to go.
  18. Ok, so I'm probably missing something very obvious. I'm trying to upgrade my docker installation of NextCloud. The software via the administration/configuration web interface reports; "Version Nextcloud 21.0.2 A new version is available: Nextcloud 21.0.7" Unraid reports the docker is "up to date". The docker does not appear to pull any new version if I add "latest" or "23.0.0" to the repository line. I'm not sure how I can actually verify what version the docker has. Pulling image: linuxserver/nextcloud:latest IMAGE ID [1890902422]: Pulling from linuxserver/nextcloud. Status: Image is up to date for linuxserver/nextcloud:latest TOTAL DATA PULLED: 0 B Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nextcloud' --net='eth0' --ip='x.x.x.x' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e HOST_HOSTNAME="NUC" -e HOST_CONTAINERNAME="nextcloud" -e 'TCP_PORT_443'='443' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://[IP]:[PORT:443]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/nextcloud-icon.png' -v '/mnt/user/nextcloud/':'/data':'rw' -v '/mnt/user/appdata/nextcloud':'/config':'rw' 'linuxserver/nextcloud:latest' 804408823ce2dce0a3e1838c2c8102875d72be2a962669eb5f658a0f9f48c596 The command finished successfully! So what am I doing wrong???
  19. Snap... as per @ghost82 real Macs don't have VGA ports, the drivers probably don't initialize/enable the port because they don't know it exists.
  20. So it looks like QEMU is having issue with accessing your card (assuming it is on address 04:00.0 and 04:00.1 When trying to debug an issue with passing a video card to the VM there are many things to consider/try. 1) Ensure the card is in its own IOMMU group and not sharing a group with any other hardware. Also ensure that it is stubbed so that the host OS doesn't take control of the card. 2) Ensure your config is correct. Here is an example from my config. My card is on bus 0x12 and I pass it to bus 0x04. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x12' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/Yeston-RX550-4G-LP-D5.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='0x12' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> 3) Try passing the VBIOS The goto place for VBIOS files is TechPowerUp but most people recommend that you rip your own BIOS. Spaceinvader has written some software and made a video that is easy to follow. 4) If it is the primary GPU in the system you will need to prevent the Linux OS from using the virtual frame buffer to display the boot process. So under Main -> Flash you can add video=efifb:off to the Unraid boot option. More details can be found in this blog. If you need more help than this, you will need to provide us more information. - The motherboard, CPU and video card(s) details. - Also the relevant logs from the Unraid OS and VM. Also be aware that weird things can happen when you upgrade Unraid (aka upgrade the host OS kernel). I ran for years without needing to do anything but then after one upgrade I suddenly needed to stub the card. Then another upgrade and I had to pass a VBIOS. Then last upgrade to 6.10.0-rc2 I needed to enable efifb:off. Good Luck!
  21. There are very few single slot cards out there. I've had success with the Yeston RX550. Single slot, <40watt, full hardware encode/decode, modern Baffin core and inexpensive (by today's standards ~$100USD). I did a big post about it here; https://forums.unraid.net/topic/84601-support-spaceinvaderone-macinabox/?do=findComment&comment=1052456 http://www.yeston.net/product/details/234/272 As with ghost82, no issue with DRM once I added unfairgva=1 to the boot options in my config.plist Should be perfect unless you want to do AAA gaming.
  22. You can check for yourself here; https://dortania.github.io/GPU-Buyers-Guide/#a-quick-refresher-with-nvidia-and-web-drivers From what I can see that's a negative because Maxwell support was dropped post High Sierra; https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/nvidia-gpu.html#maxwell-series-gtx-9xx-745-750-ti
  23. If you pass the NVMe device through in its IOMMU group then the hardware is available to the OS. I can see my drive temps via smartctl so any software should be able to do the same.
  24. Some dockers will exit on boot if they can't write to their appdata folder. In my case I'm playing with prometheus and it was behaving this way. So what's the best way to allow the docker access to its appdata files if its using uid=65534(nobody) gid=65534(nobody)? Should I add these to the Unraid server?