**VIDEO GUIDE** How to Install MacOS Mojave or High Sierra as a VM

[aptalca]

Thanks gridrunner for posting new smc_read file. not sure why it won't work for me, I get all the text without the OSK key any ideas of why it won't work for me?

The key is in there [emoji6] I know it's hard to believe but that long single line really is the key.

 

You might want to remove that screenshot

[kuhnamatata]

The key is in there  I know it's hard to believe but that long single line really is the key.

thanks aptalca, had no clue as to what I was looking for

[planetwilson]

Before I try gong down the GPU passthrough route. Does anyone know how to set the resolution for VNC or splashtop?

 

I tried updating the config.plist file in the EFI partition for Clover but it seemed to make no difference.

 

<key>ScreenResolution</key>

<string>1280x1024</string>

[SpaceInvaderOne]

Before I try gong down the GPU passthrough route. Does anyone know how to set the resolution for VNC or splashtop?

 

I tried updating the config.plist file in the EFI partition for Clover but it seemed to make no difference.

 

<key>ScreenResolution</key>

<string>1280x1024</string>

 

yes have a look earlier in this thread  http://lime-technology.com/forum/index.php?topic=51915.msg501612#msg501612

[kode54]

Quick hint, for those using Mac compact keyboards:

 

"4. As it restarts press delete (if using a mac connect a usb keyboard as mac backspace will not work)"

 

Fn-Delete on a Mac keyboard will emit a delete-forward, aka the PC Delete key.

[geosko]

gridrunner what graphic card are you using? I have one sapphire hd 6450 but it seems that is not compatible with uefi. Do you have any special rom?

[peter_sm]

Anyone running 6.3.0-rc1 with Sierra? I cant boot. Will try do run 6.2.1 again and see if it works.

[peter_sm]

6.2.1 is OK.. Now back to 6.3.0

[SpaceInvaderOne]

6.2.1 is OK.. Now back to 6.3.0

 

i tried sierra and el cap with 6.3 and both boot ok for me. But not tried passing through any gpu at the moment.

[local.bin]

 

Thankas for the videos @gridrunner, I have 2 vms up and running thanks to you

 

I wondered if it was possible to upgrade to Sierra rather than doing a fresh install?

 

I am stuck with the vm booting into the EFI shell.

 

I can get clover to boot again and see the option to install OSX as a new boot option in clover, but that option will not boot.

 

Is it possible?

[SpaceInvaderOne]

 

Thankas for the videos @gridrunner, I have 2 vms up and running thanks to you

 

I wondered if it was possible to upgrade to Sierra rather than doing a fresh install?

 

I am stuck with the vm booting into the EFI shell.

 

I can get clover to boot again and see the option to install OSX as a new boot option in clover, but that option will not boot.

 

Is it possible?

Glad they were helpful 

If you are upgrading to sierra from elcap  yes its possible . Check peter_sm post earlier in thread http://lime-technology.com/forum/index.php?topic=51915.msg501680#msg501680

 

The reason you not booting the install/upgrader is probably this. Please check.

 

 <qemu:arg value='-cpu'/>
    <qemu:arg value='core2duo,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

Your cpu is set for core2duo which is fine for el cap but not sierra.

 

you will need to change it to this

 <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

Also when you have upgraded you will need to open the efi partition again then download the files description of the sierra video and use

the efi folder in that instead as that contains a different patched clover for sierra. If you dont do this the machine will not run at full speed.

 

 

[peter_sm]

6.2.1 is OK.. Now back to 6.3.0

 

i tried sierra and el cap with 6.3 and both boot ok for me. But not tried passing through any gpu at the moment.

I think it's the CLOVER that's need to be updated. But it's looks like it's hangs during the identifying of the GPU.

 

 

Skickat från min iPhone med Tapatalk

[local.bin]

 

Glad they were helpful 

If you are upgrading to sierra from elcap  yes its possible . Check peter_sm post earlier in thread http://lime-technology.com/forum/index.php?topic=51915.msg501680#msg501680

 

The reason you not booting the install/upgrader is probably this. Please check.

 

 <qemu:arg value='-cpu'/>
    <qemu:arg value='core2duo,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

Your cpu is set for core2duo which is fine for el cap but not sierra.

 

you will need to change it to this

 <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

