bobbintb

I can but it will be a while. Like all the other cases I've read, it boots fine after the initial slow boot. It has to sit for a good long while before it happens again.

It's really not. It's about as simple as it can get and only takes a few minutes. I really don't need to invest in a whole home automation setup with all that hardware just for this. That's actually quite a bit complicated and expensive.

I'm starting to think I need to submit a bug report. There doesn't seem to be anything I can do on my end. If anyone has any ideas, I'm all ears. Thanks.

I don't just yet. I've been busy finishing my masters so I've been pretty slammed. Right now, it's just rudimentary, a wire hanging down with a spare button from some front panel. Just enough for a non-technical user. I have an actual button on the way but it is taking forever to get here. I have an open frame for my server and plan to 3d print a mount. It'll look nice and pretty soon. I've never used an Arduino but know a bit about them. An Uno is kind of overkill for just a button but it should work and you've got a spare so, why not? This is my first experience with any kind of embedded device and it didn't take me long so I'm sure you could do it.

Yes, one thing you can do is set your primary video card to VNC. That way it doesn't actually output to a monitor but you can access the video output through the webui. As Mentioned, Spaceinvader One has several videos on VMs and other stuff. It's a great resource, even for experienced users.

Ah, that's a new one for me! I didn't realize that was there. Cool.

You can change the storage amount, just not through the UnRAID webui. Try this: https://computingforgeeks.com/how-to-extend-increase-kvm-virtual-machine-disk-size/ I don't quite understand what you are asking with the second question.

My VM takes 2-3 minutes before it gets to the TianoCore screen. I've read a lot about this being an issue with VMs with a lot of cores and RAM. However, I saw in a changelog for a recent version of UnRAID that it was related to Intel processors and that it had been resolved. Unfortunately, I am still having the issue with my Threadripper on the latest version of UnRAID. I couldn't find anything in the BIOS settings to help the issue and other solutions involve recompiling. Any ideas? Here is my VM XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='37'> <name>Windows 11</name> <uuid>1e48b9f1-0149-65a1-1d9e-06bdfb84bce6</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>67108864</memory> <currentMemory unit='KiB'>67108864</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='32'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='33'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='34'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='35'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/1e48b9f1-0149-65a1-1d9e-06bdfb84bce6_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </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' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/virtio-win-0.1.215.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8' hotplug='off'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9' hotplug='off'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa' hotplug='off'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb' hotplug='off'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc' hotplug='off'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd' hotplug='off'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe' hotplug='off'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf' hotplug='off'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x10' hotplug='off'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x11' hotplug='off'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:51:1f:d5'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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-37-Windows 11/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <rom file='/mnt/user/isos/vbios/GP107.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x1'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x3'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x23' slot='0x00' function='0x3'/> </source> <alias name='hostdev6'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

I can't believe it's been this long but I have an update. I have a physical power button that will start, stop, and restart my VM. Here is a guide I plan on updating when I get some more time:

Yes, SpaceInvader One has a video on YouTube on to do this. Some are outdated. The one you need has a script that will rip the vbios from the card for you. I'm guessing the video card is your primary video card. That's usually the one that requires the vbios. Just a note, the script didn't seem to work properly for as the vbios was unusually small. I'm not quite sure why it didn't work but I just threw it in a Windows machine and used gpuz to rip it.

