Is my Qubes system corrupted or is this just a bug?
Mindus Amitiel Debsin
So I had Debian-9 templateVM running and I right clicked on it in Qube Manager and told it to shut down. [I wanted to clone the Debian-9 so I had a workspace that had exfat support] Then after about 30 seconds, it was still up, so I right clicked on it and said "Kill Qube."
And the response I got was this: (Sorry I couldn't screenshot it).
===
[Dom0] Houston, We have a problem...
Whoops. A critical error has occured. This is most likely a bug in Qubes Manager.
Assertion Error:
at line 830
of file /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py
===
I had been trying to get a Windows 10 Qube installed so I can learn Qube while also getting some stuff done in my primary OS. I have read a very interesting post here that encouraged me: https://groups.google.com/d/topic/qubes-users/dB_OU87dJWA
But sadly my attempts to even get a Win 10 installation started have resulted in complete failure. I have 2 Windows 10 install methods: by USB drive, and by .iso file. Neither have worked at all in the Qube I have created for it. Obviously I was using the Debian qube from before because it supports exfat.
===
When I start Qubes from boot, I get this message:
"[FAILED] Failed to start Load Kernal Modules.
See 'systemctl status systemd-modules-load.service' for details"
and then it goes into
"Starting apply Kernal Variables..."
And it has a bunch of [OK]s in the boot.
===
Since I believed that my qubes system might be corrupted, I did a "shutdown -Fr" in dom0 terminal, but it didn't seem to have any effect other than an ordinary shutdown.
So my questions:
1) How do I confirm that my Qubes system is fully functioning? Like maybe an SFC for Qubes?
2) With the error with the Qubes manager, how do I fix that or upgrade to a newer version?
3) Are there any step-by-step install instructions for an HVM Windows 10 Qubes install?
Thanks for reading. Maybe I will come up with more questions later. Sorry I don't know Qubes or Linux very well. I've been going through the documentation and have even used terminal commands instead of just GUI, but it is still a learning experience.
~Mindus
Stefan Leibfarth
>
> So I had Debian-9 templateVM running and I right clicked on it in Qube Manager and told it to shut down. [I wanted to clone the Debian-9 so I had a workspace that had exfat support] Then after about 30 seconds, it was still up, so I right clicked on it and said "Kill Qube."
>
> And the response I got was this: (Sorry I couldn't screenshot it).
> ===
>
> [Dom0] Houston, We have a problem...
> Whoops. A critical error has occured. This is most likely a bug in Qubes Manager.
>
> Assertion Error:
> at line 830
> of file /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py
not automatically refreshed.
Just shut down the VM, refresh the qubes list und you will (most likely)
see that it hast been shut down.
Stefan Leibfarth
> But sadly my attempts to even get a Win 10 installation started have resulted in complete failure. I have 2 Windows 10 install methods: by USB drive, and by .iso file. Neither have worked at all in the Qube I have created for it. Obviously I was using the Debian qube from before because it supports exfat.
>
If you need a Win vm, that are instructions for Win7 HVMs.
cooloutac
yes as above poster said, after every action you need to manually refresh the qubes manager by clicking the green recycle icon. The qubes manager is still showing it as running but it is already shut down thats probably why you are getting that error message.
A more reliable way to see running qubes with mouse is by using the widget in taskbar.
I also personally like to keep qubes-manager organized by the state column.