I have a strange problem. When configuring the advanced qube settings for a Windows 7 HVM to no kernel, it just snaps back to current! I did install once before this, and didn’t have this problem. What could I be over looking here?
As far as I can see it, that is just a cosmetic problem of Qube Manager. If no kernel is assigned to a qube, it shows (current), while it shows the kernel version if a kernel is assigned.
If I were you, I wouldn’t try to set Linux kernel to Windows qube to check what is going on.
No qube is doing anything for kernel assignment. It does what is being told by dom0 (you).
This is now solved: Qube Manager 4.1.26-1 (in the current testing repo) displays (provided by qube) for TemplateVMs and StandaloneVMs, and default() for AppVMs if no kernel is assigned.
Thanks, enmus and gweck. I appreciate your replies! Guess the bottom line is that the Qube Manager is being updated to resolve the incorrect reporting on settings for kernel being displayed, and is in testing.