mikegg

I don't have a discord server anymore, but i will do my best to help. The instructions on the github page has instructions on how to run the container. Have you had a look at the image specifically? Do you have anymore info on what's not working? Any logs?

I've made the code available on Github with some basic instructions https://github.com/micke/unraid-vm-manager

Allright, so i've done some more tests and now i'm even more confused than i were before. To recap, i'm having problems with IO in windows with my SSDs. "Average response time" goes up to 16000ms as seen here (https://imgur.com/a/BMLXHYv). What i've tested since my last post is: Booting into the SSD directly that i use to pass-through to the VM. Same issue Swapping from connecting the SSD to a sata port on the M/B to connecting the SSD through a LSI 9211. Same issue Clean install a windows VM on my cache drive instead (another SSD drive). Same issue I've exhausted all the troubleshooting options i can come up with, so any and all ideas are highly appreciated.

I susccessfully resized the vm image but could not for the life of me resize the partition/container/level in macos. It let me set 100GB which was maximum and it proceeded to go through 5 steps and said it was scuccessful but it never actually did anything haha

That's probably a bit easier solution than trying to resize the container (apfs seems a bit confusing and annoying imho). Creating a new drive, mounting it and using carbon copy cloner worked great, a important and extra step is making sure that you bring the EFI files with you otherwise it wont boot. It might be possible in CCC directly if you play with the settings, i dunno. Thanks for the help dude!

I'm running the latest nvidia web drivers and the latest clover and i had problem booting with two monitors connected, tried the fixes mentioned in this thres without any of them working. What ended up working was swapping the dvi cable to the second monitor to a displayport one. I'm wondering though, as i wanted to be smart i created a 25GB image formated with apfs to act as a base image. I then copied it and expanded it to 100GB in the unraid ui and proceeded to try and use `sudo diskutil apfs resizeContainer disk1s1` to resize it to the full 100GB without any success. Do you have any experience in resizing apfs systems? @gridrunner?

Good shout, will likely try that tomorrow. I think i did this before and didn't see the issue then. But i don't think i looked at the average response time but went more on feeling. Passing the ssd through like i do makes it possible to also boot on the SSD directly. But don't want to disturb peoples plexing right now

@david279 Thanks for the help but no dice. I've tried; * Changing the currrent VM to Q35 - still same issue * Changing bus to VirtIO - won't even boot * Reinstalled windows with Q35 and disabled cache - still same issue * Reinstalled windows with i4 and disabled cache - still same issue

Thanks for trying to help, i tried checking the alignment of the partitions and it says that it's aligned. Also, it's not my diagnostics file you've been loking at since i haven't posted any yet I've already set it like that but i don't think it's working as it's evident that my read speeds are RAM speeds ? Here is my xml for the VM: <domain type='kvm' id='1'> <name>Windows 10 Gaming</name> <uuid>a97e8d42-ddc6-a463-54d6-8a2b4918092a</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='10'/> <vcpupin vcpu='3' cpuset='11'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='14'/> <vcpupin vcpu='7' cpuset='15'/> <emulatorpin cpuset='6-7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/a97e8d42-ddc6-a463-54d6-8a2b4918092a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='block' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source dev='/dev/disk/by-id/ata-INTEL_SSDSC2BW240A4_PHDA428200RD2403GN'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_1709_English_x64.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:9d:30:39'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10 Gaming/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/gtx1080.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <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='0x05' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

This is what i get when running crystaldiskmark on my 64bit windows 10. As you can see the response time is crazy slow

I'm also experiencing really horrible ssd performance in my windows vm. I'm gettin 250mb write which is OK but it feels like it's lagging as soon as it's doing any io. I have no clue as to how to debug this so any help would be appreciated

Hiya guys! I wanted to quickly share a project i've been working on and see if there is any interest in me releasing all the files and maybe writing a build guide for others to use. I love unRAID and the flexibility of the VM system. I quickly replaced the need of having two machines at home by just having a unRAID server that i can game on by passing through my graphics card to a VM. I'm quite lazy though and having to go into the webUI each time i wanted to start a VM quickly became a big enough hazzle so that i had to do something about it. What i came up with is a small controller using a D1 mini together with some switches for mechanical keyboards (i'm quite addicted to mechanical keyboards and even build my own custom boards). The D1 mini has one button per VM i want to be able to control plus one button for shutting a VM down and one button for destroying a VM. The D1 mini connects over Wi-Fi and only needs power over USB. It does not have to be connected to the servers USB ports. I designed the case to be glued together kinda like a puzzle and ordered it from a company here in europe that cut it for free with a lasercutter and they raster engrave the OS icon on the mirrored backside so that i can put a activity led behind it that shines through. The VM is started by pressing the button for the VM which then sends a WOL signal to the server where i've installed the "Virtual Machine Wake On Lan". There is also a companion docker app running written in ruby which exposes a super simple API that the controller use to find the state of all the VMs but also to issue a shutdown or destroy command to libvirt. When the button is pressed the VM is started and the activity led flashes slowly. If you press a button for a started VM the VM is selected and the activity led flashes in a quicker rate and you can then press either the shutdown or destroy button. All in all the whole project is pretty cheap. The D1 mini i just a couple of bucks on aliexpress. The case is not needed but makes it a bit prettier on your desk. I used the service available at http://cotter.co to cut the case in acrylic. At the time i ordered they offered free cutting time and material in silver mirrored acrylic, but they calculate the price live when you upload your design.

Great video as always. I'm interested in the performance while using encryption. Anything to report so far?