On Friday, October 13, 2017 at 4:12:12 AM UTC+2, Chris Laprise wrote:
> On 10/12/2017 06:42 AM, Foppe de Haan wrote:
> > On Wednesday, October 11, 2017 at 10:08:18 PM UTC+2, Chris Laprise wrote:
> >> On 10/11/2017 04:05 PM, Chris Laprise wrote:
> >>>
> >>> I can explain the steps. You may wish to backup your appVM before
> >>> continuing.
> >>>
> >>> 1. Start a dispVM (I'll call it disp1). Your appVM should not be running.
> >>>
> >>> 2. In dom0 run 'qvm-block -A /var/lib/qubes/appvms/yourappvm/private.img'
> >>> Substitute 'yourappvm' in above command with the name of your appVM.
> >> Correction: This command should be 'qvm-block -A disp1
> >> dom0:/var/lib/qubes/appvms/yourappvm/private.img'
> >>
> >>
> >> -- 
> >> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
> > just for my information: why not just run that from dom0 directly (e.g. 
> > sudo fsck /var/lib/qubes/appvms/bla/bla.img)? is there a security risk 
> > involved with the invocation of fsck?
> >
> 
> Actually, yes there is a risk.
> 
> -- 
> 
> Chris Laprise, tas...@posteo.net
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

btw, when I try this (qvm-block method) in R4.0-rc1, I get 'backend vm 'dom0' 
doesn't expose device '/var/lib/qubes/etc/etc.img'.

-- 
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/c065d54a-ec38-4f55-84d0-e8b6adfae77d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to