Win7, qvm-copy-to-vm, QubesIncoming location?

[Martin L. Fällman]

New Qubes user here. Running a Win7 VM for many work tasks. Once I set it up I could copy-to-vm just fine, with a QubesIncoming folder showing up and everything. Then I domain-joined the W7 install and got a new user account, the user account I set up during install was renamed “admin” and I don’t use it unless I have to now.

 

All of a sudden, copy-to-vm doesn’t work as expected. The file is clearly sent just as normal. But I can’t find it anywhere on the W7 hard drive. What’s weirder is, if I try to send it a 2^nd time I get the error message

qfile-agent: Fatal error: File copy: not overwriting existing file. Clean QubesIncoming dir, and retry copy; Last file: test.txt (error type: File exists)

 

So, my guess is that it’s written somewhere to the W7 disk, but qfile-agent is confused as to where exactly it should end up, and it’s probably written to a dir that Windows for some reason doesn’t even see. Is there anywhere in the settings for the VM where I can change the incoming directory to match my current user profile?

 

(I’ve tried to re-install the Windows tools as well; didn’t make any difference.)

 

Thanks!

 

MARTIN L. FÄLLMAN
PROTECTION OFFICER

CIVIL RIGHTS DEFENDERS
Address: Sergels torg 12, floor 12, SE-111 57 Stockholm, Sweden
Tel: +46 8 120 744 03, Mobile: +46 70 484 96 75
martin....@civilrightsdefenders.org

PGP: 0ECD 731D D578 6145 AB22 D213 5104 FC60 779A FD28
SIGNAL available on cell number 

We defend people’s civil and political rights and empower human rights defenders worldwide.
Learn how to support us on www.crd.org

 

[Foppe de Haan]

it'll be in a subfolder of the documents root.

[Martin L. Fällman]

This is the problem: the files are nowhere to be found. Somewhere they do get written because the file copy mechanism identifies that there's already an object there by the same name and it shouldn't be overwritten, but there's no way for me to find it. I did a proper clean re-install of the Windows tools, and set the default user for my W7 HVM to the correct name (the one I log in as) in qvm-prefs, but the problem persists.

Wherever the files I send to the VM gets written, I can't find them from inside the VM, and they persist between restarts. Could it be that they're written to private.img but somewhere Windows doesn't consider "real" for whatever reason? Tried reading the source too but I'm not a C programmer and can't make heads or tails of what's going on.

Best,
//MLF.

[Grzesiek Chodzicki]

Does the issue still occur after You change the default Windows user in Qubes settings? qvm-prefs -s windows default_user admin ?

[Martin L. Fällman]

>
> Does the issue still occur after You change the default Windows user in
> Qubes settings? qvm-prefs -s windows default_user admin ?

Just tried it, yep. This is strange!

//MLF.

[brenda...@gmail.com]

Hi Martin - were you ever able to resolve exactly where these files were going?

I am seeing the same issue with a Win7 HVM under R4.0rc4 using the qubes windows drivers. First copy seems to work from a fedora VM but no file shows up in windows. Additional attempts to copy says it failed because the file is already there. Happens across reboots (fedora source says file is "there" but nothing on the drives in windows).

Thanks,
Brendan

[brenda...@gmail.com]

On Tuesday, February 13, 2018 at 2:06:59 PM UTC-5, brenda...@gmail.com wrote:
> On Friday, March 3, 2017 at 1:36:35 PM UTC-5, Martin L. Fällman wrote:
> > > Does the issue still occur after You change the default Windows user in
> > > Qubes settings? qvm-prefs -s windows default_user admin ?
> >
> > Just tried it, yep. This is strange!
>

> I am seeing the same issue with a Win7 HVM under R4.0rc4 using the qubes
> windows drivers. First copy seems to work from a fedora VM but no file shows
> up in windows. Additional attempts to copy says it failed because the file is
> already there. Happens across reboots (fedora source says file is "there" but
> nothing on the drives in windows).

Found it (windows 7 search explicitly skips the system directory, so it's a little difficult to discover).

The following directory is the receiving directory:

C:\Windows\System32\config\systemprofile\Documents\QubesIncoming\

Presumably this maps correctly for the account that qubes tools component is running under.

Just FYI, in case someone else runs into this.

Thanks,
Brendan

[Ivan Mitev]

I did run into this a few days ago...

I've just opened an issue to track those things:

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

BTW, did you manage to build QWT ?

[brenda...@gmail.com]

On Wednesday, February 14, 2018 at 3:32:18 AM UTC-5, Ivan Mitev wrote:

Thanks!

> BTW, did you manage to build QWT ?

Sadly, no - I ran out of vacation time (...and should have asked before banging my ahead against the issue for so long). I still have my build environment and Marek's response in my queue so maybe I'll look at it this weekend.

Brendan