I use a "disk image" on more than one appvm (not at the same time of course) and mounting as a loop device in dom0 then qvm-block attach to the target vm works ... most of the time. I normally get an error concerning qubes not exposing the device until I perform a "cd" command.
It is a poor implementation of a security intent. This is how I circumvent... Open dom0 terminal. Execute script to loop mount disk image (losetup) and attach to vm via qvm-block. Get error device not "exposed" Unmount loop device. Issue "cd" command...stay in home dir...change nothing. Loop mount image. Qvm-block attach... Success. This is repeatable. Is there a way to turn off that "feature"? I can avoid it by issuing the "cd" command first. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAArVCJWqNYMY6HFSBBeC4faJfrgc74HzE-Y%2BJyaQtS9Dz4MP9g%40mail.gmail.com.
