qrexec not connected on HVM

[Vins]

Hi, I realized now that if I attack any devices on the USB port and I connect to the "Standalone qube not based on template", I get the "qrexec not connected" error.
Looking on the web it seems like I need to update the update distribution lists (source lists), but I don't know how.
For now I would like to have the usb wi-fi card recognized on kali-os, but very soon I will also need it on the voip exchange OS. Undoubtedly I will also need it for the copy paste between Hvm.
I read on the web that they recommend installing the tools directly on the AppVm, but I have several Hvm that I want to be able to continue using. Is it possible to use the same Dom0 kernel on Hvm, if something is needed?
Thank you

[thedigit...@gmail.com]

Not being able to use devices on virtual machines is a limitation that I don't know if I can stand.
I remember that it was possible to pass the entire usb controller to a windows machine without having to install the addons or tools. Maybe it's the fault of some updates, sometimes even the second usb controller disappears in the choice of devices in the tray bar.

I searched on the web and on the mailing list on how to resolve "qrexec not connected" but there are only suggestions on using a template based qube.
No information on how to solve the problem and no explanation as to why this problem occurs.

Also tried to pass the USB controller through the panel of devices in the settings of the virtual machine, first it tells me that the controller is in use by Sys-Net, once killed Sys-Net in the other error logs:

2019-05-17 14:29:52.517+0000: libxl: libxl_pci.c:1176:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0

I already had failures with gpu passthrough, in installing bluetooth headphones and now I see that not even the usb controller works on the virtual machine.

Thanks anyway

[awokd]

thedigit...@gmail.com:

> Also tried to pass the USB controller through the panel of devices in the settings of the virtual machine, first it tells me that the controller is in use by Sys-Net, once killed Sys-Net in the other error logs:
>
> 2019-05-17 14:29:52.517+0000: libxl: libxl_pci.c:1176:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0

This should work. Make sure the USB controller you want to pass through
is deselected from sys-net in its Qube Settings/Devices (on the left
side instead of right). You might have to shut it down first. Next, go
to Qube Settings/Devices and attach it to your powered off Windows HVM.
Based on that error message, you'll also have to hit the large
"Configure strict reset for PCI devices" button at the bottom, and make
sure to check the box to NOT require strict reset.

[vins]

Il giorno giovedì 23 maggio 2019 21:20:44 UTC+2, awokd ha scritto:
> This should work. Make sure the USB controller you want to pass through
> is deselected from sys-net in its Qube Settings/Devices (on the left
> side instead of right).

Thanks for the reply.
In fact I tried again with the strict-reset button and the vm at least starts the bootloader. But then again error.
All tests all errors

2019-05-17 14: 29: 52.517 + 0000: libxl: libxl_pci.c: 1176: libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000: 00: 14.0

sudo lspci -nnk -s 00: 14.0
00: 14.0 USB controller [0c03]: Intel Corporation 7 Series / C210 Series Family USB Chipset xHCI Host Controller [8086: 1e31] (rev 04)
Subsystem: Dell Device [1028: 057e]
Kernel driver in use: pciback
Kernel modules: xhci_pci

qvm-pci attach --persistent --option permissive = true --option no-strict-reset = true khal-2 dom0: 00: 14.0
qvm-pci: error: backend vm 'dom0' doesn't expose device '00: 14.0 '
(also tested with 0000: 00: 14.0)

If I try to connect the PCI bridge (root port) the error is:
Domain has failed to start: internal error: No endpoints PCI devices cannot be assigned to guest

(XEN) [VT-D] It's risky to assign 0000: 00: 14.0 with shared RMRR at c8a0a000 for Dom11.
(XEN) MMIO emulation failed: d11v1 64bit @ 0010: ffffffff88c33784 -> 48 0f ae 27 31 c0 0f 1f 00 85 c0 0f 85 9d 00 00


Yet I remember that in the past I worked with a template that wasn't stand alone with interconnected devices. Maybe it was R2, I don't remember.

So qrexec doesn't connect, passthrough doesn't work, I don't understand if it's my laptop or something else ....

[awokd]

vins:

> 2019-05-17 14: 29: 52.517 + 0000: libxl: libxl_pci.c: 1176: libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000: 00: 14.0

That error is from the 17th. Might not be relevant any more.

> qvm-pci attach --persistent --option permissive = true --option no-strict-reset = true khal-2 dom0: 00: 14.0

Try
qvm-pci attach --persistent --option permissive=true --option
no-strict-reset=true khal-2 dom0:00_14.0