relink

That post was actually what inspired me to try LXC. But I think I might have found part of my issue. In my excitement to get everything setup, it never dawned on me to create a user inside the container 😅 so I had done everything as root. I ended up nuking that container last night since I also started having an unrelated issue with PostgreSQL too. Im going to start fresh. I will post back with how everything worked out.

Is it possible to run CUDA in a LXC container? Having an issue and I'm unsure of where to start troubleshooting. I have my Quadro P400 exposed to my Ubuntu 22.04 container and can see it from nvtop inside the container. Driver in the container is the 535 branch, the exact same version that is installed in unraid. Inside the container I have installed CUDA 11.2 and cuDNN 8.1.0. Both seem to be installed fine. The issue is the app I need the GPU for says that it has loaded all the libraries but that it cant load the GPU… I don’t know if its a permissions issue or what. For those curios im trying to setup the Nextcloud app Recognize.

I didn't want to change that, I know I cant use a bind mount or anything like that, I already went down that rabbit hole. All I want is to store the named volume somewhere other than inside my docker.img file. EDIT: So I was completely unaware that in Unraid 6.9 the ability to get rid of the Docker img file and use a directory instead was introduced. That completely solves this issue right there. I'll just screenshot what containers I'm currently running and migrate over to using a directory instead of a vDisk. So long as everything goes well, then problem solved.

The title pretty much says it all. I am trying to install the Nextcloud-AIO container from CA which insists on using a named volume to store pretty much everything except your personal files. From my understanding Unraid by default will store named volumes inside the docker.img which I absolutely do not want to do. The Nextcloud AIO github has a "manual install" process that supposedly allows you to use a bind mount instead, however the manual install breaks nearly every feature that makes the AIO setup so nice in the first place. So that seems kind of pointless. I have already searched the forums and everyone keeps sharing this link to a install guide; https://myunraid-ru.translate.goog/nextcloud-aio/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp However, nowhere in this guide is this issue addressed.

That definitely seemed to have been the culprit. I have been running on and off for over 2 days and that issue hasn't happened again since.

Ok, im off to try again. Thank you for your help. *fingers Crossed*

<memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> In the context of the earlier comment I assumed this went along with the Unraid share setting. Should I ensure this is changed to `<nosharepages/>` regardless of what the share setting is?

Ok, so this is definitely a KVM/Host issue. I decided to scrap Ubuntu entirely and installed Arch. I did nothing in Arch aside from setup user accounts, networking, time zone, and other basic stuff. I didn't even mount the share, it was in the VM config, but not mounted in the guest. Arch was literally just sitting there doing absolutely nothing and this issue still happened.

Damn, no go. I’ts still crashing, this time it was only running for about an hour. Completely reinstalled Ubuntu again, this time I changed the mount from virtiofs to 9p. I also took the opportunity to expand my vdisk and switched to RAW instead of qcow. I have no idea what’s going on

Ahhh, ok. I did it through the GUI so I never saw that part. I’ll give it a shot as soon as I can get to my computer and report back. on a side note, isn’t 9p mode significantly slower?

I can certainly try it, can’t hurt. I’m not sure what your talking about here. All I did was add the share in the GUI when creating the VM and then added it to /etc/fstab. Maybe I missed an important step or option?

Anyone? Even any suggestions on what I could check? Im still dealing with this. And it actually seems to be less than 24 hours, maybe 12 or less.

I have no idea whats causing this so I'll try and provide as much information as possible. I have a VM running Ubuntu Server 22.04, it seems to run just fine for hours on end, but not one day has gone by where I went to sleep or to work only to find the cores assigned to the VM at 100%, and the VM totally unresponsive. Unraid Version 6.11.5 AMD Ryzen 5 2600 80GB DDR4 Diagnostics Attached (Taken while the VM was locked up) VM Info: OS: Ubuntu Server 22.04 CPU: 3C/6T Host Passthrough RAM: 8GB GPU: VNC Nvidia Quadro P400 (Passed through with it's audio controller) Storage: 40GB Virtio Vdisk qcow (On nvme cache) Virtiofs mounted directory on a 2TB unassigned SSD. VM Use: The VM only runs Nextcloud 25.0.2 & NGINX. PostgreSQL and Redis are both running as docker containers on unraid. The Virtiofs storage is set as the Nextcloud data directory. Aside from SSH & the Nvidia drivers there is nothing else running on this VM that isn't part of the standard Ubuntu Server installation. I have completely formatted and re-installed the guest OS 4 times and this issue still happens. I'm really not sure why... VM XML: serverus-diagnostics-20221227-1719.zip

