On Thursday, May 17, 2018 at 8:57:09 PM UTC-4, Qubes Guy wrote:
> I've successfully used qvm-block (in Dom0) to attach USB drives to different 
> VMs (persistently), but I've noticed that Qubes (or Linux) sometimes gives 
> them to different devices over time. In other words, on Monday, my 
> BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to /dev/sdj when 
> I boot up on Wednesday. This is throwing off my VeraCrypt / FreeFileSync 
> backup routine. (Another way of saying this is if I say "qvm-block attach 
> MyVM sys-usb:sda --persistent" when one of the three drives I use for MyVM is 
> currently attached to that, this will fail if Qubes moves that drive to a 
> different device-name (during boot) that isn't one of the three I previously 
> attached (when I go to start up that VM).
> 
> I thought about persistently attaching all 10 of my USB drives to the VM 
> (some HDs, some flash, one SSD - I never use all of them at once - don't 
> ask!) because that would certainly fix this problem, but I get the following 
> error when I try to start the VM: "ERROR: Start failed: XML error: target 
> 'xvdi' duplicated for disk sources '/dev/sdc' and '/dev/sde', see 
> /var/log/libvirt/libxl/libxl-driver.log for details".
> 
> Note that I did all the persistent attachment commands while the VM was not 
> running. If I detach all those, start the VM, do the persistent attachments, 
> shut down the VM and then restart it, I get an error along the lines of 
> "qrexec process failed to respond in 60 seconds".
> 
> So, I guess I'm asking if there's a way to just persistently attach 2 or 3 
> external USB drives and have them consistently available on the same device 
> names when I start the VM so VeraCrypt doesn't balk?  (VeraCrypt ultimately 
> doesn't care what device a drive is attached to (it could be sda - sdj on my 
> system) because it shows the attached drive as "/media/user/BIG_TOSHIBA, but 
> if a drive isn't where it's supposed to be, that'll fail.
> 
> In case you're curious, the error messages in 
> /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you 
> want me to post it, I can.
> 
> Any help you guys can give me would be greatly appreciated! Thanks...

By the way, I'm running version 4.0 of Qubes on a fairly recent laptop with 8GB 
of RAM...

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/592ec7f7-d1c5-4bf6-871a-3863fec8ff0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to