Hi everyone! I want to be able to access a folder inside the guest that corresponds to a cloud drive that is mounted inside the guest for security purposes. I have tried setting up a shared filesystem inside Virt-Manager (KVM) with virtiofs (following this tutorial: https://absprog.com/post/qemu-kvm-shared-folder) but as soon as I mount the folder in order for it to be accessible on the guest host the cloud drive gets unmounted. I guess a folder cannot have two mounts at the same time. Aliasing the folder using bind and then sharing the aliased folder with the host doesn’t work either. The aliased folder is simply empty on the host.

Does anyone have an idea regarding how I might accomplish this? Is KVM the right choice or would something like docker or podman better suited for this job? Thank you.

7 points

Maybe NFS share the drive from guest to host?

permalink
report
reply
2 points

This, had the same idea for other purposes, sharing a folder from vm to host through network share is the easiest way. Every other solution looks more elegant on paper but has lots of pitfalls.

permalink
report
parent
reply
1 point
*

Every other solution looks more elegant on paper but has lots of pitfalls

A very sane and fair comment.

permalink
report
parent
reply
1 point

I can try but I might end up in the same situation as with virtiofs. The cloud drive will get unmounted and I will end up with an empty folder when I try to access it from the host.

permalink
report
parent
reply
2 points

Absolutely not, NFS is a shared mount. Virtiofs is more complicated because it is emulating a block device.

permalink
report
parent
reply
1 point

Then I will try NFS and get back to you. Thanks :)

permalink
report
parent
reply
1 point

What would be the performance implications? Isn’t virtiofs theoretically faster?

permalink
report
parent
reply
2 points

Not an expert.
Assuming it’s internal I’d assume it’s probably as fast as the guest nic allows?

permalink
report
parent
reply
1 point

Fair. I will try NFS if anything else fails. Thanks :)

permalink
report
parent
reply
2 points

Maybe see if ‘rclone mount’ solves the problem for ya. Rclone can often be a super handy swiss army knife for stuff like this.

permalink
report
reply
1 point

The cloud binary is proprietary and it’s not supported by rclone unless I find out how the binary works but I doubt it uses something standardized like WebDAV underneath.

permalink
report
parent
reply
1 point
*

You say it is mounted. Then you can share it in all the same ways as you would share any other of the VM’s folders.

I am using SMB shares for that (but that is not always the best way ofc).

permalink
report
reply
1 point

The cloud drive is mounted on the guest, yes, but once I mount it with virtiofs in order to share it with the host it gets unmounted and I end up with an empty folder. bind doesn’t work either.

permalink
report
parent
reply
0 points

You don’t

That is going to be painful and not beneficial

permalink
report
reply
1 point

I strongly disagree why this would not be beneficial. Could you expand?

permalink
report
parent
reply
2 points

You will need to mange the VM separately and the added hop (into the VM and then out again) will slow down performance and create another point of failure.

Why would running it in a VM benefit security? Couldn’t you just mount it with fuse?

permalink
report
parent
reply
2 points

Because the executable is proprietary (and a bit legacy I would say) and full of telemetry, undocumented and the cloud service has no CLI, WebDAV or rclone support. I do not want to run something like that on my personal computer and I do not know how to use bwrap properly and don’t want to risk it. I have since switched over to a podman container but I encounter the same problem, the folder is empty on the host (See my post here: https://lemmy.ml/post/22215540).

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.2K

    Monthly active users

  • 1.8K

    Posts

  • 19K

    Comments