Qubes R3.1 (Some Windows Partitions available in Dom0 File Manager, unavailable to assign to VMs)

[Srini]

Greetings!

I have an NTFS partition labeled "Official". This is available to mount in Dom0 (via Thunar File Manager) and is unavailable while trying to assign to any of the qube (VMs) .

However, I have another NTFS partition "Windows" and "RECOVERY" which is available both in Dom0 (via Thunar File Manager) and also available to assign to any of the qube (VMs).

Also, tried refreshing using udevadm, but it did not help.

Appreciate any help in fixing this.

Thanks & Regards,
Srini

[Andrew David Wong]

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

It is strongly recommended that you do not run the file manager in
dom0. See point 3 of this section:

https://www.qubes-os.org/doc/security-guidelines/#tocAnchor-1-1-10

Also, I don't know how much or little you trust these disks, but in
general, it is strongly recommended that you do not attach any
untrusted disks in dom0. The safest thing to do is to use a USB qube,
assign any untrusted disks there, then attach them to other VMs using
qvm-block (which is what Qubes Manager does when it "attaches/detaches
block devices").

You can read more about creating and using a USB qube here:

https://www.qubes-os.org/doc/usb/#tocAnchor-1-1-2

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

iQIcBAEBCgAGBQJXaDqaAAoJENtN07w5UDAwhWwP/j4uIOOEC5FHigdMgmWPP6A4
aulUhdoRk8l2dWp8Y1Zp++xwVJm0H9M2BZefwao7UeLuSDm4LPiXkUoXCXc2esaC
uVP62l0yd+7ZTs9o3zSTgurlr5DlCGmafo4QDOoPRkQl8m/bwQW7FNbjAK1mvivf
TG8BZ7f8a5Ma8Phsjbj0XIDn69FKGt8Cn1YBR5D0cpmaimpVjVFgCRbU79g/f2eu
CcAFw6Q5F1pult++ZZmqoPcVEarm6EQO2H8CqdsIXJhEzcxz2h9aKL9y03fgKKGs
DvSjYa2O/NtUcOkSuE7qJKVucii/s0fUKgVbwUSyOXG1IDh1CI9U+5i0U8159FNW
SkeYuq/0z7x4M9/aAQudtTQuMu9q5UnfABOG15Lv5UuMSI4qVOwe0+SbyqNoW0yZ
DSbBpEIUzHOCtA672tyKGdif1RuXCc5ymolXV5kDxViC+/HhfkiD3ofkT0pDB6ax
rL+pX1OBOZKoHLeyP532xT8XfGoQgrunYWBP1BXfmXRx5XFba5Uhuif2GI5BRaBg
FLXR2Nvum2n01cbi1Lp/NP+2yBrz6q82II4cU+AkHRjhS4D0pSLsgXDGfz7nh+8Z
5vdk2wCVIjl1AVcCUc3QxxXIlhI45Ae77+XEkBB+Dg5m6DCwmNfbiyURE+FjTF1C
y2QnFPhfP0HfQmpucWBl
=Vq9e
-----END PGP SIGNATURE-----

[Srini]

Dear Andrew,

Thank you for sharing the details. I have gone through them and will work to have a USB qube.

However, the issue of a partition unavailable to assign to a qube from Qubes VM Manager still exists - Given the fact that I am able to see/access that partition from File Manager in Dom0 (I understand the security risk) - All windows partitions were available to any qube earlier, only some are now available now.

Any suggestions on getting this fixed please?

Thanks and Regards,
Srini

[Andrew David Wong]

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

On 2016-06-22 03:14, Srini wrote:
> Dear Andrew,
>
> Thank you for sharing the details. I have gone through them and
> will work to have a USB qube.
>
> However, the issue of a partition unavailable to assign to a qube
> from Qubes VM Manager still exists - Given the fact that I am able
> to see/access that partition from File Manager in Dom0 (I
> understand the security risk) - All windows partitions were
> available to any qube earlier, only some are now available now.
>
> Any suggestions on getting this fixed please?
>
> Thanks and Regards, Srini
>

In that case, it sounds like this issue is unrelated to Qubes. Rather,
it sounds like there's something different about the one partition
that is now unavailable relative to the others. I recommend searching
for information about managing disk partitions in Linux.

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

iQIcBAEBCgAGBQJXarj4AAoJENtN07w5UDAwMwgP/1rarHifOFG/uXuSLbjUQkQs
sf95OxRFRx1NKur9UjtGT/KBSH/2Xpwh6BI3veBbmW2CiCfN5w5VmbGlg+I+jmDE
ln23XcYtwTL346M/Gw9mh/ORa5HhC1w8faqLwpuxhdBh/rIEytT1vodT809XpT7x
MCcBxrf+EPb4BjOkEWPGRZwfeUYmbU2Rr2IYZ9IgC9JtCNaU6cHDGbCPsZYZk+Hx
EQ0jh2nh+94MAseGiEVk9xn1mdMzwkvtkGz3m1hdRWzT0T0b7QZGuT2auOhmf9NV
j1sTIG7SnCpvhi84nx6au4P0znFkzdieZN44KmePgwVwnZXYzz6QJTUdZwXzfgXY
bj7GD/rvoaGYUEl9XEBQxEpt1ujzD/bN3ul54dniKq+EZM0Tqxbx+14gam/FIjXW
Nutx/fQkHl0l9LZDl6SQqQyNS2O4LlCCwru/XkZNiymZt2CGAoZE8n1kn214mYk5
jLlE/evFmK0KxE6Di7o94SbzcXfwq9PC5tVuC7PgrSE3QukOQG4IC9JWhpy2MQ44
uDMhn56imBKlXARb5q53nSfjpylejfe8UZWzahgQG5tcO90c5gBQL4FzEbR9JKwZ
FpucOhSdczFJlMH2WUMGCnyxEqV8XHJN5CRxw0UU7q9iP1z0x+TwXBoFVQl+gg+t
JhYmZCTWAXP6joOzLI+S
=Nkbp
-----END PGP SIGNATURE-----

[Gustavo Lapido Loureiro]

I know this is kind of an old post, but since I'm dealing with dual booting qubes with windows, maybe this helps others.

The issue may be due to an hybernated windows partition, that is, windows (begining with 8 onwards) has this fast boot feature turned on, so when you turn windows off it actually hybernates it, so the next boot is faster then it would be otherwise.
The problem is that you can't mount an hybernated windows partition, so you have to turn that fast boot feature off (google it) and eventually force hybernation off thru windows cmd (powercfg -h off)