xeven

Fair answer, thanks for the insight. Do you feel that qcow2 has helped reduce disk space usage?

Ok so I figured out the VT-x issue. The scripts that I was supposed to run did not run properly, but now it's working. Your XML shows that your 100GB disk is a qcow2 type? Any reason why you went with qcow2, more curious than anything. But really, thanks for all your help!

Yeah I tried SATA as well and still didn't seem to pick it up. Was there anything else you needed to do in the XML? Nevermind, it seems to be working now. Although my main issue now seems to be that the ESXi controller says I don't have VT-x enabled, which wouldn't make sense as it's a KVM which needs VT-x???

Thanks! So it turns out I did not follow the instructions as I assumed I had. This fixed it for me. My only issue now seems to be that I cannot see/create data stores. I created a second drive in the VM options (also USB) and it doesn't even detect it. Would you happen to know how to create a data store in order to place the VM's? You mentioned you created a 100GB img, was this within the VM edit options? This is what I have done,

I am attempting to build out a lab and ideally would like to do this with ESXi as a nested VM on my unRAID server. The steps I've done so far are: Created the scripts mentioned in the Spaceinvader One (hxxps://www.youtube.com/watch?v=2-saWn6ZbHc) Followed the steps in the video linked above Made the necessary changes to the XML also mentioned in the video linked above I'm able to get ESXi to boot, but when it comes to installation it is asking for the disk location to continue the installation. As seen in the screenshot, it isn't locating any media to perform the install on. Is there something I'm missing in order to get his up and running? Thanks!

I've been having an annoying problem lately where the container seems to be changing the timezone (TZ) on it's own. For example, I only use the container to permit download's at 2am (schedules set). The container at random times, is changing the TZ (set as UTC -5 in unRAID settings) and in turn triggers my schedules that I've set. I can see the TZ is changed because the logs for the container are not the current time as my server. I can't see any indication of the container restarting when looking at the logs and when I make any modifications to the container, it does state the correct TZ in the build settings. Worth mentioning, that even changing the name of the container and applying settings, will force the container back into the correct TZ. Normally it wouldn't bother me, but it's becoming annoying that downloads are starting outside of my allowed window. Has anyone come across this before or know of any solutions?

Not sure if you figured this one out yet, but I spent about a month on this. With no results so I rebuilt my VM's. From scratch... after that it was back to normal but quite frustrating. Then just the other day it happened again so this time I just powered down the unRAID server, unplugged from the wall and hit the power again to clear any charge left over. Put everything back and booted up again and all was working. I'm not claiming any of my black magic worked. But it has seemed to fix the issue this time and damned if I don't do the same thing again when it happens the next. Sorry for the not so technical fix you were probably looking for. Good luck!

Cross-post from Application Support for more visibility So I had unRAID setup well with the following hardware: Gigabyte h170n-wifi i7 6700K 16GB I have been running unRAID 6.3.3 on a trial license for the past 10 days making sure it works for me before I dive in. Last night I performed the update to 6.3.4, for no apparent reason, but to keep up with releases and I had a message in unRAID telling me so. This morning however, my main Windows 10 VM which was using Intel integrated graphics and Intel onboard audio, had the audio just stop working. All it says is in Windows is the device cannot start. In the VM logs it sats the following: 2017-05-24T02:19:25.679624Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. 2017-05-24T02:19:25.679737Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. I did some searching but could not find a way to "reset" the device which I assume would put it back into working order. I have stubbed the systemlinux.cfg file with label unRAID OS menu default kernel /bzimage append vfio-pci.ids=8086:a170 modprobe.blacklist=i2c_i801,i2c_smbus initrd=/bzroot Here is a section of my device list, which shows the audio device I'm trying to reach IOMMU group 8 [8086:a144] 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) [8086:a121] 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) [8086:a170] 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) [8086:a123] 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) I backed up my unRAID usb drive, wiped it and reloaded 6.3.3 which still did not make a difference. I even made a new VM from scratch to see if that would resolve. Nothing has brought back the audio. This is my first post here so far, as I've been able to piece together what I've needed to get everything running in regards to passthrough and Skylake CPU's. So if there is additional information needed from config files let me know and I'll post them. Kind of at whits end on this one and I was really enjoying unRAID. Hoping some folks around here have faced the same issue or similar and have some other suggestions for me to try.

So I had unRAID setup well with the following hardware: Gigabyte h170n-wifi i7 6700K 16GB I have been running unRAID 6.3.3 on a trial license for the past 10 days making sure it works for me before I dive in. Last night I performed the update to 6.3.4, for no apparent reason, but to keep up with releases and I had a message in unRAID telling me so. This morning however, my main Windows 10 VM which was using Intel integrated graphics and Intel onboard audio, had the audio just stop working. All it says is in Windows is the device cannot start. In the VM logs it sats the following: 2017-05-24T02:19:25.679624Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. 2017-05-24T02:19:25.679737Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. I did some searching but could not find a way to "reset" the device which I assume would put it back into working order. I have stubbed the systemlinux.cfg file with label unRAID OS menu default kernel /bzimage append vfio-pci.ids=8086:a170 modprobe.blacklist=i2c_i801,i2c_smbus initrd=/bzroot Here is a section of my device list, which shows the audio device I'm trying to reach IOMMU group 8 [8086:a144] 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) [8086:a121] 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) [8086:a170] 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) [8086:a123] 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) I backed up my unRAID usb drive, wiped it and reloaded 6.3.3 which still did not make a difference. I even made a new VM from scratch to see if that would resolve. Nothing has brought back the audio. This is my first post here so far, as I've been able to piece together what I've needed to get everything running in regards to passthrough and Skylake CPU's. So if there is additional information needed from config files let me know and I'll post them. Kind of at whits end on this one and I was really enjoying unRAID. Hoping some folks around here have faced the same issue or similar and have some other suggestions for me to try.