Qubes 4, rename vm on secondary drive.

qubenix

unread,

Jul 23, 2018, 1:43:42 PM7/23/18

to qubes-users

Hello all. When trying to rename a vm from a secondary drive
(/dev/vg_sdb/) results in the newly named vm residing on the primary
drive (/dev/qubes_dom0/).

Can I manually rename the vm with the use of `lvrename` on the
`/dev/vg_sdb/vm-vmname.private*` and `qvm-prefs -s` on the `name` field?

--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500

qubenix

unread,

Jul 23, 2018, 4:22:14 PM7/23/18

to qubes-users

qubenix:

> Hello all. When trying to rename a vm from a secondary drive
> (/dev/vg_sdb/) results in the newly named vm residing on the primary
> drive (/dev/qubes_dom0/).
>
> Can I manually rename the vm with the use of `lvrename` on the
> `/dev/vg_sdb/vm-vmname.private*` and `qvm-prefs -s` on the `name` field?
>

`qvm-prefs -s` on `name` does not work.

Upon further thinking, one could simply `qvm-clone -P` to the desired
pool with the new name. However, in one of my situations this doesn't
suffice because the vm is more than half the size of the drive. So I'm
still left wondering how to achieve this.

--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500

awokd

unread,

Jul 25, 2018, 4:27:38 AM7/25/18

to qubenix, qubes-users

I think in Qubes 4.0 a rename does a clone behind the scenes, then deletes
the old. Having it show up in a different pool sounds like unexpected
behaviour. You might want to search to see if there's an issue on it, and
submit one if not.

This won't help where your VM is larger than half the drive. Maybe backup
the contents somewhere else, delete it, recreate with a new name, then
restore.

Reply all

Reply to author

Forward