darthdeus

So after deleting all of the config and data and re-installing the container I linked it again, started sync, everything ran well, until it got stuck very close to the point where it was stuck before (previously was at 59219 files left, and after reinstall it's at 59206). I guess I'll try syncing my whole Dropbox to another device, archive some of the contents and try to sync again. I'm not really sure how to debug this, it seems to be doing something, but network traffic is sitting at around 20-50kB/s.

Hi everyone, I think I have the same issue as Grsh and cinereus. I've had my dropbox running for about 2 weeks now, tried restarting it a bunch of times, restarting the whole array and unraid, but it's stuck at the same spot for at least a week. sh-4.3# su - nobody -c 'dropbox.py status' Syncing 59,219 files Downloading 59,219 files... Status says it is syncing, running `top` shows CPU activity, but nothing is changing. I've checked the share disk usage and it's been the same for at least a week as well. Initially I thought this could be because I had a lot of files on Dropbox (around 350GB with maybe a million files), but I've since tried reducing it significantly, but it doesn't seem to affect this in any way. What are my options? Should I somehow delete the container and the share and try re-syncing all over again? As far as I know I didn't make any config changes Screenshot 2020-11-14 at 17.26.14 edit: If I wanted to delete the whole thing and start over, I just need to stop & delete the container, it's config folder, and the directory on the share, right?

Thanks for the tip! Though looking at the page, it seems RX550 is actually not supported as well? https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/amd-gpu.html#lexa-series (they list the whole Lexa series as unsupported). Did you mean RX5500?

Thanks! I'll definitely check it out. Though to be honest I'm still browsing the forum for some more elementary explanation of how to do the GPU passthrough. On the most basic level I noticed that when I switch the "Graphics Card" from "VNC" to my 570ti I can't click on the VM anymore and connect via VNC (which I guess makes sense?). I guess this is as noob of a question as it gets, but how do I actually connect to it then to at least verify that it boots? SpaceinvaderOne mentioned installing SplashtopStreamer to connect remotely, but since that runs as a service in the OS I guess that rules out seeing any boot issues, right? I mean how do I even verify that the thing boots once I change the GPU if SplashtopStreamer is unable to connect? Sorry if this is a super noob question, I've only been using Unraid for about a week and never did any VM management before. I'm happy to read up on anything or watch more videos, but at this point I'm mostly just strugging to find what to read up on hehe.

Ok I found out one place where I was being dumb 😅Looking at a diff of a before/after config it seems that what you linked is exactly the problem. changing it to the original part in the <loader> and <nvram> section works! I guess now also moving onto the GPU. Any idea why the loader/nvram settings change on save? Or maybe how to keep them from changing?

Sorry if I'm being overly dumb, but you mean that my config is correct, or that I have some other config I should share? I didn't change any of the defaults, literally just ran macinabox and installed until it booted, then tried increasing CPU/RAM/GPU, which broke, and here I am Is there some resource I missed? From watching the video it seems like all of this works with the default settings, but maybe I'm even more confused than I thought?

Hey guys, I'm not sure what I did wrong, but after installing & getting everything running I powered off, tried to change the CPUs (4 instead of 2), edited the XML to add back the customized options, and when I try to boot the graphics are broken (the VM seems to boot normally though) Here's my XML config <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina</name> <uuid>554ea9d4-6ec9-430d-86eb-e88f5089abef</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="catalina.png" os="Catalina"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> </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/554ea9d4-6ec9-430d-86eb-e88f5089abef_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> <cache mode='passthrough'/> </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:f3:8d:5d'/> <source bridge='br0'/> <model type='virtio'/> <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-us'> <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='isa-applesmc,osk=???????????????????????????????(c)AppleComputerInc'/> <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> I tried deleting the <topology ... /> section but then it doesn't boot at all. Lastly, I also tried just changing the GPU from VNC to GTX 560ti, but I'm not able to VNC into the machine with that setting either. What did I miss?

I'm trying to setup a VM to run on an uassigned SSD, but when I select the disk under `/mnt/disks/XXX` and save it seems to create it under `/mnt/user/domains` anyway. What's the correct way of dealing with this? Should I just create the VM, edit the config and set it to manual, and then move the file over? (or let it create a new one)