sonofdbn

OK, user error here. I just noticed that there is a + sign, it's just that it's right up against the left margin of the page, and it's not visible when my browser window is not at full screen. But I do feel the GUI could be improved so that the + sign is more readily noticeable. I'm using Firefox. in case it's a browser specific issue.

Having said this, the + sign might not be the solution, though. I'm trying to passthrough one of those portable disks in a USB case. It appears as /dev/dis/by-id/usb-JMicron_Tech_000000778899-0:0. But if I enter that as the path for the secondary vDisk, it gets promoted to the Primary vDisk on boot (this shows on the VM config page) and the VM fails to boot (perhaps trying to boot from there) and shuts down. I've tried both USB and VirtIO as the vDisk Bus.

A short while later:
After trying to revert to my original setup, it seems that the original hard disk was Bitlocker encrypted and I needed to enter the recovery key because a USB device had been added to the configuration. So that's a probably reason for the VM appearing to fail. If you don't enter anything at the Bitlocker screen the VM shuts down. I saw this only because I started the VM with the console. I'd experiment further, but it's such a pain entering the Bitlocker key using the function keys, and I'm not sure if there's a simple copy and paste that I can do into the console window. Anyway, if entering the Bitlocker key is required every time I add or remove the USB drive, it's not a practical option for me.

Will try to assign the USB drive as a network share instead.

I tried deleting and then recreating proxynet, but that didn't help. Then I tried creating a new network, proxynet2. I assigned my Swag and Nextcloud containers to it and they seemed to be OK. Then I reassigned the containers back to proxynet and lo and behold, they're now working.
 
To tidy up I deleted proxynet2. So far, so good.
 
If things run fine for a few days, I'll mark this as solved.

So I did a little test: stopped docker containers and VM. Set the graphics card in the VM to the Nvidia card (no VFIO binding) and then booted up the VM.
 
It seemed to be running but I couldn't connect via RDP. So I thought about stopping the Nvidia plug-in. At that point I thought it might be a good idea to see what the the Nvidia plug-in is meant to do, and went to the support thread. I didn't understand everything, but in the first post there was this warning:
 
"Please be sure to never use one card for a VM and also in docker containers (your server will hard lock if it's used in a VM and then something wants to use it in a Container)."
 
Looks like my idea is horribly risky, so I've abandoned it.

Problem solved here:
 
 
Essentially the problem is an issue with libtorrent 2.x, which is used by qbittorrent, which I was running. Solution was to roll back to an earlier version of qbittorrent. See details in the quoted thread.