Leaderboard

v6.8.2 uploaded. Delayed for a few reasons, had problems (and still do) with the nvidia container runtime, worked around it in the end, but not a long term solution looking forward, I'm working like a dog at the moment as my current real life job finishes in 2 days and I'm having to put a ton of extra hours in, wife a bit ungainly at the moment as very heavily pregnant so I'm having to do a bit more for our existing beast, and to add to that bass_rock has been away for work, so kind of a perfect storm of not having much time to sit down with this, although I have been trying to get it working every chance I've had. Anyways, I've tested this version, think everything is working, and I believe all the out of tree drivers are squared away. Last version (v6.8.1) might have been missing the Intel 1gb driver as I hadn't realised that it was different to the 10gb driver.

I agree with the previous post by Ellis34771: I think at the moment ZFS would just introduce unwanted complexity for the majority of home users of Unraid, and think the Lime team would be better adding features such as Server to Server native backup/sync. I realize I might be in the minority here holding this view! 😎

Hi I just build a kernel to support X570 motherboard (mine is msi x570 ace) and latest AMD Ryzen 2 3000 family CPU. 6.8.3 is out, here is the new kernel and some tweaks: Add Vega Reset Patch Add Navi Reset Patch Enable NFSv4 in kernel(God damned, we finnaly get nfsv4 to work) Add R8125 out tree driver. AMD onboard audio/usb controller flr patch. Provide two version (linux-5.5.8 and linux-4.19.108) in case of bug. Notice that linux-4.19.108 still don't have AMD Zen 2 suppport. Download url can be found in the latest comments. For those who want to use NFSv4: NFSv4 have some change compared to v2/v3, it must have root share and the nfs-utils version can't handle it well.You must add this script to UserScript Plugin triggered when array start: #!/bin/bash # Add NFSv4 root echo '"/mnt/user/" -async,no_subtree_check,fsid=0 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash,crossmnt)' >> /etc/exports # Load configuration exportfs -ra # Tunning mkdir -p /var/lib/nfs/v4recovery sed -i 's@/usr/sbin/rpc.nfsd 8@/usr/sbin/rpc.nfsd 32@g' /etc/rc.d/rc.nfsd # Restart Services /etc/rc.d/rc.nfsd restart And if you have trouble mount nfsv4, you can specify mount vers=3 on client. Edit at 2020.01.31 The procedure of compiling kernel(you can compile it in other linux distribute or linux VMs): download kernel sources from kernel.org, notice that should be same or related version of unraid(like 4.19.94 which 6.8.2 used) unarchive the kernel source zip, like kernel-4.19.94/ copy the patches and .config (important!) from unraid server which located at /usr/src (like /usr/src/linux-4.19.94-Unraid/) to step 2 source directory (Optional) copy custom patches like navi patches or others to source directory too apply patches: find . -type f -iname '*.patch' -print0|xargs -n1 -0 patch -p 1 -i use old config : make oldconfig compile the kernel and modules: make -j5 bzImage; make -j5; make -j5 modules installing the modules, then you can find the module directory in /lib/modules: sudo make modules_install Copy the kernel image: cp sources/linux-4.19.94/arch/x86_64/boot/bzImage releases/6.8.2-4.19.94/bzimage (Optional) ThirdParty modules compiling (like nic r8125 outtree driver): enter the thirdparty driver directory compile the module: make -C /lib/modules/4.19.94-Unraid//build M=(pwd)/src modules install the module to direcotry: sudo make -C /lib/modules/4.19.94-Unraid/build M=(pwd)/src INSTALL_MOD_DIR=kernel/drivers/net/ethernet/realtek/ modules_install you can check whether the module exists in /lib/modules/4.19.94-Unraid/kernel/drivers/net/ethernet/realtek/ archive the modules to bzimage: mksquashfs /lib/modules/4.19.94-Unraid/ releases/4.19.94/bzmodules -keep-as-directory -noappend Then you get the bzimage and bzmodules, copy it to unraid server: /boot/

When dealing with multi-function devices (e.g. GPU with GPU + HDMI audio), Unraid GUI will assign a new bus for each additional device by default. This can cause compatibility / performance issues in some cases, most notably but not exclusive to MacOS VM. The workaround is adding multifunction='on' and change the bus + function values in the xml. If any edit is done via the GUI, it will revert the bus + function back to the default method, requiring additional edits. New users are also unlikely to be able to make these manual xml edits. It would be a good idea to enhance the VM GUI to detect and make the appropriate edits in the xml automatically for these devices. E.g. group devices by bus + function and create the bus + function in the xml accordingly (adding multifunction='on' for the first device of a multi-function group). At least, I would imagine it would not too complicated to apply it as a priority to GPU and HDMI audio devices since they have their own dedicated GUI boxes so matching them is rather simple.

