arkan

Hello, I have the same exact issue on my both VMs (Windows and MacOS). The issue only started to happen recently just after I changed my screen. I switched from an DVI 1920x1200 screen to Displayport 2560x1440 screen. Maybe the issue is in the BIOS where maybe the resolution is not correctly detected. I have to check with a VNC screen. Or this is because of an issue with Displayport. I've seen some threads with that already(not on this forum).

Hello guys, I wanted to give a quick update about all the questions i've been asking previously. About the Docker issue, I've not been able to fix it, so I created a Linux VM with only Docker in it, and it works perfectly Regarding the sound issue, I was using a USB sound card, and I wasn't passing an entire USB controller. I did it and it solved all the glitches. Thanks again for all your help

Thanks! I missed the video. I'll check this out

Hello, I tried to run the VM by changing the CPU type in the XML from Penryn to host, and newer types, but OSX refused to load in all the scenarios. Any clue?

Hey guys, In the OSX VM running on top on unRAID, I'm trying to install Docker. It refuses to install with the following error: "Incompatible CPU detected" Apparently the CPU appears to lack some instructions or capabilities. Any idea?

Thanks @Thingi On my side I have sound, but it's choppy with some pauses every few seconds. This is really annoying and the microphone is barely usable because of this .... I'm wondering if this is not related to the Qemu bug which fails to properly detect the frequency. What do you think @gridrunner?

@elmn8r : I think I already got this issue which was caused by an invalid CPU. I had to tweak the XML to make it works. <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <resource> [...] <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </cpu> [...] <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline>

Hey Gridrunner, Thanks for the reply. I solved the issue by upgrading the nVidia driver to the latest available one: https://images.nvidia.com/mac/pkg/378/WebDriver-378.05.05.05f01.pkg So now "almost" everything is working properly. The last issue is the sound. I have tested 3 different ways to have sound which where: - USB SoundCard - Bluetooth headset - Splashtop sound driver All of these solutions suffered from noice crackling/stops for a few milliseconds. I also noticed having the similar issue(less noticeable though) on my Windows Gaming Rig also running on unRaid. I haven't configured anything on unRaid regarding the CPUs with `isolcpus` for example. Should I? Is there any other things that I should be taking care of? Thanks

Hey, Thanks for the video, and this new method which is really really faster than the old one. However I got an issue at some point: OSX was running 10x the normal speed. I browsed the thread, and found out the solution was to use older UFI files. I took those from your video from september. It did the trick. However I'm curious to know the reason of this failure for some of us But I got other issues too ... I've been able to boot, and also been able to attach the GPU (a MSI 1070 Gaming X). However the Graphic card is not recognized on OSX, and appears incorrectly. I've attached several pictures and the VM XML + Clover config plist + devices informations are available here https://gist.github.com/arkan/0aabf5243d5fe3af82eaeb6aaf8539cc Anyone has an idea? Thanks

I'm getting the following error while trying to update the Plex image: root@ark:~# docker pull limetech/plex Using default tag: latest latest: Pulling from limetech/plex 6ffe5d2d6a97: Already exists f4e00f994fd4: Already exists e99f3d1fc87b: Already exists a3ed95caeb02: Already exists ededd75b6753: Already exists 1ddde157dd31: Already exists 0a487611efb0: Pull complete 8bfd8127b8cc: Pull complete ea61e8c14bd4: Pull complete layers from manifest don't match image configuration root@ark:~# docker version Client: Version: 1.10.3 API version: 1.22 Go version: go1.5.3 Git commit: ceb0ccd-unsupported Built: Sun Mar 13 18:56:59 2016 OS/Arch: linux/amd64 Server: Version: 1.10.3 API version: 1.22 Go version: go1.5.3 Git commit: ceb0ccd-unsupported Built: Sun Mar 13 18:56:59 2016 OS/Arch: linux/amd64 root@ark:~# Any idea?