Also when you have upgraded you will need to open the efi partition again then download the files description of the sierra video and use

the efi folder in that instead as that contains a different patched clover for sierra. If you dont do this the machine will not run at full speed.

 

@gridrunner again useful information thanks & @peter_sm

 

I;ve spent the best part of the day getting this to work and upgrading.

 

I have used the Sierra EFI files and am running well, except I am again booting into the efi shell.

 

I have to manually point the shell to the efi file to boot into clover each time, for some reason.

 

It seem to occur when I change your default resolution from 800x600 to 1920x1080.

 

I've setup the same resolution in the ovmf config too, so not sure why its not booting striaght.

 

I have at least un upgraded El Cap to Sierra, thank you.

 

I will listen to your clean install video to see if I have missed a step....

[SpaceInvaderOne]

 

Glad they were helpful 

If you are upgrading to sierra from elcap  yes its possible . Check peter_sm post earlier in thread http://lime-technology.com/forum/index.php?topic=51915.msg501680#msg501680

 

The reason you not booting the install/upgrader is probably this. Please check.

 

 <qemu:arg value='-cpu'/>
    <qemu:arg value='core2duo,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

Your cpu is set for core2duo which is fine for el cap but not sierra.

 

you will need to change it to this

 <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

Also when you have upgraded you will need to open the efi partition again then download the files description of the sierra video and use

the efi folder in that instead as that contains a different patched clover for sierra. If you dont do this the machine will not run at full speed.

 

@gridrunner again useful information thanks & @peter_sm

 

I;ve spent the best part of the day getting this to work and upgrading.

 

I have used the Sierra EFI files and am running well, except I am again booting into the efi shell.

 

I have to manually point the shell to the efi file to boot into clover each time, for some reason.

 

It seem to occur when I change your default resolution from 800x600 to 1920x1080.

 

I've setup the same resolution in the ovmf config too, so not sure why its not booting striaght.

 

I have at least un upgraded El Cap to Sierra, thank you.

 

I will listen to your clean install video to see if I have missed a step....

 

ok i maybe your ovmf nvram file is corrupt.

try this.

 

1. make a new  ovmf linux template virtual machine.

2. name it say "test template"

3. set primary disk location to none.

4. leave everything else as is, but uncheck start vm after creation.

5. click update

 

what this will do is generate a new nvram file. so now goto the vm "test template"

and look for the os tags like below

 

 <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/6d6dda8c-f323-ba22-8ed6-8fe56565dfd1_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </os>

 

copy that out of your test template then goto the osx vm template and replace the os tag code in that, with what you have just copied from the test template.

 

now go back to your test template and find the line in uuid tags

like this

<uuid>6d6dda8c-f323-ba22-8ed6-8fe56565dfd1</uuid>

 

then use that uuid in the test template copy it and then open osx template and replace the uuid line with that.

 

after you have changed those 2 parts in the xml you can delete the "test template" vm

 

You will have to change the resolution in the ovmf again as the new nvram file will be defualt.

 

Please try that and report back here 

 

[local.bin]

@gridrunner makes sense what you have suggested and it worked when I only used the os part of the new test template, I got clover auto loading again.

 

I couldn't use the uuid of the test template until I had delete it, as I got the error of duplicate uuid.

 

Anyway past that and deleted the test and pasted the correct uuid from the test template to the el cap ovmf template.

 

I get the following error when I try start that vm;

 

unable to stat: /etc/libvirt/qemu/nvram/a1ffa6bc-4bf9-8a37-f338-aab26fcd906d_VARS-pure-efi.fd: No such file or directory

 

Do I need to do something with test so that it creates the nvram are somehow?

 

Edit:1 OK, so I checked /etc/libvirt/qemu/nvram/ and indeed the nvram had not been created, so I created another test with no disk and this time started the vm. The nvram was created, so I am now pasting the new details into the elcap vm xml

 

Edit:2 So the nvram gets deleted with the deletion of the test vm, so then the el cap vm cannot find it. Will copy a version before I delete the test vm template.

 

Edit:3 Ok, so that worked and the vm is booting. Will try changing the resolution next.

 

Thanks for the direction

[SpaceInvaderOne]

@gridrunner makes sense what you have suggested and it worked when I only used the os part of the new test template, I got clover auto loading again.

 

