SpaceInvaderOne

Thanks. Excellent suggestion. I will probably use the rsync switch. Great work on this Or maybe you could export the disks using qemu-img convert -O output_format source destination

jbrodriguez, I have changed to mainline 6.2.1-2016.09.22. I cant add my server now I saw in the thread you said this Is this why its not working with mainline?

Send server status to phone I have made a script which sends server status to your phone or tablet using pushover or push bullet. It sends 1. Running VMs 2. Running Dockers 3. Free Array space 4. Free cache space 5. Cpu core temperatures You will need a pushover/push bullet account and will need to insert user key and a token into the script. Maybe useful for people who want to check a vm used for cctv etc is running. #!/bin/bash #set whether to use pushnotication [0- none] [1-pushover] [2-pushbullet] pushnotifications="0" #pushover api (only fill in if set above to pushover above) apitoken="token=xxxxxxxxxxxxxxxxxxxx" userkey="user=xxxxxxxxxxxxxxxxxxxx" #pushbullet api (only fill in if set above to pushbullet above) API="xxxxxxxxxxxxxxxxxxx" #dont edit below this line####################################################################### #set function "pushnotice" to push type if [[ "$pushnotifications" =~ ^(1|2)$ ]]; then if [ "$pushnotifications" -eq 1 ]; then function pushnotice { curl -s \ --form-string $apitoken \ --form-string $userkey \ --form-string "message=$1" \ https://api.pushover.net/1/messages.json } echo "set for pushover" elif [ "$pushnotifications" -eq 2 ]; then function pushnotice { curl -u $API: https://api.pushbullet.com/v2/pushes -d type=note -d title="unRAID status" -d body="$1" } echo "set for pushbullet" fi else function pushnotice { echo "$1" } fi vmsrunning=$(virsh list | awk '$1 == "-" || $1+0 > 0 { print $2 }') docsrunning=$(docker ps | awk '{ print $2}') temp=$(sensors | awk '{ print $1,$2,$3}') hdspacefree=$(df -h /mnt/user/ ~ | awk 'NR==2 {print $4}') cachespacefree=$(df -h /mnt/cache/ ~ | awk 'NR==2 {print $4}') #!send server status message pushnotice "These VMs are running $vmsrunning These Dockers are running $docsrunning Array space left $hdspacefree Cache space left $cachespacefree temperatures $temp " sleep 10 exit Hopefully useful Server_info_push.zip

Try changing the smbios to the iMac14,1 or iMac14,2 definition. In your earlier post you say you are using hostdev to passthrough. You could try by qemu:arg value instead as peter_sm did. Check his code on here http://lime-technology.com/forum/index.php?topic=51915.msg501064#msg501064 he is also using an nvidea card.

Yes i have known this to happen to me before. The fix is really easy. It is not to do with seabios or clover. What causes it is sometimes the e1000 network driver built into OSX (AppleIntel8254XEthernet.kext) fails to detect network link. This is basically because of what pci slot the “card” is in. The problem is invoking the e1000 hardware interrupt handler before setup is complete and then it fails to detect network. So the network must be on a custom pci slot and it gets around this problem. I guess that your xml code for the network looks a bit like this now <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='0x01' function='0x0'/> </interface> note this line address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' This is wrong for us. The system will try and put it on here as the default settings. Matbe you deleted the address line and it put this in for you? We need it to be <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> So just change your address line and all will be good. so like below <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> As regards sierra on seabios. Yes and no. I found i couldnt see the install iso on clean install and couldnt see "Boot macOS Install" option if going upgrade with seabios. However after its installed by clover ovmf you can switch to seabios and it will boot I was messing with it today and not really tested it but first impressions it seems very good. speed is normal speed. Sound is good (i am using no soundcard h or gpu, using remote desktop with splashtop) I will test more later. I was using enoch2839 for bootloader.

Ha ok no problem. i have got one done just need to edit it and ill put it up

Yes Peter thats exactly right and works well. I tried un upgrade last week and this was the only way it would work. I tried booting from seabios to do an upgrade but that way didnt work. It never saw the macOS Install in seabios boot menu on reboot. Guys be sure to pay attention to step 6 in Peters post above, as it is easy to miss this and clover automatically boot into the osx drive itself (5 second countdown) and be back in el capitan. This happened to me and i thought it had failed! If this happens you can just reboot the vm and then choose macOS Install second time around. Also as Peter says its best to install patched clover first as is based off latest clover. Some earlier clovers (not sure from which version) will not see the macOS Install in clover boot menu.