Hi, First thanks for your guide. I followed the instructions, and tried to boot using VNC. However the loading takes ages(hours and never completes) and I don't know why ... Here is my XML <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS</name> <uuid>7b5d8655-5ac8-b824-eb8c-5435faf61f66</uuid> <metadata> <vmtemplate xmlns="unraid" name="macOS" icon="/mnt/user/ISOS/OSX/OSX-10.12.png"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7b5d8655-5ac8-b824-eb8c-5435faf61f66_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Penryn</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/disks/Samsung_SSD_850_EVO_250GB_S2R6NX0H750197X/Mac OS Sierra/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='sata'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOS/OSX/sierra_usb'/> <backingStore/> <target dev='hda' bus='sata'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </memballoon> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=OSKEYS/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> Any idea? Thanks

Anyone please

Issues happened again .... I run smart tests, and even if the quickest one succeed without issues, the longest fails at 10% with the following message: "Errors occurred - Check SMART report" So here is the results: ATA Error Count: 24 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 24 occurred at disk power-on lifetime: 615 hours (25 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 88 a1 95 e0 Error: UNC at LBA = 0x0095a188 = 9806216 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 78 a0 95 e0 08 17:15:44.108 READ DMA c8 00 00 78 9f 95 e0 08 17:15:44.107 READ DMA c8 00 00 78 9e 95 e0 08 17:15:44.107 READ DMA c8 00 00 78 9d 95 e0 08 17:15:44.104 READ DMA c8 00 00 78 9c 95 e0 08 17:15:44.103 READ DMA Error 23 occurred at disk power-on lifetime: 615 hours (25 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 a8 fb 94 e0 Error: UNC at LBA = 0x0094fba8 = 9763752 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 78 ec 94 e0 08 17:15:30.205 READ DMA c8 00 00 78 eb 94 e0 08 17:15:30.205 READ DMA c8 00 00 78 ea 94 e0 08 17:15:30.205 READ DMA c8 00 00 78 e9 94 e0 08 17:15:30.202 READ DMA c8 00 00 78 e8 94 e0 08 17:15:30.202 READ DMA Error 22 occurred at disk power-on lifetime: 615 hours (25 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 cc 93 e0 Error: UNC at LBA = 0x0093cc78 = 9686136 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 78 b0 93 e0 08 17:15:07.011 READ DMA c8 00 00 78 af 93 e0 08 17:15:07.011 READ DMA c8 00 00 78 ae 93 e0 08 17:15:07.010 READ DMA c8 00 00 78 ad 93 e0 08 17:15:07.008 READ DMA c8 00 00 78 ac 93 e0 08 17:15:07.008 READ DMA Error 21 occurred at disk power-on lifetime: 615 hours (25 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 d8 4f 93 e0 Error: UNC at LBA = 0x00934fd8 = 9654232 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 78 a9 92 e0 08 17:14:54.023 READ DMA c8 00 00 78 a8 92 e0 08 17:14:54.023 READ DMA c8 00 00 78 a7 92 e0 08 17:14:54.022 READ DMA c8 00 00 78 a6 92 e0 08 17:14:54.022 READ DMA c8 00 00 78 a5 92 e0 08 17:14:54.020 READ DMA Error 20 occurred at disk power-on lifetime: 615 hours (25 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 a0 20 92 e0 Error: UNC at LBA = 0x009220a0 = 9576608 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 78 20 92 e0 08 17:14:41.626 READ DMA c8 00 00 78 1f 92 e0 08 17:14:41.625 READ DMA c8 00 00 78 1e 92 e0 08 17:14:41.625 READ DMA c8 00 00 78 1d 92 e0 08 17:14:41.623 READ DMA c8 00 00 78 1c 92 e0 08 17:14:41.623 READ DMA And here is the disk informations: Thanks for your help

Basically upgrading to Unraid 6.2 which comes with Docker 1.10 solved the issue.

Awesome. Sorry I missed this FAQ... This is all solved. Thanks again!