Xvdi is mapped to /mnt/removable

red-pepper-pesto · August 22, 2025, 3:34pm

Any idea why xvdi is alway mapped to /mnt/removable?

Will there be any issues if I remove the line from TemplateVM? I prefer the defaults provided by udisks2.

github.com/QubesOS/qubes-core-agent-linux

filesystem/fstab

9af5c38af


      
          
          # <file system>   <mount point>     <type>  <options>            <dump> <pass>
          
          /dev/mapper/dmroot   /              ext4    defaults,discard,noatime    1 1
          /dev/xvdb            /rw            auto    noauto,defaults,discard,nosuid,nodev    1 2
          /dev/xvdc1           swap           swap    defaults                    0 0
          tmpfs                /dev/shm       tmpfs   defaults,size=1G            0 0
          devpts               /dev/pts       devpts  gid=5,mode=620              0 0
          sysfs                /sys           sysfs   defaults                    0 0
          proc                 /proc          proc    defaults                    0 0
          /dev/xvdi            /mnt/removable auto    noauto,user,rw              0 0

Atrate · August 22, 2025, 10:04pm

I have to say I can’t find any good documentation on that line, but I think Enable more than one block device in VM · Issue #419 · QubesOS/qubes-issues · GitHub is partially related?

rustybird · August 23, 2025, 11:52am

Hmm, that was added 15 years ago in R2. Seems like a conventional location?

I’m not aware of anything that depends on that /etc/fstab line, and a GitHub code search didn’t bring up anything obvious.

However, if you modify the file at all, it will no longer automatically pick up updates to it. Maybe masking or overriding the mnt-removable.mount systemd unit in the TemplateVM instead would be enough to make a difference for udisks2?