I couldn't use the uuid of the test template until I had delete it, as I got the error of duplicate uuid.

 

Anyway past that and deleted the test and pasted the correct uuid from the test template to the el cap ovmf template.

 

I get the following error when I try start that vm;

 

unable to stat: /etc/libvirt/qemu/nvram/a1ffa6bc-4bf9-8a37-f338-aab26fcd906d_VARS-pure-efi.fd: No such file or directory

 

Do I need to do something with test so that it creates the nvram are somehow?

 

Edit:1 OK, so I checked /etc/libvirt/qemu/nvram/ and indeed the nvram had not been created, so I created another test with no disk and this time started the vm. The nvram was created, so I am now pasting the new details into the elcap vm xml

 

Edit:2 So the nvram gets deleted with the deletion of the test vm, so then the el cap vm cannot find it. Will copy a version before I delete the test vm template.

 

Edit:3 Ok, so that worked and the vm is booting. Will try changing the resolution next.

 

Thanks for the direction

Cool glad you got it working

 

I made a script that backs up the nvram and xml of all the vms, for use with squids user script plugin, that you may find useful

in case one gets corrupted again  http://lime-technology.com/forum/index.php?topic=50416.msg505867#msg505867

[dustin.reynolds]

Hello, everyone. I was wondering if I could get a little help. I was able to pass-thru my GPU however, I cannot get my keyboard and mouse to pass-thru. I would be very grateful for any suggestion you may have. I hope I have posted the proper information, thanks in advance.

 

XML:

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacOSX</name>
  <metadata>
    <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='3'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-2.5'>hvm</type>
    <kernel>/mnt/disk1/isos/Yosemite/bootr2839</kernel>
    <boot dev='hd'/>
    <bootmenu enable='yes'/>
  </os>
  <features>
    <acpi/>
  </features>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>core2duo</model>
    <vendor>Intel</vendor>
  </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/cache/vdisks/MacOSX/vdisk1.img'/>
      <target dev='sdc' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' 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='pci' index='3' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='3'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x02' function='0x0'/>
    </controller>
    <controller type='pci' index='4' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='4'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x03' function='0x0'/>
    </controller>
    <controller type='pci' index='5' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='5'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x04' function='0x0'/>
    </controller>
    <controller type='pci' index='6' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='6'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x05' function='0x0'/>
    </controller>
    <controller type='pci' index='7' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='7'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x06' function='0x0'/>
    </controller>
    <controller type='pci' index='8' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='8'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='9' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='9'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x08' function='0x0'/>
    </controller>
    <controller type='pci' index='10' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='10'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x09' function='0x0'/>
    </controller>
    <controller type='pci' index='11' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='11'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0a' function='0x0'/>
    </controller>
    <controller type='pci' index='12' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='12'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0b' function='0x0'/>
    </controller>
    <controller type='pci' index='13' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='13'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0c' function='0x0'/>
    </controller>
    <controller type='pci' index='14' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='14'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0d' function='0x0'/>
    </controller>
    <controller type='pci' index='15' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='15'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0e' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:51:66:48'/>
      <source bridge='br0'/>
      <model type='e1000-82545em'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
    </interface>
    <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='0x02' slot='0x05' 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='0x03' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc52b'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1b1c'/>
        <product id='0x1b09'/>
      </source>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <seclabel type='none' model='none'/>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,osk=XXXXXXXXXXX'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='core2duo,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

PCI Devices:

00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07)
00:01.1 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x8) [8086:1905] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31)
00:1b.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #17 [8086:a167] (rev f1)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1)
00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1)
00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #7 [8086:a116] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a145] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GM200 High Definition Audio [10de:0fb0] (rev a1)
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1)
02:00.1 Audio device [0403]: NVIDIA Corporation GK208 HDMI/DP Audio Controller [10de:0e0f] (rev a1)
04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
05:00.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:01.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:02.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:03.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:04.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:05.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:06.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:07.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
08:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
09:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
0b:00.0 Audio device [0403]: Creative Labs SB Recon3D [1102:0012] (rev 01)
0c:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
0e:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
0f:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]

 

USB Devices:

Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver   ----Main Mouse
Bus 005 Device 002: ID 1b1c:1b09 Corsair  ----Main Keyboard
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0b05:180a ASUSTek Computer, Inc. 
Bus 001 Device 004: ID 0781:5575 SanDisk Corp. 
Bus 001 Device 003: ID 046d:082c Logitech, Inc. 
Bus 001 Device 006: ID 28de:1142  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[kode54]