I didnt know that, but now that I think about it Debian is one of the 100% Foss distros so that makes sense. Thanks for pointing that out, I actually hadn't seen the latest reply yet. So unless I'm missing something, it looks like my only option is a VM if I want HW transcoding, especially nvenc. I cant think of a single Docker image I haven't tried in the last 2 weeks.

I'm surprised I didn't see this mentioned yet, but is it possible to expose a GPU to this container? I'm desperately trying to find a way to expose my Quadro P400 to Nextcloud so I can enable hardware trasncoding in Memories.

Have you had any luck with this? I have been trying to use rclone mount with vfs_cache to do something similar and having no luck at all.

Did you ever get Untangle working in KVM? I was literally just talking about doing this exact same thing this weekend. Sorry, I know this is an old post but what are the odds of running across a post about exactly what I was getting ready to do.

That was the problem, my unraid box handles a lot, including DNS for my entire network.

I didn’t even know there was a ticket system 😅 but I’ll do that. I ended up buying a new pro license and tying it to some pos flash drive I had laying around just so I could get my work done last night. I’d really like to suggest to Lime Tech that when a license issue arises that maybe unraid could revert to a shortened trial mode, something like 5days or so. Something long enough that you can get in touch with support to get it resolved. Right now that felt like a bit of a “middle finger” to just be dead in the water with zero ways to get back online other than to buy another license and use another flash drive.

I already contacted support, but I doubt I'm going to hear back before morning. I accidentally blacklisted my USB. I have 2 servers and recently bought a new USB for one of them and I transferred the wrong key to the new USB and now I cant start my array on the other. I'll buy a new key if I need to, I'd prefer not to as it was a Pro key, but I just need to get my unraid server back up asap. Theres has to be something I can do?

Hmmm. I tried your XML with the VNC portion removed and still I'm getting nothing, monitor wont even wake up.

