Now when I attempt to start the qube, the terminal for the template (and its dependent appVM) will only display what looks like static. Or if you're old enough, what the TV looked like when you messed with the horizontal hold too far. :)
The VM seems to be running, as if I type "shutdown -h now" in the unintelligible terminal, the VM shuts down.
Any tips? I'm hoping to avoid having to re-build this qube from scratch.
Thanks.
--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/nP_6mgtX0eY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181026113932.3ba50a6e.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.
Moving the terminal windows around doesn't help. I decided to build another HVM template from scratch, but got the same result when I set the kernel to "none" and the virt_mode to "HVM".
Then I tried setting the appVM back to PVH and a qubes kernel. It booted fine. But of course my ZFS modules are compiled for the latest 4.18 distro kernels, so they don't load.
So, something about the distro kernel doesn't like the new updates for dom0?
I meant resizing the terminal windows. Not just moving. Tried that on both. Fullscreen, minimize, etc.
Thanks.
I thought I had already replied to this, but apparently not.
I checked the above link and sure enough, I had several issues with modules on the distro kernel. I attempted to rebuild them, but it still didn't work. So I ended up compiling the zfs modules on a new HVM template after applying the manual u2mfn re-build, and that worked. I then pointed my old appVM to the new template, and am all set.
Thanks for all your help!!