dd bs=4M if=raspbian-stretch.img of=/dev/sdX conv=fsyncI can confirm it can work with qvm-block at least, when I made a raspberry pi (quite recently too) on Qubes 4 RC-3 (updated to RC-4), through the Card Reader and qvm-block, and performed the install inside the AppVM without a hitch.
Does any of these suggestions help?
- Is it certain that this Card Reader is run through a USB controller and not another type of controller? the block devices show up in the USB VM? lsusb? if not, maybe the issue might be whichever controller is responsible for the SD-Card Reader needs to be moved away from dom0, given some types of qvm-usb/qvm-block flaws in dom0, which are bugs that may not appear if the controller is located in VM's.
- Does dd command work in the same AppVM (or dom0) where the controller responsible for your SD-Card Reader is located, without using qvm-block to another AppVM? It could give better clues as to whats wrong. It might not be desired, but it could also serve as a last resort to just use the USB VM itself as a work-around to execute 'dd' if everything else fails.
- The USB VM is not a minimal template right? If so, all the required packages installed?
- I wonder about this one (probably not the issue), but it might be worth trying making a new partition tables with fdisk command in whichever domain you the controller.
- You could temporarily move the controller away from the USB VM and onto the AppVM where you want to run the dd command, and then back again once you're done. Troublesome to restart without the PCI memory reset though, and doesn't fix the issue and is more a work-around right :/