Those entries in the XML should be managed='yes', otherwise they will not be unbound from the host first.

[SpaceInvaderOne]

Hello, everyone. I was wondering if I could get a little help. I was able to pass-thru my GPU however, I cannot get my keyboard and mouse to pass-thru. I would be very grateful for any suggestion you may have. I hope I have posted the proper information, thanks in advance.

 

XML:

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacOSX</name>
  <metadata>
    <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='3'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-2.5'>hvm</type>
    <kernel>/mnt/disk1/isos/Yosemite/bootr2839</kernel>
    <boot dev='hd'/>
    <bootmenu enable='yes'/>
  </os>
  <features>
    <acpi/>
  </features>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>core2duo</model>
    <vendor>Intel</vendor>
  </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/cache/vdisks/MacOSX/vdisk1.img'/>
      <target dev='sdc' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' 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='pci' index='3' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='3'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x02' function='0x0'/>
    </controller>
    <controller type='pci' index='4' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='4'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x03' function='0x0'/>
    </controller>
    <controller type='pci' index='5' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='5'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x04' function='0x0'/>
    </controller>
    <controller type='pci' index='6' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='6'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x05' function='0x0'/>
    </controller>
    <controller type='pci' index='7' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='7'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x06' function='0x0'/>
    </controller>
    <controller type='pci' index='8' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='8'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='9' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='9'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x08' function='0x0'/>
    </controller>
    <controller type='pci' index='10' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='10'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x09' function='0x0'/>
    </controller>
    <controller type='pci' index='11' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='11'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0a' function='0x0'/>
    </controller>
    <controller type='pci' index='12' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='12'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0b' function='0x0'/>
    </controller>
    <controller type='pci' index='13' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='13'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0c' function='0x0'/>
    </controller>
    <controller type='pci' index='14' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='14'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0d' function='0x0'/>
    </controller>
    <controller type='pci' index='15' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='15'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x0e' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:51:66:48'/>
      <source bridge='br0'/>
      <model type='e1000-82545em'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
    </interface>
    <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='0x02' slot='0x05' 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='0x03' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc52b'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1b1c'/>
        <product id='0x1b09'/>
      </source>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <seclabel type='none' model='none'/>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,osk=XXXXXXXXXXX'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='core2duo,vendor=GenuineIntel'/>
  </qemu:commandline>
</domain>

 

PCI Devices:

00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07)
00:01.1 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x8) [8086:1905] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31)
00:1b.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #17 [8086:a167] (rev f1)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1)
00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1)
00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #7 [8086:a116] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a145] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GM200 High Definition Audio [10de:0fb0] (rev a1)
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1)
02:00.1 Audio device [0403]: NVIDIA Corporation GK208 HDMI/DP Audio Controller [10de:0e0f] (rev a1)
04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
05:00.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:01.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:02.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:03.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:04.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:05.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:06.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
06:07.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:1187]
08:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
09:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
0b:00.0 Audio device [0403]: Creative Labs SB Recon3D [1102:0012] (rev 01)
0c:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
0e:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
0f:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]

 

USB Devices:

Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver   ----Main Mouse
Bus 005 Device 002: ID 1b1c:1b09 Corsair  ----Main Keyboard
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0b05:180a ASUSTek Computer, Inc. 
Bus 001 Device 004: ID 0781:5575 SanDisk Corp. 
Bus 001 Device 003: ID 046d:082c Logitech, Inc. 
Bus 001 Device 006: ID 28de:1142  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

I cant see anything wrong with your xml.

But i see this line

<kernel>/mnt/disk1/isos/Yosemite/bootr2839</kernel>

 

From this i guess you are using Yosimite yes? I havent used yosimite myself (only el cap and sierra) so this possibly could be why?

What you could try is to convert the vm to ovmf and cover and try with that.

[dustin.reynolds]

Thank you for the help guys, I was able to get the keyboard & mouse working. I had to convert the vm to ovmf and clover. Thanks gridrunner for the suggestion.

[SpaceInvaderOne]

Just a stupid video i made of running unRAID on a macbook pro with usb flash drive as array. Then using its own OS X operating system passed through via its sdd as an unRAID vm!!

 

