Another qui-device widget bug

tempmail · September 30, 2024, 8:58pm

[user@dom0 ~]$ qvm-block ls
BACKEND:DEVID   DESCRIPTION                                         USED BY
dom0:loop68     /usr/lib/qubes/qubes-windows-tools-placeholder.iso

So, obviously no qube uses it. How on earth I can get rid of it from qui-devices? I don’t even know what the proper term for getting rid of it would be, because it isn’t mounted (df -H), I don’t even know how it got there on the first place.

Device widget is the worst thing in Qubes, after keyboard layout switch. Better not to have them, then to have them in this state.

parulin · October 1, 2024, 7:23am

Edit: I’m wrong. ~~I don’t think it’s a bug: given the loop... device id, it may be a loop device, try to run losetup --list in dom0 to get more informations about this.~~

apparatus · October 1, 2024, 7:25am

Related issue:

github.com/QubesOS/qubes-issues

Unable to Detach/Unmount Block Devices using GUI

opened 02:07PM - 14 Sep 20 UTC

zellchristensen

T: bug C: manager/widget P: default needs diagnosis affects-4.1 affects-4.2

**Qubes OS version** 4.0.3 **Affected component(s) or functionality** Devic…e Manager **Brief summary** Certain Block Devices persist in the device manager list and can't be detached/unmounted via GUI. **To Reproduce** Two separate methods. Example 1 1.) Make sure Windows Tools are installed `sudo qubes-dom0-update qubes-windows-tools` 2.) Start new or existing VM with Windows Tools attached. `qvm-start <vmName> --install-windows-tools` 3.) Observe that Qube starts with windows tools attached. 4.) Shutdown Qube. 5.) Optionally, repeat steps with other Qubes or same Qube to get multiple block devices of the Windows Tools for each time it was used. OR Example 2 1.) Load an ISO file on to a USB stick 2.) Insert in to Qubes machine, start USB Qube (sys-usb), assign device to OtherVM (Debian based in my test case). 3.) Mount Block Device in OtherVM and verify it's accessible. ( `udisksctl mount -b /dev/xvdi` in my test case) 4.) In ThirdVM Settings >> Advanced tab, click button "Boot qube from CDROM" 5.) In popup, select from file in qube and select the OtherVM the device is mounted in and browse to the mounted dir and choose the ISO file. Click OK. 6.) ThirdVM starts up with ISO mounted and new Block Device for that ISO. 7.) Shutdown ThirdVM and verify the device is still in the Device Manager, now unattached. 8.) Attempt to unmount from OtherVM ( `sudo umount /mnt/removable` in my case) 9.) See error, "target is busy" **Expected behavior** There should be some way to easily manually remove these Block Devices. **Actual behavior** Block devices from dom0 (First example above) remain until system reboot. Block devices from OtherVM's (Second example above) cannot be unmounted from within the VM and are only removed from the Device Manager when that VM is shutdown. **Screenshots** ![snapshot_2020-09-14](https://user-images.githubusercontent.com/38737447/93095286-85338800-f668-11ea-932b-4688dac9da44.jpg) Note that USB drive was physically removed before image was taken. **Additional context** The screenshot is mostly relating to Example 1 after using the command line to start various VMs with the Windows Tools added leading to multiple versions of the ISO being mounted when no VM is using it. Also Example 2 with the top ISO which cannot be unmounted from inside that debianQube, It just requires the VM be shut down. I did not try Example 2 with a Fedora based VM yet. I'm using a Debian based VM as my USB drive is formatted in exFat and Fedora lacks exFat support and cannot mount it. **Solutions you've tried** Restarting VMs block devices are from or restarting the entire system. **Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted** https://www.qubes-os.org/doc/block-devices/ https://www.qubes-os.org/doc/usb-devices/ https://www.qubes-os.org/doc/windows-tools/

apparatus · October 1, 2024, 7:34am

I’ve tried to remove it with e.g. sudo losetup -d /dev/loop68 and it’s unmounting the iso from the loop device but it’s not removing the loop device itself. I guess it’s not removing the loop device since it’s in use by some Qubes process.