On 11/19/18 12:48 PM, qube1...@gmail.com wrote:
I'm a newbie trying to set up a Windows 10 HVM template (without Qubes windows tools) in Qubes 4.0.1rc1. The tempalate works fine but never leaves the transient state. Is this a known limitation without the windows tools or am I missing something?
Without Qubes windows tools (QWT) you don't have qrexec [1], so no communication is possible between the (H)VM and dom0 -> no way for dom0 to know that the vm has properly started. Hence the 'transient' state instead of 'running'.
My real issue is that an AppVM of this template never persist/commit the private snap image. I'm just guessing this might be due to the fact that the qube (AppVM and TemplateVM) never hits the Running state?
No, that's because in template mode the private volume is wiped so you have to format it *each time* (+ migrate the user profile folders there). You'll have to write a shell script that takes care of that or alternatively, try to install QWT, which provides that feature. But if you go that route clone/backup your vm first and be ready for some trial and error (QWT 3.x is buggy on R4 [2], and I have no idea if the QWT 4.x test versions works properly on Win10 as a template).
Normal PVHs AppVM's work fine with their states/private data.
Yes - because their private volume is persistent. Hope this helps, Ivan [1] https://www.qubes-os.org/doc/qrexec3/ [2] https://github.com/QubesOS/qubes-issues/issues/3585 -- 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/62248398-13c3-14df-7084-1f4216de487a%40maa.bz. For more options, visit https://groups.google.com/d/optout.
