May 9, 20179 yr So I have been perplexed by this problem for the past 48 hours. I have followed various installation techniques from that of @archedraft, @gridrunner, and @danofun to no avail. Every time I boot up an image of macOS Sierra through Clover, my loading screen looks like this: http://imgur.com/a/ugQo0. For testing purposes I tried to run OSX El Capitan, which was surprisingly successful, yet pointless in the longterm as it does not support my RX 480 GPU at high resolutions. I tried making an complete disk image pre-installed with VMWare and it worked, however porting it to unRaid caused the glitch. I tried making an empty image on unRaid with a separate install image, however the same error occurs. I can always boot to Clover in perfect speeds and clarities with a mouse and a keyboard functioning correctly. I originally thought the graphics card was the problem, but it seems the same thing happens through VNC. Specs: Intel Core i7-6700K MSI Z170A SLI PLUS Corsair Vengeance LED 16GB (2 x 8GB) DDR4-3000 XFX RX 480 8GB GPU unRAID 6.3.3 Clover_v2.4k_r4045-UEFI FakeSMC.dmg macOS 10.12.4 XML (well one of the many versions I've tried): <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS Sierra</name> <uuid>e48673fa-abfc-4352-81ec-29e49f3e86ba</uuid> <metadata/> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/315449c2-826c-b76e-71f6-eac86acdd21c_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='forbid'>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/user/domains/macOS Sierra/SierraInstallation'/> <target dev='hda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/domains/macOS Sierra/sierra_vdisk1.img'/> <target dev='hdc' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <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 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'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1f' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc332'/> <address bus='1' device='4'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='2'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> </qemu:commandline> </domain> Edited May 9, 20179 yr by About7Deaths
May 9, 20179 yr I have a similar issue with my gtx 780, clover looks fine but the boot screen is all messed up. Once the drivers kick in near the log in screen everything goes back to normal.
May 9, 20179 yr VNC gets wonky due to it expecting one resolution and receiving another (iirc.) Otherwise should be fine to use as a desktop or with other remote desktop software.
May 9, 20179 yr Author 1 hour ago, squark said: I think he said that it occurs with both the graphics card and vnc. Yes, I did say it occurs with both the graphics card and vnc. Also, one of the screenshots is a picture of the computer at the desktop while the other is of the computer booting. Edited May 9, 20179 yr by About7Deaths
May 9, 20179 yr I do have similar issues. once I added my original MacPro (late 2009) GeForce GT 120 Gfx card into my unRAID and wanted to pass it trough to my macOS KVM running 10.12.4 Error Message: internal error: process exited while connecting to monitor: 2017-05-09T13:49:59.860781Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2017-05-09T13:49:59.860801Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to get group 1 2017-05-09T13:49:59.860810Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.2,addr=0x4: Device initialization failed and replaced the VNC portion with <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> </hostdev> as stated in the guide from gridrunner unRAID seems to have the problem that qemu does not "known" my GT 120. What do I miss?
May 9, 20179 yr 2 hours ago, About7Deaths said: Yes, I did say it occurs with both the graphics card and vnc. Also, one of the screenshots is a picture of the computer at the desktop while the other is of the computer booting. Neither shows the desktop GPU output. Both only show VNC output. Is your complaint that BOTH the GPU and VNC do it, or just VNC when using GPU? If it is just the VNC being garbled, that is common, at least in some of my installs when using in conjunction with GPU. VNC in OS X typically does not work correctly unless you take further, needless steps. WHICH is also part of the reason gridrunner suggests using splashtop or other remote desktop.
May 9, 20179 yr Author 46 minutes ago, 1812 said: Neither shows the desktop GPU output. Both only show VNC output. Is your complaint that BOTH the GPU and VNC do it, or just VNC when using GPU? If it is just the VNC being garbled, that is common, at least in some of my installs when using in conjunction with GPU. VNC in OS X typically does not work correctly unless you take further, needless steps. WHICH is also part of the reason gridrunner suggests using splashtop or other remote desktop. Ah, sorry for the confusion. Neither of my screenshots show the GPU output as it looks exactly the same as the VNC output. I have tried both methods seperately and both have the same graphical issue. However neither has the issue in El Capitan so I assume the issue is that of Sierra or unRAID. Edited May 9, 20179 yr by About7Deaths
May 9, 20179 yr 5 minutes ago, About7Deaths said: Ah, sorry for the confusion. Neither of my screenshots show the GPU output as it looks exactly the same as the VNC output. I have tried both methods seperately and both have the same graphical issue. However neither has the issue in El Capitan so I assume the issue is that of Sierra or unRAID. 2 questions: 1. in the bios, what is the resolution set at? 2. what happens when you start the vm w/out the vnc viewer and only the GPU?
May 9, 20179 yr Author 18 minutes ago, 1812 said: 2 questions: 1. in the bios, what is the resolution set at? 2. what happens when you start the vm w/out the vnc viewer and only the GPU? 1) There is no resolution option in my bios. (I checked every setting.) It is a 1080p monitor. 2) When I start the VM without the VNC viewer my monitor will boot up to Clover. Once Clover boots macOS, the Apple logo will appear in the top left corner (just like in the VNC picture) and multiple tiny screens will load up along the top.
May 9, 20179 yr Author 9 minutes ago, ashman70 said: What happens if you try to boot into safe mode? With my most recent configuration I am booting into the macOS Installation disk, so I don't believe I can boot into safe mode.
May 9, 20179 yr Author Just now, ashman70 said: If you are booting into the OSX installation disk that how can any drivers load? I assumed Clover took care of that. With a prior install I had a pre-installed disk image that I made in VMWare and ported / converted to unRAID KVM; this other image had the same issue and was able to boot all the way into the desktop. If you'd like I can add that old Sierra image back into unRAID and try booting it into safe mode. (Also, what is the best method for booting into safe mode from a GPU with this kind of setup?)
May 9, 20179 yr You hold down the SHIFT key once the mac begins to boot, that's how you boot into safe mode. It definitely sounds to me like its a driver issue. It also sounds like El Capitan may have had native support for your GPU and for whatever reason Sierra doesn't. Was there any differences between your clover configuration for El Capitain vs Sierra?
May 9, 20179 yr Author 23 minutes ago, ashman70 said: You hold down the SHIFT key once the mac begins to boot, that's how you boot into safe mode. It definitely sounds to me like its a driver issue. It also sounds like El Capitan may have had native support for your GPU and for whatever reason Sierra doesn't. Was there any differences between your clover configuration for El Capitain vs Sierra? Oddly enough I did a lot of research on the compatibility of my GPU and many people stated that the RX 480 does not, nor will it ever have support for El Capitan, otherwise I would have stayed on it. Whenever I ran Capitan the GPU seemed passive; it had poor resolution and had a few graphical glitches (however not nearly as bad as Sierra). What component do you think is having the driver issue? I don't think it's necessarily a GPU driver issue as the same error happened with VNC without using the GPU at all. With El Capitan I used Enoch Chameleon + SeaBIOS, I hadn't tried to use Clover on that setup. With Sierra I'm using Clover + OVMF. My motherboard is supposedly compatible with both.
May 9, 20179 yr I'm not sure, I gave up a long time ago trying to get OSX VM's to work, some people seem to have no problems and get it the first time, others like me never seem to be able to pull it off. Hopefully one of the other members with more experience can help you out, I know how frustrating it is.
May 9, 20179 yr Any idea about my error? This is coming from unRAID KVM Manger when I power on the VM. Or better a separate thread? 4 hours ago, Trebron74 said: I do have similar issues. once I added my original MacPro (late 2009) GeForce GT 120 Gfx card into my unRAID and wanted to pass it trough to my macOS KVM running 10.12.4 Error Message: internal error: process exited while connecting to monitor: 2017-05-09T13:49:59.860781Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2017-05-09T13:49:59.860801Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to get group 1 2017-05-09T13:49:59.860810Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.2,addr=0x4: Device initialization failed and replaced the VNC portion with <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> </hostdev> as stated in the guide from gridrunner unRAID seems to have the problem that qemu does not "known" my GT 120. What do I miss? Any idea about my error? This is coming from unRAID KVM Manger when I power on the VM. Or better a separate thread?
May 9, 20179 yr 15 minutes ago, Trebron74 said: Any idea about my error? This is coming from unRAID KVM Manger when I power on the VM. Or better a separate thread? Any idea about my error? This is coming from unRAID KVM Manger when I power on the VM. Or better a separate thread? own thread and post diagnostics.
May 9, 20179 yr 53 minutes ago, ashman70 said: I'm not sure, I gave up a long time ago trying to get OSX VM's to work, some people seem to have no problems and get it the first time, others like me never seem to be able to pull it off. Hopefully one of the other members with more experience can help you out, I know how frustrating it is. Once you get the hang of it, it's "fine." With a few hiccups along the way.... 59 minutes ago, About7Deaths said: With El Capitan I used Enoch Chameleon + SeaBIOS, I hadn't tried to use Clover on that setup. With Sierra I'm using Clover + OVMF. My motherboard is supposedly compatible with both. does your GPU support uefi? if not, then you need to be using seabios and not ovmf. (I don't know anything about your card.)
May 9, 20179 yr Author 25 minutes ago, 1812 said: does your GPU support uefi? if not, then you need to be using seabios and not ovmf. (I don't know anything about your card.) I'm not sure to be exact, supposedly it's a hybrid module that supports either. According to Reddit: "AMD ROMs are Hybrid, they have Legacy section with UEFI/GOP module added in them. SO when you have Legacy mobo (or UEFI mobo with Legacy support enabled) the UEFI/GOP in VBIOS is ignored. On a UEFI mobo for it to really to be using the UEFI/GOP in VBIOS you need to disable CSM in mobo bios. If you only have Legacy VBIOS on card and disable CSM in mobo bios you will get issues (like black screen on power on, etc)." How would I go about booting Sierra from SeaBIOS? I can't find any good tutorials or supported updates for Enoch Chameleon. Technically, why would the GPU's compatibility matter if the problem also persists in VNC? Edited May 9, 20179 yr by About7Deaths
May 9, 20179 yr 1 hour ago, About7Deaths said: Technically, why would the GPU's compatibility matter if the problem also persists in VNC? actually, that's a good point. if you're in ovmf/sierra, boot the vm and launch vnc. then at the clover boot loader screen, click restart to access bios. Sequence can be seen below. Change resolution as described.
May 9, 20179 yr Author 1 minute ago, 1812 said: actually, that's a good point. if you're in ovmf/sierra, boot the vm and launch vnc. then at the clover boot loader screen, click restart to access bios. Sequence can be seen below. Change resolution as described. I followed that step within his video and the resolution was already set at 1080p prior to entering the BIOS and upon exiting the BIOS. It didn't help.
May 9, 20179 yr I'm confused because you said: 3 hours ago, About7Deaths said: 1) There is no resolution option in my bios. (I checked every setting.) It is a 1080p monitor. and then said 5 minutes ago, About7Deaths said: I followed that step within his video and the resolution was already set at 1080p prior to entering the BIOS and upon exiting the BIOS. It didn't help. Anyways.... Perhaps you buggered something in clover or it got buggered. Do you have the ability to do a new install? I've abandoned .img files before after messing up a setting an not being able to correct it.
May 9, 20179 yr Author Just now, 1812 said: I'm confused because you said: and then said Anyways.... Perhaps you buggered something in clover or it got buggered. Do you have the ability to do a new install? I've abandoned .img files before after messing up a setting an not being able to correct it. Ah sorry, my unRAID machine does not have a BIOS resolution option, while my Clover / Sierra virtual "machine" does have the resolution option. I have the ability to do a new install, however this is my second attempt using a completely different method yet still having the exact same problem.
Archived
This topic is now archived and is closed to further replies.