coppit

Community Developer
  • Posts

    496
  • Joined

  • Last visited

Everything posted by coppit

  1. LOL. Did you pull the trigger on Threadripper as soon as the passthrough fix was announced? I ran into exactly the same issues today. (Stuck in D3, and need to reboot after each VM boot.) System Specs: Threadripper 1950X ASRock - X399 Taichi 64 GB DDR4 memory Lots of drives 2x GTX 960 I'm trying to pass through one of my GPUs to a Windows 10 VM, and the other to a different Windows 10 VM. I have a 3rd GPU in the first slot, and I use that for my unraid bootup. Before the server rebuild, I was able to pass the NVIDIA GPUs through with my Xeon processor as long as I did the ACS override. I would hear the fans spin up when the VM started. No such luck this time. The first problem I ran into was the ROM error, so I followed the instructions in this video on how to download a ROM and edit it to work with KVM. I didn't try blacklisting the devices in the kernel, but I did try disable_idle_d3=1 to the boot options. No luck. Attaching my VM XML. juggernaut-2017-11-04.xml
  2. My VM won't even boot if I uncomment the part in the XML below. Does anyone have an optical drive successfully passed through? An example would be helpful. <domain type='kvm' id='2'> <name>Windows 10</name> <uuid>453d7cd7-17b8-f8df-99fc-ffc048246eef</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>7340032</memory> <currentMemory unit='KiB'>7340032</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/453d7cd7-17b8-f8df-99fc-ffc048246eef_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <runtime state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:31:66:08'/> <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 port='0'/> <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-2-Windows 10 - David/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='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x00' slot='0x1b' function='0x0'/> </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='0x00' slot='0x14' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </memballoon> <!-- Won't boot if this is added <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </controller> <hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host13'/> <address bus='0' target='0' unit='0'/> </source> <alias name='hostdev0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev> --> </devices> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
  3. I got the sense that it was a "feature", where it uses the low-res stream until you click on it. Regarding high CPU usage, definitely avoid any kind of conversion.
  4. For what it's worth, they seem to be quick to give away licenses. I bought the software soon after I got V1 of the container working. I emailed them about a technical question, and mentioned that I containerized the software (hoping that they would be more likely to answer my question). They answered my question and threw in a license without me asking. Yeah, the licensing is annoying. I thought that simply restarting after internet was back was enough to fix it, but I just checked and I had to re-enter my key. Ug. That's putting it mildly. ZoneMinder's interface is just broken. Stuck in the 90's. (And bad for an 90's web interface, even.) I'm not surprised that ZM doesn't have good camera support. It seems not to be actively maintained. I also noticed high CPU with one camera. Near as I can tell, it's converting the video to still frames to do the motion detection, then converting it back. Xeoma in contrast has the lowest CPU usage I've seen for the 4-5 different camera programs I tried. Not at all! As you can tell, sometimes it takes me a while to get back to folks on the forums.
  5. From https://github.com/HandBrake/HandBrake/issues/672: No. I created a feature request for it: https://github.com/coppit/docker-handbrake/issues/2
  6. Yeah, quotes in quotes don't work. Try one of the following: "{plex.derive{' [$vf, $vc, $ac]'}}" "{plex.derive{\" [$vf, $vc, $ac]\"}}"
  7. Did you put the password in the config file as per the documentation? https://hub.docker.com/r/coppit/mumble-server/
  8. Hi everyone, I just pushed a pretty big set of fixes to the container. There were several file ownership, process owner, and file permissions problems that I fixed. Hopefully <fingers crossed> the UI is working well now. One thing you can do to see if it's saving your prefs properly is see if it shows the "getting started" dialog, then stops showing it after restarting the container. You can also check for "<entry key="getting.started" value="1"/>" in <config dir>/java_prefs/prefs.xml. Please try it again and let me know if you're still seeing issues!
  9. My guess is that Xeoma is trying to delete "older" directories. I recommend getting in touch with the Xeoma team. This is a Xeoma question, not a container question.
  10. Well that's vague. It's clearly finding your /input directory. Does the amc.log in the container say anything interesting? Run: docker exec -t FileBot bash -c 'cat /files/amc.log' | less Use whatever your container name is instead of "FileBot". Wild guess... Did you forget to map the /output directory in your container settings? To verify that the mount it correct, put a file in the output dir in the host, then run this: docker exec -it FileBot ls /output and make sure the file is listed inside the container too. Well, are you trying to tell the GUI to output the files into the nonexistent path /Music?
  11. Look in your logs. There was a version bump to the conf file and sh file. You need to update your versions of the files and restart the container.
  12. The only difference I see is that my filebot.sh says this: MOVIE_FORMAT="Movies/{n.$QUOTE_FIXER} ({y})/{n.$QUOTE_FIXER} ({y})" and yours says: MOVIE_FORMAT="Movies/{n.$QUOTE_FIXER} {' CD'+pi}" What does your filebot.conf look like? Mine looks like the default one. I also have USER_ID set to 99 and GROUP_ID set to 100 in my container settings. While you're in there, you could add a space to the coppit/filebot container name, then delete it. That will force it to check for an update, and download it if there is one.
  13. I'm not sure I trust the "last updated" info on the webpage. I ran strace on my server, and attached it to the noip process. Every 20 minutes it woke up and talked to http://ip1.dynupdate.no-ip.com. The web page finally did change after a couple of hours. (Maybe sooner -- I wasn't watching it carefully.) You can do it yourself to see if it's waking up and doing work. Run: strace -rp $(pgrep noip2)
  14. I don't have that. My guess is that there's a dot file sitting in there from when you browsed the recordings with a computer. And when Xeoma tries to delete the dir, it can't because that file is there. Run this on your server to see if there is something in there: ls -al /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-26 If so, rm it.
  15. Can you send me your log? Also, what is the output of this? Use your container name instead of "HandBrake". docker exec -it HandBrake ls -l /tmp/HandBrake.conf That message is coming from the component that monitors the directory for changes. Double-check that COMMAND is defined either in your config file or the env vars of your container.
  16. I'm not running Ryzen, but on the off chance that your issues are not Ryzen-specific, here's my XML. I'm gaming with less memory and CPUs, and it works well enough most of the time. I have occasional crackling audio. When I diff my file against yours, I see that you don't have any caching on your vdisk, and that my clock, pm, and hyperv settings are different. Good luck! <domain type='kvm' id='1'> <name>Windows 10/name> <uuid>453d7cd7-17b8-f8df-99fc-ffc048246eef</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>7340032</memory> <currentMemory unit='KiB'>7340032</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/453d7cd7-17b8-f8df-99fc-ffc048246eef_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <runtime state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:31:66:08'/> <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 port='0'/> <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/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='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x00' slot='0x1b' function='0x0'/> </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='0x00' slot='0x14' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
  17. Yeah, I was thinking that maybe the browser wasn't running some javascript efficiently or something. Interesting that you're seeing the same problem with a full VM. So it's not docker-specific... How does the system utilization look (CPU, network) on the stats tab of your UI? If network is high, you could try installing and running nethogs. (I use nethogs-0.8.5-x86_64-2_slonly.txz) The only other thing I could think to try is to disable plugins and other stuff you might be running on the server to see if something fixes it.
  18. Yeah, I only have 2 cameras, and the cost was comparable to Blue Iris. Plus there's no guarantee that they won't charge you for a future upgrade.
  19. Please read the section on licensing here: https://hub.docker.com/r/coppit/xeoma/ What kind of networking are you using? Try host instead of bridged.
  20. Yeah, sorry. There was a bug in the creation of the default config file that is created during the first run. It will be fixed in the version I'm releasing later today. Note that you also need a line like: VERSION='latest'
  21. Not released yet for Ubuntu. https://launchpad.net/~stebbins/+archive/ubuntu/handbrake-releases
  22. Sounds like these might be related. I don't get this problem at all. What browser are you using? I'm tested with Chrome and Edge on Windows 10. You might also want to try disabling any plugins you might have.
  23. What did you have in mind? Maybe put the files you want to process in a dir, then run "docker run ...", and it just runs once and exits? It should be hard to pass a -e runonce=1 option to docker, and use that to have it not go into monitoring mode. But the command line is going to be pretty long...
  24. Well, given that the line with the error is the line that specifies /input to FileBot, I think you'd better get those ducks in a row before worrying about why /input isn't being processed. Like I said, you're probably literally missing one character from the end of the previous line. If you're still having problems, paste your entire filebot command here, like I did with mine. Also, open the log, make note of the last line, then rename one of those files in the input folder. Wait a few minutes, then PM me the log lines that were added after the previous last line.
  25. Did you configure the port, /archive path, and /config path? Bridge or host networking? Are you saying that when you click on the logs icon, you see that output? If so, are you sure you're using coppit/xeoma?