You should probably study this explanation of the Use cache settings and carefully consider how you have that set for each of your user shares. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-537383 Post diagnostics and we can give recommendations.

Ah thank you! That worked it is definitely running now! Thanks for such a quick response too! One issue now is that i have 2 servers running under the same Letsencrypt/DuckDNS. Would you know how to go about separating them so they are seen as 2 separate servers when trying to connect? Do i need to make a 2nd docker container for LetsEncrypt and DuckDNS as well under a different Token so that they can be see separately, or is there a more streamlined way of setting it up? Greatly appreciate all the help!

It should be under Settings -> User Preferences -> Scheduler

Good that you solved, all seems ok to me, your optimization of the system should be the same as mine, so no new inputs to give to you

Have you enabled the mover logging? It is off by default.

Note also that both en0 and en1 are builtin=false from your ioreg and you could have issues; see my above reply to make it/them builtin.

Ok, you put the .aml in the wrong folder. Inside ACPI folder create a new directory named "custom" and put aml files in that folder. then check if X86PlatformPlugin is loaded.

So for I have not had any more memory errors or dismounting of the directory. I took the suggestion of Gragorg and moved the thumb drive to another USB port. I also installed from Nerd Pack sshfs-fuse.

I thing I noticed about eBay listings is that after I bought a card which I was fairly positive was counterfeit prior to purchasing, but took a shot at the price that it would work is that the minute I listed poor feedback on the item, they immediately closed that particular listing and reopened it again so that the feedback I left wouldn't appear.

SO, what resolution am I supposed to use? it all looks stretched out. Made this one, quick and dirty, looks sharp on 1920x1080. Something from my garden Banner below.

No. That's done by the webUI....

Just build related issues I believe, nothing that would affect the enduser

Correct.

So I can go ahead and mark you down as a no for for multiple pools?

Seek_Error_Rate is FAILING NOW, this indicates a mechanical issue, disk should be replaced.

Tools -> Diagnostics -> attach zip file Or you can always view the SMART report on the GUI.

It's fine if both are regular HBAs, disks are tracked by serial number.

I’ll give you the second point because I just didn’t use the right words to describe who has been working on the plugin. The LS.IO guys are phenomenal. The first point, the one quoted above, I still stand by. I originally thought the same as you that the 9th Gen Intel QuickSync needed Linux kernel 4.20 and above but it turns out there are several people saying that they are using it with 6.8.0 even though it’s on 4.19. I submit this comment and the following comments on the reddit thread for the 6.8.0 release: Since I don’t currently have a 9th Gen Intel CPU, I cant verify it. If there’s anyone out there that does, it would nice if you could verify that it’s working.

With regards to the 1950X (and Threadripper in general), you might want to watch Spaceinvader One guide on lstopo and numa node. Once you identify the NUMA nodes, these tweaks will improve gaming performance (and playability). Isolate cores from the numa node connected to the GPU Pin cores from the GPU numa node to the appropriate VM (i.e. only the one that uses that GPU). Allocate RAM from the GPU numa node to the appropriate VM Emulator and IOThread pin (especially if you are using vdisk) Do not over assign cores (e.g. if you can limit to 4 cores of the same CCX, that would be best) If multiple CCX is required, spread the core assignment evenly across multiple CCX (e.g. 3 + 3 is better than 3 + 4) You should dump vbios for all the GPUs. The procedure (if you follow SpaceInvader One guide) is very straight-forward. Note: you have multiple GPUs so there's no excuse to download vbios from Techpowerup. One of the most annoying issues on here is downloading the wrong vbios.

Cache Minimum Free is to keep you from overfilling cache. A larger cache will help of course but if you were overflowing 500G there are probably some things you might consider changing about how you are using cache. Post Diagnostics if you want further advice.

Dumping vbios is recommended for all GPUs, not just Nvidia. Nvidia is mainly to resolve error code 43. AMD is mainly to help with reset issue. RX 580, in particular, has reset issue so you definitely should dump vbios for it. The only success story I have seen so far with the RX 580 is when it's NOT being used as a primary GPU (what Unraid boots with). So given your mobo doesn't allow picking any PCIe slot as initial display output, your only solution is to put it in a different slot instead of slot 1. What's wrong with putting the RX 580 in the 3rd slot given you do have multiple GPUs? What's preventing you from dumping vbios? It's a rather simple procedure.

