Unable to start VM after renaming in Qubes Manager

19 views
Skip to first unread message

joonas....@openmailbox.org

unread,
Dec 14, 2017, 4:00:25 PM12/14/17
to qubes...@googlegroups.com
Hello,

it looks like I got hit by a severe problem that prevents me from starting an appvm


I searched the bugtracker and it looks like:

https://github.com/QubesOS/qubes-issues/issues/2054

I also renamed a VM and it no longer starts.

The folder under
/var/lib/qubes/appvms/oldname
is still present.

What is the easiest way to get access to the data stored in that VM?

thanks!
Joonas

Unman

unread,
Dec 14, 2017, 4:12:43 PM12/14/17
to joonas....@openmailbox.org, qubes...@googlegroups.com
The data is stored in the private.img file in that folder.

You can either create a new qube, and then attach the file:
qvm-block -A <new> dom0:/var/lib/qubes/appvms/oldname /private.img
then mount /dev/xvdi in <new>, and extract the data from
/mnt/home/user
OR: mount the private.img file in dom0 and qvm-copy the data files to some qube.
OR: create a new qube, and copy the private.img file to /var/lib/qubes/appvms/new

joonas....@openmailbox.org

unread,
Dec 16, 2017, 3:09:05 AM12/16/17
to Unman, qubes...@googlegroups.com
> The data is stored in the private.img file in that folder.
>
> You can either create a new qube, and then attach the file:
> qvm-block -A <new> dom0:/var/lib/qubes/appvms/oldname /private.img
> then mount /dev/xvdi in <new>, and extract the data from
> /mnt/home/user
> OR: mount the private.img file in dom0 and qvm-copy the data files to some qube.
> OR: create a new qube, and copy the private.img file to /var/lib/qubes/appvms/new

Thank you I used the last option and it worked just fine.

Reply all
Reply to author
Forward
0 new messages