Can installing Xen drivers to PopOS let me use Qubes to send files in and out?

I want to transfer files in and out of PopOS likes with Windows. Can I install some Xens drivers?

You mean like with Windows qube with Qubes Windows Tools installed?
For this you need to install Qubes tools in the PopOS but they are not available for it.
Since PopOS is based on Ubuntu then maybe you can install the Qubes tools packages for Ubuntu that @unman provides:
https://qubes.3isec.org/

Or you can create a disk image in one of your app qubes, place the files there, attach it to the PopOS as block device and copy the files from this disk.
In the app qube create a disk:

dd if=/dev/zero of=~/mydisk.img bs=1M count=256
mkfs.ext4 ~/mydisk.img

Mount the disk in the app qube and copy the files:

mkdir ~/mnt
sudo mount ~/mydisk.img ~/mnt
sudo chown -R user:user ~/mnt
cp ~/somefile ~/mnt
sudo umount ~/mnt

Make the disk image available in the Qubes Devices widget:

sudo losetup -f ~/mydisk.img

Attach the /home/user/mydisk.img block device to the PopOS using the Qubes Devices widget.
In the PopOS mount the attached disk, copy the files from it and unmount the disk after you finish the copy:

mkdir ~/mnt
sudo mount /dev/xvdi ~/mnt
cp ~/mnt/somefile ~/somefile
sudo umount ~/mnt

Detach the /home/user/mydisk.img block device from PopOS so you can mount it in app qube and use it there again.

1 Like

I don’t see it

Using Repositories in Debian based templates

To use a repository, copy the validated key to a template, and install it.

sudo gpg -o /usr/share/keyrings/unman-keyring.gpg --dearmor unman.pub

replacing unman.pub with the path to the key.

Then create a repository definition like this at /etc/apt/sources.list.d/3isec.list:

deb [signed-by=/usr/share/keyrings/unman-keyring.gpg] Index of /4.2 trixie main

or:

deb [signed-by=/usr/share/keyrings/unman-keyring.gpg] Index of /4.2 noble main

Make sure that the definition matches the distribution you want.

I have unman’s key in dom0

I am looking for Qubes Tools Packages for Ubuntu and don’t see it on the site.

Are you saying add unman’s key to the PopOS StandAlone VM in the command line inside the VM and then install an ubuntu tool from command line?

I am not sure what the name of the tool would be.

sudo apt install qubes-tools-ubuntu?

I don’t see anything about this on unman’s site.

The quote is about template repositories, not dom0.

Yes.

No idea which packages are required for file copy/move to work.
You can see the list of all available Qubes tools in the repository here:
https://qubes.3isec.org/4.2/pool/main/q/

1 Like

:exploding_head:

I thought it was a solution. I got unman’s key into Pop, used the jammy repo for Ubuntu, and did sudo apt install qubes-core-agent (or it may have been something else but it was start of files listed by unman)

it is very easy to install unman’s repository in PopOS

it seemed to install multiple qubes and lib files, it rebuilt some stuff, and asked for restart

did restart

I have Luks encryption on the drive. I get to the part at which Pop asks for LUKS password.

I type in password

then it say cryptsetup set up succesffully

then zram and dm-2 drives show up in USB list of files!

then error messages display:

failed failed to start Ad… root filesystem size
time timed out waiting for device /dev/xvdc1
depend dependency failed for /dev/xvdc1
depend dependency failed for swaps

what did i do bad?

it also crashes qubes after starting

i also have option to run PopOS in Qubes using a Xen Hypervisor

I am doing it and if you never hear from me again, this has destroyed all the Qubes

why didn’t I listen to the “why don’t you back up data” thread?

it didn’t break qubes but nothing happened

now there is a log in screen for user and password and it won’t accept user or password

should i be booting with xen or without xen? what did i do?

why does it say “volume data cannot be found”

“Maybe” and “No idea” is not an indication of a production-ready and tested solution.

First of all clone your qube without shutting it down.
Then for a cloned qube you can try to revert the volumes to the previous revisions. Qubes OS is keeping 2 revisions of the volumes:

If you didn’t restart the qube after the Qubes tools package installation a few times already then you may be able to revert the volumes to the state before installing them.

Maybe the /etc/fstab entry is expecting for swap to exist on /dev/xvdc1 partition.
If you edit the /etc/fstab and remove this entry from there:

/dev/xvdc1           swap           swap    defaults                    0 0

Then maybe you’ll be able to boot the system.

You mean it crashes whole Qubes OS system? I have no idea how this could happen.

You can copy the data from your qube like this:

Maybe it’ll be faster to just reinstall the PopOS and copy the saved data.

It would just be easier to reinstall Pop. I have the ISO and hadn’t done that much in the VM.

I can get into a command line where it asking me to login, however, it’s asking me to log into the VM:

Pop-QubesMachine login:

that’s the name of the VM. How does it even know it’s own name? I didn’t tell it it’s name.

You should never assume a user with low skills will read the phrase “maybe” and “no idea” and not read that as “this is production ready for all users without doing any backup”

Try to login with root user or as user user.

It’s probably easier to just reinstall.

I can probably run what I wanted to run without PopOS as a StandAlone VM anyway and this was mostly experiment.

I had tried user, I am not sure if I tried root with same Password.

I am not deleting VM if there is easy way to get to work. Had not installed software or done anything major in VM at time of crash.

Easy solution is this:

If you already restarted the qube a few times then just reinstall the OS in the qube.

Oh. Yeah I could do that by booting from the iso in the Qube.

Is this something that could work?

Did this not work because FDE was used?

Did I just install too much stuff from unman’s repo? I am not sure if this is something I can do in theory.

It could to be possible:

@unman did this not work because the disk had FDE or is this because I did something wrong?