SimonF

Does VM Manager just show as a blank page? Does the VMs show on the dashboard? Looking at your VFIO bindings you have bound some parts of the 2070 but not all. I cannot see any thing obvious in the logs.

Here is my repo if you want to use for examples. https://github.com/SimonFair/unraid-lcd plan is to create a client to show Unraid specific info, but not built yet. client.php is my starter for 10 based on a pfsense plugin.

Do you have two of the same device type in the system? When you removed the card did you adjust any vfio mappings you may have had as the pci ids may have changed. VM manager template does not support two of the same devices. But you can use my VM Manager to do that if required. post diagnostics as that will give more info about your system.

So this is a PCIe USB card? Can you provide diagnostics?

As it looks like both devices have the same serial ID you cannot use the device mapping. Just setup a port mapping per device to the correct VM.

It should provide similar functions but I have not used this plugin so cannot say if it is like for like.

What does lsusb show? Provide output lsusb -vvs 001:054 replace bus:device which matches the value that you device has. Is it a serial adapter?

reserved

reserved

This was a function being developed for the next release but was decided best to be a plugin to start with to allow better interations for changes. Currently this is a beta release. the is an existing plugin called virtwold this expands on it to include dockers and LXC. I am in the process to complete changes to make it work fully under 6.12 but currently the search function and help text don't work or don't exist. Two pages are created, first is the settings. Within the settings you can specify which servers are enabled. The interface name needs to be a physical NIC. By default shutdown actions are disabled. The second page is in tools. It allows you to specify the actions allowed. To be able to start dockers you need to have a user defined mac address as one is not assigned until the docker starts and changes. Values for the enabled field are

You maybe be able to use custom kernel from here until 6 13 is released https://github.com/thor2002ro/unraid_kernel

Yes domains is the vm share, appdata is the container path. configs are normally stored in system for both.

If you remove the mac address on the NIC it will remove the definition from the guest. You will still be able to access via VNC.

attach Diagnostics when the VM is started.

Do you have the connect plugin installed? and is it on the latest?

look for cups in CA.

Yes also check CSM is not enabled. These are from the manual for the MB. CSM Enable to launch the Compatibility Support Module. Please do not disable unless you’re running a WHCK test. Have you tried different settings for the option below? Legacy USB Support Enable or disable Legacy OS Support for USB 2.0 devices. If you encounter USB compatibility issues it is recommended to disable legacy USB support. Select UEFI Setup Only to support USB devices under the UEFI setup and Windows/Linux operating systems only.

Check for bios updates, do you have fast boot enabled? are you booting uefi?

New drivers released a few days ago. mm268/build 248

Any reason why you are not using host passthru for the CPU? First one is missing the feature lines below are the ones you have on the 2nd working one. <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>qemu64</model> <topology sockets='1' dies='1' cores='1' threads='1'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='lahf_lm'/> <feature policy='disable' name='svm'/> </cpu>

Yes it maybe release as 7.

Have you change anything else in the xml, maybe post your xml

that is fine the file should be in the hooks/qemu.d dir now.

No that is the code for pre 6.10 that gets inserted into the qemu file. If you run the following it should create the hooks /usr/local/emhttp/plugins/usb_manager/scripts/install.sh Looks like it is not recreating at boot because lbvirt is not mounted until services start will look into it.

if you are running < 6.10 the lines are added to qemu in the hooks dir. it should have the code inserted near the top. #begin USB_MANAGER\nif ($argv[2] == 'prepare' || $argv[2] == 'stopped'){ shell_exec("/usr/local/emhttp/plugins/usb_manager/scripts/rc.usb_manager vm_action '{$argv[1]}' {$argv[2]} {$argv[3]} {$argv[4]} >/dev/null 2>&1 & disown") ; } #end USB_MANAGER Also check the permission on the file that it is execurtable. ls -l you have the x in the flags. can you also check usb.ini in /usr/local/emhttp/state/ Entries should look similar to this [001/111] ishub = "" connected = "" parents = "1-9,usb1,0000:00:14.0,pci0000:00" bus = 001 dev = 111 ID_VENDOR_FROM_DATABASE = "Dresden Elektronik" ID_VENDOR_ID = "1cf1" ID_MODEL = "ConBee_II" ID_MODEL_ID = 0030 USBPort = "1-9.3" class = "interface" ID_SERIAL = "dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE" isSerial = "1" isSerialPath = "usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE-if00" bNumInterfaces = 2 isSerialDevPath = "/dev/ttyACM1"