Great glad you got it working Yes the reason this is at 800 x 600 is because if you change the resolution in the vm (clover) it doesnt match the ovmf settings and you get the prob you describe.This isnt a problem with gpu passed through. So for vnc this is what you must do. 1 start vm normally. Change the resolution of clover with clover configurator or edit the config.plist file ( eg 1920 x 1080) 2. reboot the vm but stop on the clover boot loader 3. choose restart on clover screen 4. As it restarts press delete (if using a mac connect a usb keyboard as mac backspace will not work) 5. now you will be in config screen 6. change resolution here to match what you did in step 1. 7. save settings and restart and boot to osx now you will have resolution you want.

Yes it should be possible. Attach the harddrive to your server as an unassigned disk. Then use my guide (second video) to create an ovmf xml template but instead of attaching the vdisk as primary drive like below <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/virtual systems/mac os sierra/vdisk1.img'/> <target dev='hda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> change it to this <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-ST31000528AS_6VP41EPS'/> <target dev='hda' bus='sata'/> </disk> This will pass through the whole disk here named ata-ST31000528AS_6VP41EPS (find out the disk id of your disk and put that in there) Then booting the vm should just boot straight off the drive. I have done similar before off a usb harddrive connected to unraid. After its booted use open the efi partition then delete the efi folder and replace it with the one in the video (see the guide). That will have the right clover files for unraid. Let me know how you get on

I am also passing through my gpu (6450) and a keyboard and mouse using host dev. my code below <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </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='0x03' slot='0x00' function='0x1'/> </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='0xc52b'/> </source> </hostdev>

for some reason i cant open my server on app any more. it is added and reports disk info etc. but when i press on server nothing happens. i have this issue with my xperia z2 phone and xperia z3 tablet. Any ideas?

if you are using the ssd exclusively for the vm, i should passthrough the disk then install the os directly to the disk rather than use a vdisk I am also trying to get the best performance I can from a Win10 gaming VM on an SSD, accessed using Unassigned Devices. Currently I am using a vdisk but if the performance gains are significant then I would pass through the entire SSD. Are the gains significant? And what is the best practice for passing through the entire disk? yes i put all my games on a passed through disk(d) but have the os drive © on vdisk. <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-ST31000528AS_6VP41EPS'/> <target dev='hdd' bus='virtio'/> </disk> you can adjust the above code for your needs. ata-ST31000528AS_6VP41EPS is my disks id. You will need to put in yours here

Yes just done a guide to do a fresh install of Sierra on unRAID. Hope you find it useful.

Great thanks glad you like them. Ive put the files in the youtube description now. Sorry bit tired today and forgot !!! I have just put up a video for installing a fresh copy mac OS Sierra in ovmf and clover as well if you interested. many more unraid vids coming which will be released every friday.

Yeah thats what i like to be able to have the sound on mac like rdp on pc

using the webvnc the cursor will always be out of sync unfortunately. With tight vnc make sure the screen sharing is enabled. I dont use either. I use splashtop desktop http://www.splashtop.com/ the free version works within your own network. It works very well and works with mac, win, and linux.

Great glad its all working for you

Yeah it finds my efi partitions ok. I find if i want to install kexts though, I must delete all folders in the clover kext folder except the "other" folder and put them in there. Ed

Glad you have got it working. I have not got the screen correctly showing more than 800x600. You can edit the resolution in the config.plist but it seems to mess up the screen for me. But you may have better luck? The reason 800x600 works is because that is the setting in the bios of the vm. It has to match the resolution of the osx when using vnc. If using gpu passthrough this isnt an issue. If you change the resolution in the bios aswell it may work. But you would have to do so every boot. I havent tried yet as i can never get into the bios screen quick enough!! I will have a look at this problem and see if i can figure a way around this. This isnt a problem on seabios so maybe boot with that. You can still use same disk image just setup another xml and point it to the vdisk but with the seabios settings and bootloader file.

Hi Peter sorry for late reply. Yes if you want to edit clover. Open the efi partition then goto clover and click open file then goto efi partition then open the config.plist in the clover folder. It doesnt find it itself for some reason. clover installer settings as below.

I followed the video exactly and the same has happened to me. I start the new OVMF VM and i get the same error message ("Guest has not initialized the display yet"). I'm running 6.2 stable. EDIT: Changed the VNC to Cirrus and now get the clover boot menu. However, the VM reboots (repeatedly) as soon as the Apple logo is displayed. This can happen when the cpu is not set to core2duo in xml. can you post your xml file here please (just remove the osk key from it though) Here is my XML -- <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MOMAC02</name> <uuid></uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="/mnt/disks/VM02/MOMAC02/OSX-10.11.png" os="OSX"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='18'/> </cputune> <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/2397b50d-5f80-4c96-a331-1962018355cb_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='2'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/VM02/MOMAC02/MOMAC02.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </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='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='connect'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-gb'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </memballoon> </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='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> </qemu:commandline> </domain> Yes osx will not boot unless it thinks it has a core2duo in it. Add this above </qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='core2duo,vendor=GenuineIntel'/> also remove this line or else your mouse will not work at all. <input type='tablet' bus='usb'/> also remove these lines <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> should work fine now if it still reboots at apple sign then change this part <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='2'/> </cpu> to </features> <cpu mode='custom' match='exact'> <model fallback='allow'>core2duo</model> <vendor>Intel</vendor> </cpu> but if you have added the first bit above the </qemu:commandline> you shouldnt need to worry about that. You could use the xml file in the description of the video in youtube if you want and edit that. Let me know if you have any other probs!

