SimonF

Looks to be ok to me. I would turn of start/resume VM as you will be unlikely to need it. Which USB model are you using in the VM

Can you provide the results of cat /tmp/gpujson

Looks like it should be possible. https://forum.proxmox.com/threads/serial-port-between-two-vms.63833/ I dont have the XML to enable as yet, also socatis not install within Unraid so would need to get a package for that also.

Pro is the same as lifetime, but on the old license model.

Here is command and example php btrfs subvolume snapshot '.$readonly.' '.escapeshellarg($subvol).' '.escapeshellarg($snapshoty). subvol is path to snap. snapshoty is the name of the snapshot. readonly is -r if you want the snapshot to be readonly. case 'create_snapshot': $snapshot = urldecode(($_POST['snapshot'])); $subvol = urldecode(($_POST['subvol'])); $readonly = urldecode(($_POST['readonly'])); if ($readonly == "true") $readonly = "-r" ; else $readonly="" ; $DateTimeF = findText("{", "}", $snapshot) ; if ($DateTimeF == "YMD") $DateTime = "YmdHis" ; else $DateTime = $DateTimeF ; $ymd = date($DateTime, time()); $snapshoty = str_replace("{".$DateTimeF."}", $ymd, $snapshot); # check_to_dir($snapshoty) ; $slashpos = substr(strrchr($snapshot,'/'), 1); $directory = substr($snapshot, 0, - strlen($slashpos)); if (!is_dir($directory) && $snapshot != $subvol) mkdir($directory, 0777, true) ; $result = NULL ; exec('btrfs subvolume snapshot '.$readonly.' '.escapeshellarg($subvol).' '.escapeshellarg($snapshoty)." 2>&1", $result, $error) ; snap_manager_log('btrfs snapshot create '.$snapshot.' '.$error.' '.$result[0]) ; if ($error=="1") $error_rtn = false ; else $error_rtn=true ; echo json_encode(array("success"=>$error_rtn, "error"=>$result)); break; Auto script. https://github.com/SimonFair/Snapshots/blob/b4ff445c44f3618a74d2737873c3efadfda43a38/source/include/snapping.php#L228

Is this your flash drive? Bus 001 Device 005: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 You have it defined in the JasonVM. mv /usr/local/sbin/qemu /usr/local/sbin/qemu.old This will allow you VM manager and the VMs will not autostart. edit the VM to remove this section. <hostdev mode="subsystem" type="usb" managed="no"> <source startupPolicy="optional"> <vendor id="0x0951"/> <product id="0x1666"/> </source> <address type="usb" bus="0" port="1"/> </hostdev> mv /usr/local/sbin/qemu.old /usr/local/sbin/qemu Now you should be able to start your VMs.

Yes

Are they connected via a hub, looks like maybe power is being removed from them. Unraid gets text from lsusb, usb manager gets from udev but includes more detail. Have you changed anything over last few days?

Sorry for the late reply just looked at the Diags but they seem to be after a reboot so cannot see any errors.

Hi I did a quick test on my test server. I dont use HA except for testing this is what i have added to my yaml. wake_on_lan: switch: - platform: wake_on_lan mac: 52:54:00:DA:18:68 name: Debian2LXC And button added to UI. Apr 7 09:56:16 computenode Unraidwold[26103]: 2024/04/07 09:56:16 Found 52:54:00:da:18:68 LXC DebianLXC2 My settings.

If you have a PCI card you should passthru that to the VM. In system devices bind that new card to vfio. I dont have a dedicate PCI USB, but like my A770 click the check box next to the card. Then the bind button will allow you to save the setting. You will need to reboot the server for that to take effect. Then in the VM you should see the card. in this section on the VM Template. Other PCI devices. Select the USB card and update. Now when the VM starts the whole card is connected to the VM and any USB devices connected will be on the VM. For devices connected to the card they do not need to be in the VM template and should not even show as the card is not bound to the host but the VM.

The gui will not show anything except connect outside when connected as the plugin functions are not being used. What does cat /tmp/vmaddxml show

6.13 implementation is slightly cbanged /usr/libexec/virtiofsd is now a symlink to /usr/local/sbin/virtiofsd wrapper. Rest is the same so no change functionally just where files are.

Last idea I have a presentis to see if turning off guest reset helps. create a temp file i.e. nano /tmp/vmaddxml and add the text below. Change device ID to match if not still 055 <hostdev mode='subsystem' type='usb'> <source guestReset='off'> <address bus='001' device='055' /> </source> </hostdev> Detach the usb device from VM. Then run from the command line virsh attach-device "Adam Driver" /tmp/vmaddxml Since 8.6.0, the source element can contain guestReset attribute with the following value: off all guest initiated device reset requests are ignored uninitialized device request is ignored if device is initialized, otherwise reset is performed on device is reset on every guest initiated request This attribute can be helpful when assigning an USB device with a firmware that crashes on reset.

Looks like there is a serial component, try using connect as serial, but his may mean other parts are not mapped as there are 3 interfaces for the USB device. I will have to do some research to see if I can find other solutions if that does not work. Do you have an option for a USB PCI card you can pass thru to the vm and connect the device to that?

Not sure as yet, not sure why the hub lines are there not seen that before in a standard xml. can you provide lsusb -vvvvs 001:055

You should be able to swap mb with no issue.

Did you add this entry to the xml? <hub type="usb"> <address type="usb" bus="0" port="2"/> </hub> There a lots of errors keep apearing for the Simucube how is it connected, Is there enough power. Bandwidth is only showing as 12mb is that enough? can you send udevadm info query -a -p /sys/bus/usb/devices/1-11.2

can you post diagnostic and I will look at it tomorrow.

Yes

Strange I would expect to see an error

Have you enabled serial in the mapping? Also looks like you have the USB defined in the VM Template. can you provide the output from this command. cat /usr/local/emhttp/state/usb.ini | grep -n6 virsh

Fixed in 6.12.10

Looks like that is in use by the system you may need to look at acs overide settings or post diagnostics

Do you have a 02 00.0?