Re: [qubes-users] Re: How do I attach a hard drive to a VM on boot?

2020-01-01 Thread River~~
On 16:36, Sun, 22 Dec 2019 <244clarendo...@gmail.com wrote:
>
>
>> The only remaining problem here might be that /dev/sda3 doesn't
>> reference the same drive on each dom0 boot process...
>>
>> So you'd have to write ... Alternatively  you could  ...
>
>
> Another option is to label the filesystem, say with
>
> tune2fs -L foo /dev/sda3
>
> Then, instead of the /dev/xxx entry in fstab, use LABEL=foo like this
>
>
> LABEL=foo   /mnt/tmpauto user,rw 0 0
>
> That way it will find the relevant partition, even if it moves around in
the partition table on the real disk, or if it appears on a different
virtual disk.(not yet tested on Qubes, but this is my normal way of making
fstab entries persist)

That success the problem of the disk moving around in the VM. It doesn't
solve the issue that it might be on a different unit in Dom0.

To get ground that, you might like to label the filesystem as before, and
refer to it in Dom0 as

/dev/disk/by-label/foo

Happy new year !

-- 
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/CAK3jUKr2Ks4WVsXwJLRZMWM8sEACAwnyVOY63haDReDgKqiawQ%40mail.gmail.com.


Re: [qubes-users] Re: How do I attach a hard drive to a VM on boot?

2019-12-22 Thread 244clarendonst


> The only remaining problem here might be that /dev/sda3 doesn't 
> reference the same drive on each dom0 boot process... 
>
> So you'd have to write ... Alternatively  you could  ...
>

Another option is to label the filesystem, say with 

tune2fs -L foo /dev/sda3

Then, instead of the /dev/xxx entry in fstab, use LABEL=foo like this


LABEL=foo   /mnt/tmpauto user,rw 0 0

That way it will find the relevant partition, even if it moves around in 
the partition table on the real disk, or if it appears on a different 
virtual disk.(not yet tested on Qubes, but this is my normal way of making 
fstab entries persist)

You can also do the same using UUIDs, but I prefer to use meaningful 
identifiers. I am old-school in that respect.

R~~

-- 
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/8767cb3e-335e-4585-8691-bb0795c4a0e0%40googlegroups.com.


Re: [qubes-users] Re: How do I attach a hard drive to a VM on boot?

2019-12-14 Thread David Hobach

On 12/13/19 8:33 PM, billol...@gmail.com wrote:

No, it's been consistent for a few weeks now, so I'm not going to worry
about it.  I did find another way to screw up, though.  I attached the
drive persistently to my "untrusted" VM, and then put the mount in
/etc/fstab in the debian-10 template, so it would persist also.  That
worked fine for the untrusted VM, but none of the other debian-based VMs
would start, since they couldn't mount /dev/sda3.  Sigh.  So, now I have to
figure out how to add that to the fstab just for "untrusted."  I saw some
instructions, involving adding an echo command to an rc script, but haven't
tried it yet.


Yes, simply use your mount in /rw/config/rc.local, cf. [1].

[1] https://www.qubes-os.org/doc/config-files/

--
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/d5dcf2af-6290-1acc-6bee-20fba3647d41%40hackingthe.net.


smime.p7s
Description: S/MIME Cryptographic Signature


Re: [qubes-users] Re: How do I attach a hard drive to a VM on boot?

2019-12-13 Thread billollib
No, it's been consistent for a few weeks now, so I'm not going to worry 
about it.  I did find another way to screw up, though.  I attached the 
drive persistently to my "untrusted" VM, and then put the mount in 
/etc/fstab in the debian-10 template, so it would persist also.  That 
worked fine for the untrusted VM, but none of the other debian-based VMs 
would start, since they couldn't mount /dev/sda3.  Sigh.  So, now I have to 
figure out how to add that to the fstab just for "untrusted."  I saw some 
instructions, involving adding an echo command to an rc script, but haven't 
tried it yet.

-- 
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/c99573f3-4b4f-40b6-a978-027d385c595f%40googlegroups.com.


Re: [qubes-users] Re: How do I attach a hard drive to a VM on boot?

2019-12-12 Thread David Hobach

On 12/12/19 8:46 PM, billol...@gmail.com wrote:


Doh.  I just noticed the "noauto" option.  Sigh. Deleted it and it works
fine.


The only remaining problem here might be that /dev/sda3 doesn't 
reference the same drive on each dom0 boot process...


So you'd have to write a udev rule for that. Alternatively your could 
write a little dom0 script to do the attachment by disk ID 
(/dev/disk/by-uuid) rather than via --persistent.


But I might also be wrong and Qubes OS solved that referencing issue 
internally.


--
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/59257a08-0257-82f9-e618-3eeaf25b8c75%40hackingthe.net.


smime.p7s
Description: S/MIME Cryptographic Signature