OS X on unRAID running on a macbook pro!

 

[DoeBoye]

So I'm still struggling with getting my hd7770 GPU passed through to my sierra VM. (Note: It works fine in Windows 10) . I've tried just about everything in this thread, and the best I can get is a pixelated/garbled red screen. It appears to be trying, but something is just not clicking .

 

I've been poking around on the internet in the Hackintosh forums, and have come across posts discussing using the verde.kext or modifying the config.plist to include Dashimaki frame buffer support...

 

My OSX experience is extremely limited, and though I can follow directions, I'm really not entirely sure if I'm just wasting time with those 2 suggestions.

 

Any thoughts? Part of me wonders if my card is just not supported, but I keep reading about successful implementations of OSX with an hd7770.

 

Thanks for any insight!

[SpaceInvaderOne]

So I'm still struggling with getting my hd7770 GPU passed through to my sierra VM. (Note: It works fine in Windows 10) . I've tried just about everything in this thread, and the best I can get is a pixelated/garbled red screen. It appears to be trying, but something is just not clicking .

 

I've been poking around on the internet in the Hackintosh forums, and have come across posts discussing using the verde.kext or modifying the config.plist to include Dashimaki frame buffer support...

 

My OSX experience is extremely limited, and though I can follow directions, I'm really not entirely sure if I'm just wasting time with those 2 suggestions.

 

Any thoughts? Part of me wonders if my card is just not supported, but I keep reading about successful implementations of OSX with an hd7770.

 

Thanks for any insight!

 

I have no experience with that card but have a look at this post here it may be worth a try.

 

https://www.tonymacx86.com/threads/radeon-hd-7750-xfx-glitchy-after-10-10-3-update.161511/

 

You will have to manually add the kext to the clover folder in the efi partition.  efi/clover/kexts/other

 

 

 

[DoeBoye]

I have no experience with that card but have a look at this post here it may be worth a try.

 

https://www.tonymacx86.com/threads/radeon-hd-7750-xfx-glitchy-after-10-10-3-update.161511/

 

You will have to manually add the kext to the clover folder in the efi partition.  efi/clover/kexts/other

 

Thanks gridrunner! I'll try that tonight! I appreciate you looking into it for me! I thought I found everything there was on this issue, but I didn't find that thread!

 

I tried the verde.kext fix last night that I mentioned previously, but it didn't do anything . Though the instructions said to put it in the 10.10 folder... Now I realize those folders must be the osx version, so 10.10 would not have worked for Sierra anyways...

 

A couple of questions: Once I've dumped the kext in the correct efi folder, do I need to do anything else (Run Kext Utility etc etc), or do I just unmount the EFI partition and reboot?

 

Finally, if I update my install, does this need to be repeated again, or will it stick?

 

Thanks so much for the help! I'm so close to getting this working and ditching my bare steel PC and Mac (And justifying the monster server humming away in my basement! ;p)

[SpaceInvaderOne]

I have no experience with that card but have a look at this post here it may be worth a try.

 

https://www.tonymacx86.com/threads/radeon-hd-7750-xfx-glitchy-after-10-10-3-update.161511/

 

You will have to manually add the kext to the clover folder in the efi partition.  efi/clover/kexts/other

 

Thanks gridrunner! I'll try that tonight! I appreciate you looking into it for me! I thought I found everything there was on this issue, but I didn't find that thread!

 

I tried the verde.kext fix last night that I mentioned previously, but it didn't do anything . Though the instructions said to put it in the 10.10 folder... Now I realize those folders must be the osx version, so 10.10 would not have worked for Sierra anyways...

 

A couple of questions: Once I've dumped the kext in the correct efi folder, do I need to do anything else (Run Kext Utility etc etc), or do I just unmount the EFI partition and reboot?

 

Finally, if I update my install, does this need to be repeated again, or will it stick?

 

Thanks so much for the help! I'm so close to getting this working and ditching my bare steel PC and Mac (And justifying the monster server humming away in my basement! ;p)

 

Yes if you put in the folder thats all you need to do. Most people put the essential kexts in the clover in efi. They should stick there if you reinstall or upgrade.

Some people say that some kexts dont work in clover and they have to put them in /System/Library/Extensions but i have only put mine in clover