I followed the video exactly and the same has happened to me. I start the new OVMF VM and i get the same error message ("Guest has not initialized the display yet"). I'm running 6.2 stable. EDIT: Changed the VNC to Cirrus and now get the clover boot menu. However, the VM reboots (repeatedly) as soon as the Apple logo is displayed. This can happen when the cpu is not set to core2duo in xml. can you post your xml file here please (just remove the osk key from it though)

Ah ok I see. So you are running the clover bootloader but with your bios as seabios. If you installed clover to the efi when you did this you only need convert the xml. if not just put clover in the efi partition as my guide. Now goto a linux template and create a new virtual machine.Give it a random name doesnt matter what. Check machine type is q35. Don't assign any vdisks (set to none) then uncheck start vm on creation. Now goto edit xml of that vm can copy whatever is in between the OS tags will be similar to this. Its important to cut and paste this into a text file. <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/bd14d6e1-92b7-3c50-a16f-329d176d2d9b_VARS-pure-efi.fd</nvram> </os> But dont just copy and paste mine in the above example, because when creating an ovmf vm it it also creates a file in the /etc/libvirt/qemu/nvram folder. That file's name is based on the UUID of the VM (ie mine above is /etc/libvirt/qemu/nvram/bd14d6e1-92b7-3c50-a16f-329d176d2d9b_VARS-pure-efi.fd'). bd14d6e1-92b7-3c50-a16f-329d176d2d9b is the uuid of my vm. So now you can paste the part you put in the text file into your osx vm as that .fd file will now exist in the correct location. (Just follow the last couple of minutes of the second video if tim not clear here with what i say about starting and creating of vm templates to get the ovmf xml code.) After doing that you can delete the vm you just created with the linux template as that was necessary only to create that .fd file. But to be 100% "proper" you should really copy the uuid into the xml aswell to match but will work without. (I guess if you dont copy the uuid there could be problems if the uuid number was ever generated again on the server same as in the .fd file but i doubt it, unless 2 vms were using the vram file at the ame time?) So now you will be using clover but with ovmf not seabios. I have found performance better in my limited testing with geekbench 4. My gpu i passed through for osx has broken so I am awaiting another compatible one so not sure if any improvements there. Hope that makes sense.

Hi Peter I am not sure i understand what you mean? probably me being stupid lol! I dont understand how you dont have ovmf or seabios in your xml?? The xml must use one or the other seabios or ovmf. you must have something like this from archedrafts guide <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> <kernel>/mnt/cache/vm_images/enoch_rev2795_boot</kernel> # heres the chameleon bootloader # <boot dev='hd'/> <bootmenu enable='yes'/> </os> and as it doesn't have the below, its using seabios not ovmf <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/41589327-89c4-099b-b658-e63dc0641e20_VARS-pure-efi.fd</nvram> <boot dev='hd'/> At first I tried creating a usb installer for osx on an 8 gig usb flash drive. Then i installed clover to the usb install flash drive. I didnt want to dd the image (but you could do) so I passed through the usb flash directly to the vm and booted from that. That did work so you can install the osx, to a fresh image that way without a previous osx vm. But then you need to install clover onto that or always use the dd image of the usb install media with clover on it. And in the past I find using the clover installer, problematic installing it into the efi on a vm. Also it takes so long to create the usb, dd the usb to an image (as not ideal using passthough ) and the dd image takes 8 gigs. Then the install of osx then installing clover on newly installed osx. I think for most people it is far quicker and easier to, 1. Install new osx using the normal way with the enoch chameleon bootloader. (or use an existing installed osx one if they have one ) 2. When disk utility partitions and formats vdisk during the install it creates the efi partition and recovery partition at same time. 3. So all that is needed is to open the efi partition after install using EFI Mounter v3 and copy the files there manually. (the files i linked in the video. I made by putting in q35-acpi-dsdt.aml, HFSPlus.efi and then edited the config.plist so they ready to go) 4. Now the clover is in efi of the osx disk image so no other images needed. 5. So all thats left is just adding the ovmf part to the OSX xml <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/41589327-89c4-099b-b658-e63dc0641e20_VARS-pure-efi.fd</nvram> and deleting the chameleon bootloader <kernel>/mnt/cache/vm_images/enoch_rev2795_boot</kernel> Hope that answers your question Peter.

Thanks. Yes your and archedrafts work is excellent and i am glad i can contribute something back