But I already fail at the very first step. My setup is vanilla (all lvm stuff done by the installer after giving it the entire drive) Can someone please walk me through how to get the qube from the one to the other machine?
You need to know some LVM details to start using Wyng. On Qubes the following will show the necessary info:
sudo lvs | awk '{print $2, $1}' | grep pool
On Qubes 4.0 you should see ‘qubes_dom0 pool00’. That is the vg and the pool.
To add an ‘App’ qube’s storage volume to the archive, you probably want only the private volume. Qubes private volumes are prefixed with ‘vm-’ and suffixed with ‘-private’. So you would run sudo wyng add vm-my_win_qube-private and then sudo wyng send. To backup a template or standalone qube, you would add both the ‘-private’ and the ‘-root’ volumes.
The above will produce a ‘wyng.backup’ archive directory, not an img file. This is what you would transfer to the other system.
Note that Wyng doesn’t save Qubes VM settings, so you would need to configure the qube/VM settings on the destination system manually before using wyng receive.
With that said, I don’t know if Wyng is really matching your intent here. Wyng is meant for repeated backups of the same volumes (from the same source) over time, and to make that process very efficient. If you are simply transferring over to a new system as a one-time procedure, and qubes-backup is somehow not up to the task, there are simpler ways to do it using tools like dd and gzip. For example, sudo dd if=/dev/qubes_dom0/vm-my_win_qube-private | gzip >private.img.gz and on the destination system (after creating & configuring the destination qube manually): gunzip -c private.img.gz | sudo dd conv=sparse of=/dev/qubes_dom0/vm-my_win_qube-private. OTOH, if your intent is regular repeated backups then disregard this paragraph.