I’m trying to figure out my options here and a bit lost.
I have windows 10 qube without internet and I wanna transfer files into it, but without compromising on security, so I don’t wanna install QWT in dom0.
In order to use localsend afaik I need to install it on both sides, but how do I install it on a windows qube - I got no idea.
Any help please?
1 Like
You can use loopback device (any file opened with losetup), veracrypt container or physical flash drive to attach it to windows qube and copy files to/from.
1 Like
Thanks, but I can’t make that losetup thingy work.
I didn’t know I can attach usb without QWT either.
With the losetup, I tried to:
dd if=/dev/zero of=‘/home/user/storagetest.disk’ bs=1M count=512
losetup --show ‘/dev/loop1’ ‘/home/user/storagetest.disk’
attached the showed up device to the win qube, but I don’t see anything in the windows qube. I can’t see it even in the disk management inside of the win qube.
What am I doing wrong please?
I just tried to connect a usb stick and it says:
qrexec not connected
1 Like
In dom0 running qvm-features windows-vm-name stubdom-qrexec 1 should enable usb passthrough without installing qwt.
2 Likes
I thought qvm-block can attach the loop device to Windows qube without QWT, maybe I was wrong.
Anyway, open Disk Manager inside Windows qube and check if unformated disk is visible or not. Or you can format the loop disk in the GNU/Linux qube and attach it formated.
1 Like
One option mentioned here:
1 Like
Thank you! It worked perfectly!
1 Like
Which approach?
I did it with the usb, but it’s very slow.
I couldn’t make it work with the losetup, I tried it as I describe above, but when I attach it to the qube even linux vm, I get an error of:
QubesDaemonAccessError got empty response from qubesd
Maybe you could help me with this, as it looks like this would be much better approach than the usb. How is it working for you exactly?
Looks like a bug to me.
I do not use Windows qube without QWT. I think Windows virtualization in Qubes OS is already kind of inferior to VirtualBox and other solutions. Without QWT it would be even worse.
Also I see no real issue having QWT, considering that only Windows-running part can (theoretically) be compromised, it cannot affect the Qubes OS host system anyway,
But it does work with other linux qubes for you doesn’t it? For me even with other linux qubes it just didn’t work and produced the above error for some reason.
How you do that exactly, can you share please?
Yes, it works for me for gnu/linux qubes and Windows qube (with QWT, but it can be irrelevant).
Mostly the same way as you said:
in linuxqube:
- create file of some size, e.g. file
/home/user/mydiskwith size10GiB sudo losetup --show /dev/loop5 /home/user/mydisk
After that you should see a new block device in Qubes Device tray widget.
in dom0:
qvm-block attach windowsqube linuxqube:loop5
Alternative - attach with GUI widget, but I use script.
Now I have a new disk in Windows that I can format. Maybe I formated it in linuxqube, I do not remember that detail.
Note: do not try adding any read-only flags at all steps, because Qubes OS has bug with it in case of Windows target qubes.
I’m able to see the block one I sudo losetup command is fired, but when I try to attach the block to linux qube it just QubesDaemonAccessError on me.
I’m doing the exact same thing as you are, yet it doesn’t work for me with the error of above, how is that possible?
Maybe you forgot some step in between? Maybe I need to install something, some package?
Maybe you should file an issue ticket on github.
And please provide more information (do you see block device in qvm-block, post its output about this device, or screenshots).
I probably did something wrong in the previous qube itself, because I tried the same on the new qube and it worked, thanks, but only with linux vms, with windows it probably needs the QWT, that’s kinda sucks
Try attaching loopback device to Windows qube while it is powered off. It should work without QWT, because it’s just a block device.