zeus83

I tried stopping other two nodes and this wouldn't change anything. So I think there might be another reason for this particular machine to syncing slowly. However I can't figure out the root cause, because the setup looks similar to another unraid box, except different hardware.

After 200k blocks it goes awfully slow, may eventually never sync up: root@chia-unraid:~# while true; do date +%x_%H:%M:%S:%N; docker exec -it chia venv/bin/chia show -s -c | grep 'to block'; sleep 300; done 05/19/2021_22:16:25:559310495 Current Blockchain Status: Full Node syncing to block 304564 Currently synced to block: 234976 05/19/2021_22:21:26:192509311 Current Blockchain Status: Full Node syncing to block 304564 Currently synced to block: 235402 05/19/2021_22:26:27:030711131 Current Blockchain Status: Full Node syncing to block 304564 Currently synced to block: 236169 05/19/2021_22:31:27:893406981 Current Blockchain Status: Full Node syncing to block 304564 Currently synced to block: 236561 Wierd thing my other two full nodes (win10 gui & another unraid server) are in the same local network and syncing perfectly fine. Only this new dedicated chia box that I'm having troubles with.

I'm also having troubles with sync in the docker. It's awfully slow and yes I'm plotting on the machine using the same docker. So indeed it may worth trying plotting via docker and move the farmer to the dedicated VM... I originally thought to run 2 dockers - one solely for plotting and another for farming. What do you think guys?

Try to put this section into you VM xml settings: <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='1234567890ab'/> <frequencies state='on'/> </hyperv> <kvm> <hidden state='on'/> </kvm> <vmport state='off'/> <ioapic driver='kvm'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> <feature policy='require' name='svm'/> <feature policy='require' name='apic'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='invtsc'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> <timer name='tsc' present='yes' mode='native'/> </clock>

Hi, First you don't need that many virtual CPUs for a gaming vm. Passing 8 cores might improve gaming experience. Second it worth reading this post which is extremely useful for setting up a gaming VM https://mathiashueber.com/performance-tweaks-gaming-on-virtual-machines/ Third, in games what is your GPU load percentage ?

Well, overall it works but... SAM doesn't work in virtual machine. On the bare metal enabling SAM yields up to 10% improvement depending on a game. Remote play is hardly feasible. I used to use Moonlight / Parsec. Moonlight is not an option for Radeon cards so Parsec remains, but encoding latency is awful. In a game that maintains 100fps the Parsecs barely encodes 30fps (1440p). Switching to 1080p helps a little. But no stable 60 fps still. If anyone know if it's the case with 5700 XT as well? I tried my GTX 1650 super and it performs way better with Parsec... I don't understand how this is possible.

I've decided to put it here because just spent several hours trying to figure out AMD Radeon 6800XT passthrough to my Win 10 VM. Previously I've only worked with Nvidia gpus and experienced zero issues with them. Radeon a bit different story. I'm running unraid on Ryzen 5950X Asus Crosshair VIII Hero. The GPU is Gigabyte Radeon 6800XT (ref). So not all tips may be relevant to your hardware/software. So the hints are: BIOS: disable CSM compatibility mode and leave only UEFI. I couldn't get GPU passed through in Legacy mode. Only use Q35 virtual machine. i440fx didn't worked for me. Couldn't install a driver. Don't install amdgpu host drivers. Couldn't pass through the GPU to VM in that case. Passthrough didn't work on unRAID 6.8 for me (got error 43 always). So I had to switch to unRAID 6.9rc2 on 5.10 kernel. For 6800XT passthrough four devices: Enabling the AMD Smart Access Memory (SAM) didn't work for me. Got error 43 in windows vm immediately (seems like it's not yet implemented and exposed in vfio https://github.com/qemu/qemu/commit/3412d8ec9810b819f8b79e8e0c6b87217c876e32). Encoding delay in Parsec is awful > 20 ms (h.265, 1440p). Something wrong with driver/encoder I think. Didn't figure out what's wrong yet, but saw someone complains on reddit about it as well.

Hi guys, I've recently setup a Hive OS VM and ecountered a couple of issues during this. So I've decided to prepare a quick start guide. This guide won't explain you what Hive OS is and used for, neither it will show how to setup your Hive OS account and crypto wallets. There is a lot of guides on this on the web. [Prerequisite] The only prerequisite is you have to setup your Hive OS account and properly configure at least one farm and worker. You can go through the guide here or just google any appropriate guide you like. [Instructions] Download the latest Hive OS GPU image here . You should then unpack it and put into your isos share temporarily. For me it was a 7Gb file named [email protected] . Normally this image file is supposed to be written to the usb stick, but we instead just use it as our VM disk. You need to copy the image to your VM share. cd /mnt/disks/vm/ mkdir hiveos cp /mnt/user/isos/[email protected] hiveos/vdisk1.img Now let's create a VM itself which will use our Hive OS disk image. Use Ubuntu template because Hive OS is ubuntu based distro. There are however a couple of issues we must to address. First I suggest to leave OVMF bios as default. If the VM won't boot then try the same steps with SeaBIOS. I wasn't able to boot some cards with default OVMF bios. Second it seems that Hive OS doesn't contain the Virtio drivers normally found in Ubuntu and most Linux distros. I could overcome this with setting Primary vdisk bus to SATA . As for CPU and memory don't assign much resources to it. You have to pass your dedicated GPU as well because Hive OS isn't much useful without it. Switch to XML view to change the network adapter, because as I told before there are no Virtio drivers preinstalled in Hive OS. I chose rtl8139 and it worked fine for me. You must remember that whenever you edit anything using the form view the XML part would reset and you'll have to add that part once again. Now we are ready to start our VM. Once VM is started properly you need to figure out it's assigned IP. I use my router admin page for that. Then we need connect to our VM and finish the worker configuration. Since we passed through GPU and didn't configure the VNC we'll use Hive OS integrated shellinabox. Open https://YOUR_IP:4200/ in a browser. Default login is user password 1 . If everything is ok you'll see a welcoming screen like this. Your GPU must be present and identified correctly. It's now time to finish our Hive OS worker setup. Type firstrun and follow the instructions to enter your worker RIG_ID and RIG_PASSWORD . You'd better reboot your VM after configuration finished. After completion you might check your Hive dashboard to see that the worker is online and assign a flight sheet to it. [FAQ] todo

It has just started working for me.