USB Storage does not show up in AppVM after attaching

[entr0py]

I'm stumped. I've successfully used my usbVM to pass both encrypted/non-encrypted partitions to my appVMs on numerous occassions. I can't think of any relevant changes that I've made since my last successful attempt. I did re-create my usbVM with a fedora-23-minimal template but I'm confident? (maybe not) that I've used it successfully before. Could the minimal template be missing a package related to Qubes USB storage?

(using an unencrypted usb2 key storage)
* mounts successfully within the usbVM
* attaches without error to appVMs (tested multiple templates)
* QVMM & qvm-block both show that usb drive is attached to appVM as 'xvdi'
* no messages in appVM `dmesg`
* when attempting to mount, `no special device /dev/xvdi(x) exists`
* detaches without error

* `xl block-attach` does not generate any messages but device is still not available in appVM (don't know if that's expected or not)

Anything else I can try? Thanks!


-------------------------------------------------

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!

[Andrew David Wong]

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

On 2016-05-23 10:51, entr0py wrote:
> I'm stumped. I've successfully used my usbVM to pass both
> encrypted/non-encrypted partitions to my appVMs on numerous
> occassions. I can't think of any relevant changes that I've made
> since my last successful attempt. I did re-create my usbVM with a
> fedora-23-minimal template but I'm confident? (maybe not) that I've
> used it successfully before. Could the minimal template be missing
> a package related to Qubes USB storage?
>
> (using an unencrypted usb2 key storage) * mounts successfully
> within the usbVM * attaches without error to appVMs (tested
> multiple templates) * QVMM & qvm-block both show that usb drive is
> attached to appVM as 'xvdi' * no messages in appVM `dmesg` * when
> attempting to mount, `no special device /dev/xvdi(x) exists` *
> detaches without error
>
> * `xl block-attach` does not generate any messages but device is
> still not available in appVM (don't know if that's expected or
> not)
>
> Anything else I can try? Thanks!
>

Yes, I've experienced the same thing with the minimal template. Using
the full template is a workaround. Tracking here:

https://github.com/QubesOS/qubes-issues/issues/2018

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXQ4XOAAoJENtN07w5UDAwJ8QP/2Od2JG+Os1sfyGDKiZgQw1q
4KnDfUsJMl8bI25ozYnFHO5jRvsQSuGkwwXI8vptJvG+uxv9aYsYsTT0miNpL4ew
MDdjZpogbC5NOWVSsDPviN5bFGCf0h9mx7AkvgcpIb5B7xr03QvmDVlmMZ3CRx8l
HMcY4jiLERRtZOCibRzWNCYWbSNz+9CIxTQs8VxxgSFTROIppQtZCJEd97uvJKQd
c4+m4ckgIDWmY46+8+JnDOEkysvio1xfb7dIvK4iMQTIGxginKxguXqQ/qz79Yy5
Q6fcRGWPHzXxsOSXZsxN4Ot0gNDPRVPEU3fqMJ2d2p8nxVI+DgMnU28M4CKDaOky
3m9u5fEetaREw8D2wk5wwmJnaz6DITgVswby/Q1BQtAHuHv50y6gFQIaGxJ5h5MY
yFSMSVzZslocoMi1gWynm+Cl3kXGtLdOQknn5Hc6WcqjH6m3Q6HnBiodnaW/E9Gy
8kx831r5/abpoP/AtDJSsX1qETaDy8a1P0D7jxBkEZ45xXhEFhDYJq0gjQMlOEua
2tGhc0qAvAtPQd3bXLsgT8IAV58hCf1T4XvMmAk9ccGs/icLxL4xbY2TDWsqWNCp
uS4E6cF5yObqpEjNk/vPuDZJ9A28CUTEFSdSntKwXEpw05+0wyP+75f97MDajJmN
puvNv56aUc4c0Jh4kZVZ
=VxS0
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, May 23, 2016 at 05:51:27PM +0000, entr0py wrote:
> I'm stumped. I've successfully used my usbVM to pass both encrypted/non-encrypted partitions to my appVMs on numerous occassions. I can't think of any relevant changes that I've made since my last successful attempt. I did re-create my usbVM with a fedora-23-minimal template but I'm confident? (maybe not) that I've used it successfully before. Could the minimal template be missing a package related to Qubes USB storage?
>
> (using an unencrypted usb2 key storage)
> * mounts successfully within the usbVM
> * attaches without error to appVMs (tested multiple templates)
> * QVMM & qvm-block both show that usb drive is attached to appVM as 'xvdi'
> * no messages in appVM `dmesg`
> * when attempting to mount, `no special device /dev/xvdi(x) exists`
> * detaches without error
>
> * `xl block-attach` does not generate any messages but device is still not available in appVM (don't know if that's expected or not)
>
> Anything else I can try? Thanks!