Remember to go to new motherboard BIOS and change the boot order to the USB stick. Otherwise should be swap-and-play.

They did not solve the legal issue with Oracle, they're rolling the dice and hoping they wont be sued. Linus Torvalds own personal take on it: https://www.phoronix.com/scan.php?page=news_item&px=Linus-Says-No-To-ZFS-Linux https://www.zdnet.com/article/linus-torvalds-avoid-oracles-zfs-kernel-code-on-linux-until-litigious-larry-signs-off/

I just went through this a few weeks ago and yes just backup your info with screenshots,etc and the flash. Mine booted right up..I did have other problem with my raid controller but its not likely. I would just try it

I have a very similar setup with a western digital usb drive. You need community applications installed and then unassigned devices installed. You drive should then be picked up in unraid under the "disks" tab (i believe) I have mine enable auto mounting and shared. Now you should be able to browse the disk with samba (//tower/WD_Book is what mine is) The unassigned disk will usually mount to /mnt/disks/ folder so if in the unraid gui you enter the console (top right) and do a "cd /mnt/disks/" then, "ls" That should be your disk. So for example if I have a folder called movies on my usb drive and a share called movies on my array, I want to copy from my usb drive to my array I would use this: "cp -av /mnt/disks/WD_Book/Movies /mnt/user/Movies" copy files and directorys and list items copied from my usb drive to my movies directory on my array. Hope this helps you

Upgraded from 6.6.6. It took me a while to want to move away from the number of the beast.... Alas, security et. al. Seems to be OK. VM boots fine. webgui feels faster/snappier. Running on very old hardware (circa 2008): Gigabyte EP45-UD3P, core 2 quad Q9550, 8GB, Arecca ARC-1880IX-12

Upgraded successfully from 6.8.1 to 6.8.2. I waited for the unraid Nvidia build for 6.8.2 to be released. Everything working fine.

The first mount is a permission issue as you noted. I don't know enough about NFS mounts to offer any help on how to fix that. Others here can help. The second issue doesn't make any sense. If you selected the server and share from the list, it shouldn't fail on not found. Check and see that the spelling and case is correct. Is the server IP address correct for this share? Is the server IP address static?

Updated from 6.8.0 to 6.8.2 - Spun down all the VMs and Dockers first. Went well. No issues with Plex docker (upgraded it too!) Had one issue with the Windows 10VM, but after resetting the GPU and Chrome remote desktop interface, it worked fine again. Thanks!

And change the threshold within FCP for the number of incorrect logins allowed

I think it's better to keep Armor enabled and to remember when it's doing the vulnerability test you'll get the warning.

I’m in a very similar place with my upcoming build. I believe I’ve done a lot of research and can probably help. 1. TDP is really a limit to what the processor will operate at under load. Also, AMD and Intel calculate TDP differently so it’s harder to do a direct comparison. Idle power is usually considerably lower with Intel CPU’s while Ryzen processors tend to only idle a little lower than their TDP (but also have a lower ceiling in terms of power consumption). That 80W Intel processor will idle about 20-30W below that Ryzen processor. It’s important to consider this because if you’re primarily using your server as a Plex/Emby server, it will be at idle most of the time. The P2000 is limited to 75W max but if it’s just transcoding and nothing else, it will consume very little power. **Ideally, the P2000 when it’s sitting idle should be below 10W but due to a bug somewhere in Plex and the P2000, it will stay in an active state even after transcoding is done which will cause it to consume somewhere closer to 20W. Plex is looking into it but who knows when that will be fixed. 2. I’m not saying that UnRAID with Ryzen is unstable or not adequate, but there are some known quirks that are still in the process of being worked out (especially with the X470D4U and X470D4U2-2T). You will most likely need to set the power state to Typical Idle Power or something similar and you’ll be without some temperature sensors that are nice to have but won’t be in until UnRAID updates their Linux kernel. You also might run into issues with your PSU you are using causing your processor to run at very low speeds. This seems to be correctable but it’s something you need to be aware of. UnRAID updates for Ryzen also tend to cause a few more issues on average than Intel. 3. With the Intel CPU and QuickSync, you should be able to easily do 15+ 1080p transcodes with little effort except for a few changes in your BIOS and in your go file. Otherwise, you can run it with any form of UnRAID as long at it has a newer kernel where your iGPU is supported (generally anything 6.8.0rc-1 and above). With Ryzen and the P2000, you’ll need to install the Nvidia version of UnRAID which isn’t updated as fast as the regular UnRAID version (it’s still relatively fast but if you want to update when a newer version of UnRAID comes out you’ll need to wait for the Nvidia guys to bake in their drivers). Granted, with the P2000, you’ll be able to do 20+ 1080p transcodes with ease. I’m personally leaning toward an E-2288G and Supermicro X11SCH-F (I don’t need 10g and I have a Supermicro chassis). It will cost more, have more security patches in the future that will lower performance, and the CPU won’t be upgradeable. With all that said though, QuickSync is incredibly efficient, the CPU will idle below 40W, I’ll get 2 full speed NVME slots, it will be powerful enough to last me about 5 years, and I can always add a P2000 down the road if I need more transcoding power. Ryzen is a very powerful CPU at a very affordable price and if the newer Linux kernels bring forward some much needed improvements and ASRock keeps updating their BIOS to be better, I might end up going that route. We’ll see what the next few months brings.

Thanks for the link. So I've reported this as a bug. That might be an idea to do it like this, will test if that works later.

I would like to see QEMU non-native emulation support. QEMU already has the ability to emulate non-native architectures. Just building all the emulation targets would be awesome. I honestly don't care if that means I have to write my Domain XML from scratch on non-native VMs; I would really like this as an option, especially if your already compiling QEMU for UNRAID. I would also like a drop in method for adding kernel modules, for drivers and the like. Rather than compiling a custom kernel for each use case.

The compiling procedure updated in the main thread.

Hi, configuration is very personal, especially if you passthrough different devices to your vm. However, I'm attaching my config (some parts are REDACTED related to machine specification), so you can have a look at it. Here some advices: 1- ACPI section: I have the following aml files (see attached): SSDT-cpu.aml and SSDT-EC-USBX.aml These .aml file are in the EFI/OC/ACPI/custom folder 1a- SSDT-cpu.aml: this will inject plugin-type = one, usefull to load x86platformplugin instead of acpi_smc_platformplugin; not usefull to manage power states of your cpu(s) but usefull to let load AGPM, to manage the power management of the GPU I'm reporting the source code, for your info, if you are interested: /* * Intel ACPI Component Architecture * AML/ASL+ Disassembler version 20180427 (64-bit version)(RM) * Copyright (c) 2000 - 2018 Intel Corporation * * Disassembling to non-symbolic legacy ASL operators * * Disassembly of SSDT-cpu.aml, Mon Jan 27 08:07:16 2020 * * Original Table Header: * Signature "SSDT" * Length 0x000000B1 (177) * Revision 0x02 * Checksum 0xC3 * OEM ID "CpuRef" * OEM Table ID "CpuPlug" * OEM Revision 0x00003000 (12288) * Compiler ID "INTL" * Compiler Version 0x20190509 (538510601) */ DefinitionBlock ("", "SSDT", 2, "CpuRef", "CpuPlug", 0x00003000) { External (_SB_.CPUS.C000, ProcessorObj) // (from opcode) Scope (\_SB.CPUS.C000) { Method (DTGP, 5, NotSerialized) { If (LEqual (Arg0, ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b"))) { If (LEqual (Arg1, One)) { If (LEqual (Arg2, Zero)) { Store (Buffer (One) { 0x03 }, Arg4) Return (One) } If (LEqual (Arg2, One)) { Return (One) } } } Store (Buffer (One) { 0x00 }, Arg4) Return (Zero) } Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "plugin-type", One }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } 1b- SSDT-EC-USBX.aml: this will inject the EC device and usb power properties, usefull for usb devices which needs more power to charge. I'm reporting the source code, for your info, if you are interested: /* * Intel ACPI Component Architecture * AML/ASL+ Disassembler version 20180427 (64-bit version)(RM) * Copyright (c) 2000 - 2018 Intel Corporation * * Disassembling to non-symbolic legacy ASL operators * * Disassembly of SSDT-EC-USBX.aml, Mon Jan 27 08:11:39 2020 * * Original Table Header: * Signature "SSDT" * Length 0x000000D4 (212) * Revision 0x02 * Checksum 0x67 * OEM ID "hack" * OEM Table ID "EC-USBX" * OEM Revision 0x00000000 (0) * Compiler ID "INTL" * Compiler Version 0x20180427 (538444839) */ DefinitionBlock ("", "SSDT", 2, "hack", "EC-USBX", 0x00000000) { Device (_SB.EC) { Name (_HID, "EC000000") // _HID: Hardware ID } Device (_SB.USBX) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LNot (Arg2)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x08) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBSleepPowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC }) } } } 2- DeviceProperties section: I see that you have a layout-id key, most probably it's the layout id for your audio; not sure if it can be specified as <integer>, mine is specified as <data>, but if it works with <integer> do not touch it. As you can see, I have 2 devices with the built-in key: these are my virtual network cards to show as built-in: this is usefull for the apple store/imessage/etc. to work. 3- Kernel section (kexts): good that you have Lilu, Whatevergreen and AppleALC, check that they are all the latest version; I have 3 more kexts (see attached): AppleMCEReporterDisabler, AGPMInjector and AppleLPCInjector. AppleMCEReporterDisabler: this disables MCE Reporter, because of a kernel panic on boot if you use iMacPro1,1 or MacPro7,1 smbios. AGPMInjector: this injects AGPM, the GPU power manager: if you open the info.plist of this kext you will notice this section: <key>iMacPro1,1</key> <dict> <key>Vendor10deDevice100c</key> <dict> <key>AGDCEnabled</key> <integer>1</integer> <key>Heuristic</key> <dict> <key>ID</key> <integer>4</integer> </dict> <key>control-id</key> <integer>17</integer> <key>max-power-state</key> <integer>15</integer> <key>min-power-state</key> <integer>0</integer> </dict> </dict> The first "key line" is my system (iMacPro1,1); Vendor10deDevice100c: this must be changed according to your gpu: this is the case of a GTX Titan Black: Vendor ID=10de, Device ID=100c; you can find your data with hackintool for example, or with DPCIManager. Heuristic ID is set to 4: somebody suggests a value of 4 for nvidia gpus and a value of -1 (minus one) for amd gpus. Change these lines according to your System, or use the Pavo's utility AGPMInjector app to generate this kext: https://github.com/Pavo-IM/AGPMInjector/releases Note: Pavo's app will generate always an heuristic id equal to -1, also for nvidia gpu; note that in my case AGPM is correctly loaded even with an heuristic id of -1, so not sure if 4 or -1 will is making any difference. AppleLPCInjector: this inject the LPC device. 4- Kernel patch: I see that you have the "avoid a x86 validate topology error": this is usefull to avoid kernel panic if you specified topology in your xml (not 100% sure but if I remember correctly the panic applies only with iMacPro1,1 and MacPro7,1); I would change the count key from 1 to 0 (0 means always), this should not be necessary, but better 0 in my opinion. 5- Misc --> Tools: I have a couple of tools added (optional): VerifyMsrE2 and CleanNvram (see attached); these are shipped with opencore package/AppleSupportPackage; these tools must be put in the EFI/OC/Tools folder. 6- NVRAM --> 7C436110-AB2A-4BBB-A880-FE41995C9F82 --> boot-arg: I have some custom boot args, usefull for debug and also I set the busratio of my cpus manually (optional). 7- UEFI section: in addition to apfs.efi (to scan for apfs disks) and FwRuntimeServices, I have HFSPlus.efi (this is usefull when you have to load the recovery partition, no matter if you have your volume formatted as apfs, recovery needs hfs); the older HFSPlus driver loads the recovery partition faster than the driver included into opencore. I have also AppleUsbKbDxe: this should be used to load the usb keyboard driver, to use the keyboard during opencore boot, does your usb keyboard work even without this driver?? myconfig.plist SSDT-EC-USBX.aml SSDT-cpu.aml Kexts.zip Tools.zip Drivers.zip

Just to be sure this isn't related to the clover bootloader, can you try opencore? I prepared a qcow2 image for you to try with all drivers/kexts you should need. Product name: iMac14,1, preserved serial Inject: nvidia drivers Kexts to inject: lilu, whatevergreen, applealc, agpminjector, applelpcinjector Drivers: apfs, HFSPlus, FWRuntimeServices, AppleUsbKbDxe PS: not sure if driver apfs will be able to load partition, this is coming from my catalina installation, slightly patched, let me know if it doesn't boot Instructions: Download the opencore image from here: <Link sent via pm, since the image contains s.n.> 1- make sure you can access your unraid server shares, where your actual clover.qcow2 image is saved 2- backup your clover.qcow2 image, just to be sure 3- do not delete the clover.qcow2 image, extract opencore.qcow2.zip and copy opencore.qcow2 in the same folder where your actual clover.qcow2 image is stored on the unraid server 4- modifiy the vm template to point to the new opencore.qcow2 image instead of clover.qcow2 image 5- if you have problems just edit again the vm template to point to clover.qcow2 image Let me know

I have zero desire to use ZFS. I've looked at it. If I wanted it, I'd have gone with FreeNAS. I wouldn't mind if other storage options were to be added, but it sort of goes against what UnRAID is. (IMHO) Access logs would be helpful however. I also love the idea of Snapshots.

If someone runs into an exposed unraid system- they should contact limetech and give them the license # so they can contact them and advise them on what to do next. Usually there is an email on file with them. Maybe shut it down to prevent others from pwning it.

Would anyone be able to help me please? I followed the video to the letter and was all working fine until I changed to 4 CPUs and 8GB RAM. The VM starts and the splash screen before the OS boots is fine then the OS boots and the screen goes all funny and repeats itself like 5-6 times at top (screenshot attached). things I have tried.. 1. keeping the topology code as only using 4 cpus 2. removing topology code 3. changing e1000 back to virtio. 4. changed vnc graphics to cirrus. Note: although it displayed 3/4 of the screen, its was just line of white noise. I did it all correctly.. updating the vm template then changing the xml to match but to no avail. I also got 1 error and 1 warning from the VM log (screenshot attched). So my xml here is back to just after changing to 4 cpus and 8gb ram and this is where im at... Not sure if it helps.. my cpu is a Ryzen 1700. Thanks. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina</name> <uuid>f1a24709-f6bc-41b2-bff1-b6043fa42e68</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="/mnt/user/domains/MacinaboxCatalina/icon/catalina.png" os="Catalina"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='14'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/f1a24709-f6bc-41b2-bff1-b6043fa42e68_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='1'/> </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='qcow2' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxCatalina/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxCatalina/Catalina-install.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxCatalina/macos_disk.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <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='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:ea:c4:1a'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <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'> <address type='usb' bus='0' port='1'/> </input> <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='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain>

To clarify my answers, I took "Multiple Array Pools" as literally multiple array pools. You might want to add in multiple cache pools as another option. For my usage, I'd like multiple arrays, not multiple cache pools.

I've been using this plug in for a very long time and absolutely love it. Thanks so much! I have a request. Would it be possible to move the "IPMI Summary" on the Dashboard from the top of the page to the bottom of the page? With the newer look of unRAID the look and layout for the IPMI Summary just down't match and I'd also like to have access to other information at the top of the page. A silly cosmetic tweak I know, but I just thought I would ask. Kind regards, craigr

Strictly speaking step 5 is normally not necessary as KVM can handle .vmdk files directly. To do so you need to enter the path to the .vmdk file directly into the template as the unRAID GUI does not offer such files automatically.

Not sure if you ever got this done, but if anyone else finds this topic, here's how i did it: 1) Stop the VM in ESXI 2) Export the VM as an OVF template 3) Make a folder on your unraid box called /mnt/user/domains/<NameOfVM> 4) Copy the VMDK file from the export folder to the folder you created in step 3 5) Run the following command: "qemu-img convert -p -f vmdk -O raw <vmdkfile> <vmdkfilename>.img". This will convert the file to the KVM/OVirt format. 6) Create a new VM, change the bios to "SeaBIOS", and choose the .img file created in step #5 for the first hard drive. At this point, if it's a linux machine, you can boot it and it pretty much Just Works (tm). If it's a windows box, you've got a couple more steps. 7) Boot the windows box, let it freak out that there is a bunch of new hardware and attempt to install drivers for it. Let it do it's thing - it'll probably reboot a couple times. 8 ) go to add/remove programs and uninstall vmware tools 9) As part of the creation process, you'll end up with a D (or first available) letter drive with the OVirt client VM files (basically vmware client for OVirt). Open that up, go to the client install folder and install it. Reboot. 10) after the reboot, go to device manager and install drivers for anything that wasn't detected properly. All the drivers you need should also be on that D drive disk. 11) Reboot one last time and you should be good to go! That's pretty much it. The only other snag i noticed is that a couple VMs that i converted that had static IPs flipped back over to DHCP (my assumption is because of the change in virtual network hardware), so make sure to check that. Let me know if you (or anyone else) runs into any issues!