Some help would be greatly appreciated, I have been at this for over a day now, and tried 2 different GPU's with the exact same results. My unraid host is: Ryzen 5 2600 80GB DDR4 Unraid 6.10-rc4 I have setup macOS Monterey using the @SpaceInvaderOne Macinabox container. I left everything to default, and got the VM up and running no problem. I used the built in VNC to get macOS setup, create an account, etc. I then changed the allocations to 4 cpus and 12GB of ram, ran the helper script, and started the VM to verify the changes took, and they did. So using VNC macOS runs fine. I am trying to passthrough my AMD HD7870 to the macOS VM, this card is still fully and officially supported in the latest versions of macOS, and I have used it in several bare-metal Hackintoshes before with zero issues. I have the ACS override patch enabled and set to both, I went to "System Devices" and checked both the GPU and its Audio to stub to vfio and rebooted. I then dumped the vbios and added the GPU, vbios, and audio to the VM. Here is the problem, if I remove the VNC graphics adapter and start the VM I just get a blank screen on the monitor attached to the HD7870, the monitor doesn't even wake up. I have tried both HDMI and VGA (Using DVI to VGA adapter), Id try DVI but I cant find my DVI cable right now. However if I keep both the VNC adapter and the HD7870 then I get the boot picker and macOS boot process on the VNC adapter and while the VNC adapter is showing the boot process the HD7870 is doing nothing, the monitor doesn't even come out of standby. Once macOS has finished booting the VNC adapter just continues to show the last part of the boot process forever, but now the monitor attached to the HD7870 wakes up but all I see is the default macOS Monterey purple wallpaper. I installed the AMD vendor reset patch and rebooted unraid, now when I boot with just the HD7870 I still get nothing same as before. But when I boot with VNC and the HD7870, I still get nothing on the HD7870, and the VNC adapter now just shows the message "Guest has not initialized the display (yet)." I tried the exact same steps with an RX570 and got identical results. I'm not really sure what else to try at this point, either of these GPUs should have literally been plug and play with macOS... Below is the VM log and unraid diag with the VM running using VNC and the HD7870. XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-3-Macinabox Monterey/.config' \ /usr/local/sbin/qemu \ -name 'guest=Macinabox Monterey,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-Macinabox Monterey/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/5ad5f709-3506-4953-b339-152a9fa799c3_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-4.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=on,host-cache-info=on,l3-cache=off \ -m 12288 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":12884901888}' \ -overcommit mem-lock=off \ -smp 4,sockets=1,dies=1,cores=2,threads=2 \ -uuid 5ad5f709-3506-4953-b339-152a9fa799c3 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=35,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":8,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x1"}' \ -device '{"driver":"pcie-root-port","port":9,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x1.0x1"}' \ -device '{"driver":"pcie-root-port","port":10,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x1.0x2"}' \ -device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ -device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ -device '{"driver":"pcie-root-port","port":11,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x1.0x3"}' \ -device '{"driver":"pcie-pci-bridge","id":"pci.7","bus":"pci.1","addr":"0x0"}' \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Macinabox Monterey/Monterey-opencore.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.2","drive":"libvirt-3-format","id":"sata0-0-2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Monterey-install.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.3","drive":"libvirt-2-format","id":"sata0-0-3","write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Macinabox Monterey/macos_disk.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-1-format","id":"virtio-disk4","write-cache":"on"}' \ -netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=38 \ -device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:3b:a6:7d","bus":"pci.3","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0"}' \ -chardev socket,id=charchannel0,fd=39,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"max_outputs":1,"bus":"pci.7","addr":"0x1"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.0","id":"hostdev0","bus":"pci.5","addr":"0x0","romfile":"/mnt/user/isos/vbios/HD7870_vbios.rom"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.1","id":"hostdev1","bus":"pci.6","addr":"0x0"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/005","id":"hostdev2","bus":"usb.0","port":"2"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/003","id":"hostdev3","bus":"usb.0","port":"3"}' \ -usb \ -device usb-kbd,bus=usb-bus.0 \ -device '************************' \ -smbios type=2 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-04-20T14:58:25.992004Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.992094Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-04-20T14:58:25.993776Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.993795Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-04-20T14:58:25.995221Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.995239Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-04-20T14:58:25.996604Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.996621Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] qxl_send_events: spice-server bug: guest stopped, ignoring 2022-04-20T15:01:55.412615Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] serverus-diagnostics-20220420-1104.zip

I got Monterey up and running perfectly fine, allocated some more CPU cores and RAM, tested again, still worked just fine. Now I am trying to pass-through my AMD HD7870(along with its HD audio) as the 2nd GPU with VNC as the 1st and I get stuck at the Apple logo, the progress bar gets about 1/3 full and then never goes any further. I also tried with the HD7870 as the only GPU and it also wouldn't boot into macOS. The HD7870 is still fully and officially supported by Apple as macOS compatible, and I have used it multiple times in bare-metal Hackintoshes. This card should just work™ without needing to do anything special. This is normally the point where I would take my Opencore USB to another system and add the "verbose" boot flag and try to start troubleshooting. However, I have no idea how to access the "config.plist" file with this setup. Is there a key I can hold down at the boot picker to get verbose output? Does anyone have any tips on how I can get this VM to boot with the GPU passed through? I have made plenty of bare-metal installs using Opencore before, but it's a little easier to know where something went wrong when you spend hours making the config and adding kexts yourself.

Got it, I hadn't considered it from that angle. I only ran it once so far and all my data is still intact. Luckily I had the foresight to only test it on a show that is easily replaced if needed. At this point can I safely delete the copy on the cache disk and not affect the copy on the array? I think ill take a bit easier of an approach to this for now, and use a spare SSD in unassigned devices for these movies/shows, copy them over, and then add a ".plexignore" file to the originals so Plex doesn't index the array copy and the SSD copy, only the cache copy.