Check for other xvd* device (for example xvdj). Also you may try `xl
block-list`, especially look at "state" column - should be "4". Normal
AppVM has 4 disks, so 5th should be your usb stick.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXQ4ZYAAoJENuP0xzK19cs6M0H/3zwFuyjnhhmFrufOK+gppT8
wIBT31lPms6GHP9aV0MAEEFJTW7LmCVFPLFV+e6Rxc+zPn632B+ligZhBjkerb8B
IcbPDGT1SxDz31G3tFA+2TCTJMVdkRVAvXFkhNjZ+L1EcryQYmejheoTAiSyVFRs
/gbABKn8X+zi66r7ziNi0AvhVy0MdzUTrwrKmory1+MtmlNaQsMWcvDmqlodXIKV
z7hB9gC3P7B6zhJqrKbvGSYJLpIPOCCNshhGU59leNHeGTlVAnOx9rZJRCU8rYlQ
a6R2AbD7wL5vX2LDrZ989woNFLE4vz0Voyx1vukqb6+qXn0UQLOdBCchQOBNU6U=
=09du
-----END PGP SIGNATURE-----

[entr0py]

Andrew David Wong:

> On 2016-05-23 10:51, entr0py wrote:
>> I'm stumped. I've successfully used my usbVM to pass both
>> encrypted/non-encrypted partitions to my appVMs on numerous
>> occassions. I can't think of any relevant changes that I've made
>> since my last successful attempt. I did re-create my usbVM with a
>> fedora-23-minimal template but I'm confident? (maybe not) that I've
>> used it successfully before. Could the minimal template be missing
>> a package related to Qubes USB storage?
>
>> (using an unencrypted usb2 key storage) * mounts successfully
>> within the usbVM * attaches without error to appVMs (tested
>> multiple templates) * QVMM & qvm-block both show that usb drive is
>> attached to appVM as 'xvdi' * no messages in appVM `dmesg` * when
>> attempting to mount, `no special device /dev/xvdi(x) exists` *
>> detaches without error
>
>> * `xl block-attach` does not generate any messages but device is
>> still not available in appVM (don't know if that's expected or
>> not)
>
>> Anything else I can try? Thanks!
>
>
> Yes, I've experienced the same thing with the minimal template. Using
> the full template is a workaround. Tracking here:
>
> https://github.com/QubesOS/qubes-issues/issues/2018
>
>
>

Thanks for confirmation + opening issue! I loved the minimal template so much I wiped out all traces of the full template :/


Marek Marczykowski-Górecki:

>
> Check for other xvd* device (for example xvdj). Also you may try `xl
> block-list`, especially look at "state" column - should be "4". Normal
> AppVM has 4 disks, so 5th should be your usb stick.
>
>
>

`xl block-list` shows it as state "3"! No sign of it using fdisk (no abnormal xvd*'s)

#Before attaching...
[user@dom0 ~]$ xl block-list appVM
Vdev BE handle state evt-ch ring-ref BE-path
51712 0 7 4 17 8 /local/domain/0/backend/vbd/7/51712
51728 0 7 4 18 9 /local/domain/0/backend/vbd/7/51728
51744 0 7 4 19 10 /local/domain/0/backend/vbd/7/51744
51760 0 7 4 20 11 /local/domain/0/backend/vbd/7/51760

# After attaching...
[user@dom0 ~]$ xl block-list appVM
Vdev BE handle state evt-ch ring-ref BE-path
51712 0 7 4 17 8 /local/domain/0/backend/vbd/7/51712
51728 0 7 4 18 9 /local/domain/0/backend/vbd/7/51728
51744 0 7 4 19 10 /local/domain/0/backend/vbd/7/51744
51760 0 7 4 20 11 /local/domain/0/backend/vbd/7/51760
51840 3 7 3 25 868 /local/domain/3/backend/vbd/7/51840