connecting an iPhone to a AppVM - 4 non-working attempts

[lik...@gmx.de]

Hi !

Has anyone managed to connect an iPhone to an AppVM. That's the only reason I use an additional laptop (without qubes) to be able to make backups of the iPhone with iTunes.

setup: qubes os v4.0.3, AppVM: windows7.

Attempts so far:
1. Connecting using USB pass-through: https://www.qubes-os.org/doc/usb-devices/
> doesn't work. Device doesn't appear in windows due to lack of usb_proxy in qubes-windows-tools (https://www.qubes-os.org/doc/windows-tools/)

2. iTunes support sync by wifi but only if you've managed to connect the iPhone once by usb. So what I tried was to setup everything in virtualbox (usb passthourgh works there) and convert the vbox-filessystem to a AppVm. (see https://www.qubes-os.org/doc/standalone-and-hvm/)
> Doesn't work, because qubes v4.0 uses thin pools and is not file based anymore. So I don't manage to use the converted file.

3. Rootkovksa proposed using reactos for iTunes, but there's no progress since years: https://github.com/QubesOS/qubes-issues/issues/2809

4. Trying to install windows+iTunes at qubes first and then overwrite the iTunes installation with one that was already been connected with usb on another machine (to use wifi sync) doesn't work. Seems that I'm still missing to replace something.


Any suggestions or hints are very appreciated!!!


Best! P.

[Sven Semmler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Tue, Apr 28, 2020 at 01:37:58PM +0100, lik...@gmx.de wrote:
> 1. Connecting using USB pass-through: https://www.qubes-os.org/doc/usb-devices/
> > doesn't work. Device doesn't appear in windows due to lack of usb_proxy in qubes-windows-tools (https://www.qubes-os.org/doc/windows-tools/)

You could temporarily assign your USB controller to the Windows qube.
This will work for sure (I've done the iTunes/Sync/Restore this way).

Warnings:

-> do this only if you don't need USB for keyboard!
-> if you have USB3 you might need to install an extra driver
in Windows 7 (which doesn't support USB3 out of the box)
-> in some cases (like mine) you need to limit the RAM of
the qube to 2GB or less ... otherwise it crashes*

/Sven

* in my case that's true for all qubes when the USB controller is
attached. No idea why.

- --
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAl6oWZoACgkQ2m4We49U
H7ZduQ/7Bnqu+eff7H4uRZsRcssxlQtwx+HVuurmfP8522WNi9r1mtJRA6lQGDF7
RgNfdrmNbi3/3JqAURLqNOPXakhfHLmzvtK6Bf3N/x4iZWdimarCPLIJt5VPUpB0
6WCiuharpaJ1pPjozJFdettAIh5Wn/W0fD0j+Rk+FVDeoPAlY0a5B7G2sEMkSX2K
k9f0ImCLoasKCjYCauT+Jbb/Cevd/Q5URVyBpd1cJz4/O3bgqvj7r4tp4WnO1OkM
DbFjk7Xx86ntsTFRaknhJP8ZdglbJU4mK6fuzix8mI6qNxsD3dQES4FwBNSFi4DP
GkaxwitmZxQEkox+fDrGClxVxTUoxdL8O33O3vHaP/ermBqx954VRih5TdgMLWrl
c+FMk+fbB5W2wPabq6u5yN20NOB0+VepivY71aih2K8JuOdLHY4UfKUHdoLDoPRv
C/t5pxusDuqxsGbKwnZzoaCNEReI82lNZdBAgGGNRLNFMaMs+mcGobN8sF1kqlN3
LQ6mAnNAMulz21JJTG1OXl6mjwcFwXX5+tl+gHC97UFTeGn1WkbUb2+d51mTnFX6
nKpSPqOrqer1kbLmPP12cryDljvmYFRX4GncJQSU0Z6TPF7PDMLzVt2hY+XBAmC6
xAUJKcvv8BsKxxXMqml/DRTJSKOAZdZuxH7kwEkmRy13sfal66o=
=PX2l
-----END PGP SIGNATURE-----

[lik...@gmx.de]

> On Tue, Apr 28, 2020 at 01:37:58PM +0100, liked2-Mm...@public.gmane.org wrote:
>> 1. Connecting using USB pass-through: https://www.qubes-os.org/doc/usb-devices/
>>> doesn't work. Device doesn't appear in windows due to lack of usb_proxy in qubes-windows-tools (https://www.qubes-os.org/doc/windows-tools/)
>
> You could temporarily assign your USB controller to the Windows qube.
> This will work for sure (I've done the iTunes/Sync/Restore this way).
>

Right. That was my 5th non-working attempt, because I get this error, when trying to attach my USB controler from my Lenovo L380:

Start failed: internal error: Unable to reset PCI device 0000:00:15.0: no FLR, PM reset or bus reset available, see /var/log/libvirt/libxl/libxl-driver.log for details:
2020-04-29 21:03:20.397+0000: libxl: libxl_pci.c:1202:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0

How have you've chosen the correct USB controller?

[Jarrah]

> Right. That was my 5th non-working attempt, because I get this error,
> when trying to attach my USB controler from my Lenovo L380:
>
> Start failed: internal error: Unable to reset PCI device 0000:00:15.0:
> no FLR, PM reset or bus reset available, see
> /var/log/libvirt/libxl/libxl-driver.log for details:
> 2020-04-29 21:03:20.397+0000: libxl:
> libxl_pci.c:1202:libxl__device_pci_reset: The kernel doesn't support
> reset from sysfs for PCI device 0000:00:14.0
>

This will be an issue with the controller not respecting PCI reset. try
with `-o no-strict-reset`. This is less secure, theoretically some state
from the original VM/dom0 can persist to the new VM. In practice, it is
up to your judgement. See `man qvm-pci` for more info.

> How have you've chosen the correct USB controller?

Usually I'll pick a controller, assign it to a VM with no USB devices
attached to any ports and see which ports are assigned to the VM by
plugging a trusted device in. It's not easy to match them.

[Sven Semmler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, Apr 29, 2020 at 10:26:15PM +0100, lik...@gmx.de wrote:
> Right. That was my 5th non-working attempt, because I get this error, when trying to attach my USB controler from my Lenovo L380:
>
> Start failed: internal error: Unable to reset PCI device 0000:00:15.0: no FLR, PM reset or bus reset available, see /var/log/libvirt/libxl/libxl-driver.log for details:
> 2020-04-29 21:03:20.397+0000: libxl: libxl_pci.c:1202:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0
>
> How have you've chosen the correct USB controller?

I only got one. ;-) But it has the same issue yours has ... most of them
do. Try this:

qvm-pci attach win --persistent --option no-strict-reset=True dom0:00_15.0

Assuming your controller is dom0:00_15.0 and your qube is called 'win'.

/Sven

- --
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAl6rRjoACgkQ2m4We49U
H7YZDxAApxVpzqHJVD4YGTAT9g/fWzQCmT2xl7YOu4rrEc7ALCKmxN2oiyFbreBh
i8RTcb8EmoHv/A+iFtSpHrZFKAmj6hjg3mQyCDb0DTiUKNfpE+zs28JBuyDSQC6D
/mIcicvFK6v0kzBHdsRYY5xnlR4wh15W235roYxDnvWysO8+Opr1x0R2fxPPxRBi
EeBz0zMEOh3w+DzQWBVnaOTHSrU/2qGT3AMV6JHw7pHln0/nCYT19yTYSUbSM49q
nZGWpizrMhufyUXZwmv1fGV+yoIcpN3DQL3DvXjlXNVyQf7s+zF1BYdcPYKDTqwy
8Mc9t96R8vi4euak046hlOLk5mwm85znuURGY4rGtLTWIwS9OMfDECnNSWyktJza
HYEUruMExNgxpAGuZ6ehqj3EbV134jG/grsNIOpREWZclrtCxF/rKQl7VTgSo0Pj
sW/jxa8HdhKzCnzA2xS52mJLpxGvsbXfNozc2EO+HXKiQbQJ1HWmAsjCTa8rJmBT
0+HizIzoGi9zCDVG2Y/5xo9/alRQXhZIAPDPMAvuz8JcDXjduCOjq5sWYv1rJmK8
IwBJgcuGkmT+fRVcDJoqAm5I0RdVvzvDrYiSc4ZlG6A1j7mA6k4xfQwbv0FuO3GD
IueJdMpTxqZm2Nq3ghOboNM1KR0j4kvGN/gwCTycH1T2d/1HeNc=
=AG5l
-----END PGP SIGNATURE-----

[lik...@gmx.de]

>>
>> Start failed: internal error: Unable to reset PCI device 0000:00:15.0: no FLR, PM reset or bus reset available, see /var/log/libvirt/libxl/libxl-driver.log for details:
>> 2020-04-29 21:03:20.397+0000: libxl: libxl_pci.c:1202:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0
>>
>> How have you've chosen the correct USB controller?
>
> I only got one. ;-) But it has the same issue yours has ... most of them
> do. Try this:
>
> qvm-pci attach win --persistent --option no-strict-reset=True dom0:00_15.0
>
> Assuming your controller is dom0:00_15.0 and your qube is called 'win'.
>

Sven thank you so much getting closer to the goal which I've been already investigating for weeks. For now I managed to attach my
Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0

to my windows 7 box. After running "qvm-pci attach win --option no-strict-reset=True dom0:00_15.0" I get a message in windows that a new device is found. Unfortunately, windows cannot find drivers for it. In your previous message you warned already to install USB 3.0 drivers. I installed the USB drivers from Lenovo as I'm assuming that there will be a pass trough. Unfortunately, this doesn't work. Windows still is looking for drivers and doesn't find them.

Any ideas to resolve that?

[Sven Semmler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sun, May 03, 2020 at 10:01:40PM +0100, lik...@gmx.de wrote:
> Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0

I happen to have the same chipset you have. But I have never attempted
to attach the Signal processing controller (dom0:00_15.0) to Windows ...
what's your use case?

To make your iPhone play nice with Windows/iTunes only the USB
controller (dom0:00_14.0) is required.

> I installed the USB drivers from Lenovo as I'm assuming that there will be a pass trough. Unfortunately, this doesn't work. Windows still is looking for drivers and doesn't find them.

I am running the "Intel USB 3.0/3.1 eXtensible Host Controller Driver"
Version 5.0.4.43 downloaded directly from the Intel website.

https://downloadmirror.intel.com/22824/eng/Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver_5.0.4.43_v2.zip

/Sven

- --
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAl6woloACgkQ2m4We49U
H7ZaRw//ceNZIn6+9KzkhSldruKhaYiYP+T6dh1YKOQiImEw6l143xFq2Z0oOpzY
qZiPNIPhwz/3Zg2ZoMzwQaOcSBiHnl0O0Fn7TxfAl52CKuUhlSLdMHk5lctc9G7r
qN4cvE2hjUae7ET8AEzn9PnoTC/UeddQG6OtWU2VJHZeI+c+ToxWvNd042Q98lz6
/L4jxSc9TL2jJy0RCxgBiZeWSEIQGJ51xYgFRurfvtE1O4OtdBoHXuQqCWRcCRJr
lZfgEiVnUXJGjpzkLowL2dMwTZ1DTauGDkSlPp3PigFVlSgDb/pOU69E12jFSVfn
V3dOLuk4SnhbjAiH7AcXxlUBQECEDzI8s4XY4NlmeoNQ2IJCQojNcfQX2fCLfbwL
WFpsdlt9RvaYkj6P4ZCc/ZDI628A9nLW1ruQAE9L0wfBxErAQp6n7xGBCh0g38/Q
3WZCA54Cxr+0U2HrnAegL72W8EuWSAUzwz4njIICMbWjxNj89zsn7b3wDfUkh/AM
ry7XJ+YMQALKJT3IEjQZb+ovjt/l2cXEpiElCKSWQ8FLkoYIwy9gqMuFCkEX7SD7
dEwhkvVJ1WRJwrHBwaDOt94cao2GKbUnupinKdNo8GJoabbXP/8+MFMjKQOPwdnd
UDuk+G7ZnArN5pDukkD+iHjQUBjDM3Lasevz9ded7Tb/ieU3uIE=
=vp1j
-----END PGP SIGNATURE-----

[dhorf-hfre...@hashmail.org]

On Sun, May 03, 2020 at 10:01:40PM +0100, lik...@gmx.de wrote:

> Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0

that is not a USB controller.

> Any ideas to resolve that?

make sure to attach the right device.
if you are trying to assign a USB device ...
... look for one with "USB" in the name.

[lik...@gmx.de]

On 5/5/20 12:16 AM, Sven Semmler wrote:

> On Sun, May 03, 2020 at 10:01:40PM +0100, liked2-Mm...@public.gmane.org wrote:
>> Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0
>
> I happen to have the same chipset you have. But I have never attempted
> to attach the Signal processing controller (dom0:00_15.0) to Windows ...
> what's your use case?
>
> To make your iPhone play nice with Windows/iTunes only the USB
> controller (dom0:00_14.0) is required.
>
>> I installed the USB drivers from Lenovo as I'm assuming that there will be a pass trough. Unfortunately, this doesn't work. Windows still is looking for drivers and doesn't find them.
>
> I am running the "Intel USB 3.0/3.1 eXtensible Host Controller Driver"
> Version 5.0.4.43 downloaded directly from the Intel website.
>
> https://downloadmirror.intel.com/22824/eng/Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver_5.0.4.43_v2.zip
>
> /Sven
>
>

Thank you very much Sven. With these hints, I managed to sync the iPhone win a win vm. The puzzle which was missing for me was that I had to detach the usb controller from the sys-usb. After this I could successfully attach it to the win vm. Followed by installing the drivers you suggested, the iPhone was found and could be used.

Have you managed to enable Wi-Fi sync? My assumption was that I only have to sync once using USB and could sync over wifi afterwards. Unfortunately, even after enabling it in iTunes, the iPhone seems not to be found although both devices are connected to the same wifi.

Thanks a lot again!