Can't migrate qube with custom conf file from 3.2 to 4.0

[orwinslanner]

The --custom-config option has been removed from qvm-start. This is a regression from 3.2, if there's nothing to replace it.

I have a standalone VM, without Qubes tools installed, that works fine on 3.2. I'm trying to migrate it to 4.0. I use a custom conf file with some sections like

<disk type='block' device='disk'>
  <driver name='phy'/>
  <source dev='/var/lib/qubes/appvms/myvm/root.img'/>
  <target dev='xvda' bus='xen'/>
</disk>

<disk type='block' device='disk'>
  <driver name='phy'/>
  <source dev='/var/lib/qubes/appvms/myvm/myvm-1.img'/>
  <target dev='xvdb' bus='xen'/>
</disk>

<disk type='block' device='disk'>
  <driver name='phy'/>
  <source dev='/var/lib/qubes/appvms/myvm/myvm-2.img'/>
  <target dev='xvdd' bus='xen'/>
  <readonly/>
</disk>

Backup/restore doesn't get myvm-1.img and myvm-2.img and my custom conf file, but that's ok, I can copy them manually. But the problem is the new LVM storage and the rewritten qvm tools; there doesn't appear to be a way to attach the .img files to the VM. Installing Qubes tools isn't an option, and the two .img files are essential for this VM.

[marmarek]

See here: https://dev.qubes-os.org/projects/core-admin/en/latest/libvirt.html. If you want to replace default disks, you need to replace block "devices", probably also avoiding calling "super()" there.

[marmarek]

See here: https://dev.qubes-os.org/projects/core-admin/en/latest/libvirt.html. If you want to replace default disks, you need to replace block "devices", probably also avoiding calling "super()" there.