On 04/23/2018 11:15 AM,
gal...@gmail.com wrote:
> Anyone?
That's not something I tested when writing the windows VM doc, it looks
like another issue with QWT under 4.0.
I just tried to create a win AppVM based on a template (if anyone else
wants to try, see steps below) and indeed, the private disk is not
configured; it's not missing though - you can format it and attach it to
d: in windows' disk manager. Obviously the user profile folders will be
missing ; one workaround is to recreate them (didn't test it) or to copy
the templateVM's private disk, like so:
sudo dd conv=sparse if=/dev/mapper/qubes_dom0-vm--test2--private
of=/dev/mapper/qubes_dom0-vm--my--new--qube--private
("test2" is the windows TemplateVM, "my-new-qube" is an AppVM based on
the "test2" TemplateVM ; I don't know if conv=sparse helps).
That's really "low-level" and error-prone so be extra careful with dd;
maybe there are higher level qubes* (or LVM) tools that can perform
that, I didn't have time to check
Once the private disk is copied everything seems to work ; I only get a
popup for xen stuff asking me to restart the VM but simply clicking "no"
is enough.
steps:
- clone a working windows install into a TemplateVM (qvm-clone --class)
- create an AppVM based on this TemplateVM (had to fix the following
prefs because they weren't set properly: kernel, maxmem, memory, virt_mode
- replicate the private disk with `dd`
- start the new AppVM