I've been wanting a power button for a VM for a while since my UnRAID server is my main/only computer at this point. It runs everything, including a gaming VM that has multiseating for the whole family. But trying to show (and trust) everyone how to start a VM in the GUI is not ideal. I've done WOL with an app and I know there are ways to wake it from sleep but it's just not the same to me. Yes, I know I can just leave it on as well but I've taken to shutting it down since a foreign malicious user or two was attempting to access it while I was sleeping. This guide will be a bit pretty really rough for now. I'm really busy with some other stuff so I'll try to add photos and improvements when I get the time. Hardware needed: Raspberry Pi Pico A button (you can harvest one from an old PC or buy a new one. It should be a momentary switch) 1. Connect your momentary switch to your Pico. It should be two wires, one goes to pin 16 and the other to ground. Doesn't matter which. They should be in one of the corners. (photos to come) 2. Follow this guide to get the basics set up on your computer to program the Pico. You just need Thonny set up and MicroPython installed. https://projects.raspberrypi.org/en/projects/getting-started-with-the-pico 3. Copy this script: from machine import Pin import uasyncio as asyncio from primitives import Pushbutton vm_name = "\'Windows 11\'" start_command = "virsh start " + vm_name reboot_command = "virsh reboot " + vm_name force_shutdown_command = "virsh destroy " + vm_name btn = Pin(16, Pin.IN, Pin.PULL_UP) pb = Pushbutton(btn, suppress=True) async def main(): short_press = pb.release_func(print, (start_command,)) double_press = pb.double_func(print, (reboot_command,)) long_press = pb.long_func(print, (force_shutdown_command,)) while True: await asyncio.sleep(1) asyncio.run(main()) 4. Name the script "main.py" and save it to your Pico. It will run automatically as soon as it is plugged into a machine when it is named as such so name it something else if you are still testing. 5. Go to the following link. Go to the v3 folder and download the directory named "primitives". https://github.com/peterhinch/micropython-async 6. In Thonny, click the view menu at the top and select "Files". 7. Copy the primitives folder to the lib folder on your Pico. 8. Create a user script in UnRAID and set it to run when the array starts. The script is as follows: #!/bin/sh sh /dev/ttyACM0 > sh /dev/tty NOTE: You may have to give /dev/ttyACM0 execute permissions with `chmod +x /dev/ttyACM0` 9. Plug the Pico into your server and run the user script you just made in the background, or stop and restart your array. That should be it. I wrote most of this from memory, so let me know if there are issues. I will improve it and add photos when I get the time but I have school to focus on. The user script just listens on the USB port and forwards anything it gets to the terminal. I don't have a reset button set up yet but may add one later. Currently pressing the button once turns it on, long press will force a shutdown, and double press resets the machine. Theoretically, the button can be programmed to run any command in the terminal, such as a docker. Shouldn't be too hard to adjust the code for that.

I have been trying to find a way to have multiple users use the same computer at once because I didn't want multiple VMs in UnRAID. After some research I found that the term for this is multiseating. So far, I have only found two products that meet my needs. One is called ASTER (https://www.ibik.ru/) and the other is MultiPoint but it is defunct and last available on Windows Server 2016 as a server role. ASTER is pretty good. There are a few minor issues. The others I've seen are for cloud, VDI, or remote. I'm looking for something that will let me plug in multiple monitors, keyboards, and mice. Does anyone know of any other options

I'm having USB issues with my VM. I have one USB controller passed through to my VM and two identical powered USB hubs, each connected to a port on the motherboard. I keep getting an exclamation point in Device Manager for one of the USB devices. If I switch them, the other starts acting up so it's not the hub itself. I can keep trying to uninstall and reinstall the driver and sometimes that will work for a while but it usually just keeps connecting and disconnecting. I'm not sure if it is a hardware issue or not. I'm thinking it is but I'm really hoping it's not. I've included my diagnostics. Hopefully someone can see something that's just misconfigured or something. I've tried looking for a better Windows driver but it seems to prefer the generic driver. tower-diagnostics-20220226-1119.zip

I fixed the multifunction in the XML. I still get no output. I tried VNC but the VNC just stays black if I have both cards. I tried my vbios again, same thing. As mentioned in the OP, I'm not sure it dumped right because it is really small. When I get the time (maybe tomorrow), I'll have to try putting it in another machine and dumping it in Windows or something. I don't think q35 will work. I don't recall why exactly but I think I couldn't get my nvme controller to passthrough with it and I kind of need that for my SSD. edit: I finally got it working. I guess the issue was that the script wasn't dumping the vbios properly. I put it in a Windows machine, used GPUz to dumb the bios, edited it. It worked fine after that. Thanks for the help. I should have figured that out but I didn't think the vbios was the problem.

I fixed the multifunction in the XML. I still get no output. I tried VNC but the VNC just stays black if I have both cards. I tried my vbios again, same thing. As mentioned in the OP, I'm not sure it dumped right because it is really small. When I get the time (maybe tomorrow), I'll have to try putting it in another machine and dumping it in Windows or something. I don't think q35 will work. I don't recall why exactly but I think I couldn't get my nvme controller to passthrough with it and I kind of need that for my SSD.