ddevz
September 25, 2024, 7:51pm
1
When using qvm-copy-to-vm inside of some qubes it gives a deprecation warning, and I see people saying that it’s deprecated (links at end).
qvm-copy-to-vm is defaulted to “ask”. If you change the policies for particular systems to “allow” it allows it to copy to just those systems without a prompt. This is all good. So why is it planned to be removed? I can find lots of references to it being deprecated, but I never see the reason. Is it just to try to scare people away until they understand how to set policies properly?
My interest here is trying to break workflow/processes into more qubes, and I’m concerned about the qvm-copy-to-vm command dissapearing after I start using it.
Some References (note: the github issues link to a ton of other related github issues):
Of course.
qvm-copy-to-vm is indeed deprecated, but you can replace it’s
functionality in this case using a policy:
qubes.Filecopy * SOURCE @anyvm allow target=TARGET
This policy will mean that any instance of qvm-copy will be allowed
and the files transferred to TARGET without user intervention.
Armed with that, you can then run qvm-run SOURCE 'cp DIRECTORY' from
dom0.
Remove the policy when done.
The risk here is that while this policy is in place any files may be
transferred from…
opened 12:44PM - 12 Dec 19 UTC
T: enhancement
C: core
ux
P: default
I've been searching around reading, amongst others, this https://github.com/Qube… sOS/qubes-issues/issues/3529 but can't find the solution. How do I specify the destination VM in `qvm-copy` / `qvm-move` when copying / moving files from domU to domU?
### Qubes Version
4.0.2
### Steps to reproduce the behavior:
```
vm1: qvm-copy vm2 myfile.txt
```
-> gives me an error file "vm2" not found
What DOES work is:
```
vm1: qvm-copy myfile.txt
```
-> A dialogue box opens where I have to type the destination VM manually (takes time / not nice for scripting).
### Expected behavior:
When I run:
```
vm1: qvm-copy vm2 myfile.txt mysecondfile.txt
```
A dialogue box opens asking me to confirm copying files to `vm2`, where I don't have to type the destination VM.
Hope I'm not missing something trivial here but just can't figure it out..
opened 04:36AM - 14 Feb 18 UTC
help wanted
C: doc
T: task
P: default
#### Qubes OS version:
<!-- (e.g., `R3.2`)
You can get it from the dom0 t… erminal with the command
`cat /etc/qubes-release`
Type below this line. -->
R4.0 (rc4)
#### Affected TemplateVMs:
<!-- (e.g., `fedora-23`, if applicable)
Type below this line. -->
- fedora-26
- fedora-26-minimal
- debian-9
---
### Steps to reproduce the behavior:
Run `qvm-copy file` in any Qube based on the templates mentioned above.
### Expected behavior:
There should be a way to provide the target Qube on the cli (without a GUI).
### Actual behavior:
A GUI dialogue pops up.
### General notes:
The documentation (https://www.qubes-os.org/doc/copying-files/) states that the old tools like `qvm-copy-to-vm` are deprecated in 4.x The provided user interface is an improvement over the old one on 3.2, but to be able to script certain tasks would yield advantages for me.
---
#### Related issues:
#3529 (might be considered related)