-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing VM network via Qube Manager context menu crashes Qube Manager #8156
Comments
Found it - actually asking "hey we need to start the netvm" worked there for a while... except in the case of default_netvm. Nice catch :D |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Changing netvm checks if new netvm is running, and if not asks to start it - this didn't happen for default netvm. Now it will. fixes QubesOS/qubes-issues#8156 (cherry picked from commit cfe4797)
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
Or update dom0 via Qubes Manager. |
Qubes OS release 4.1.2 (R4.1)
Brief summary
Changing VM network via Qube Manager context menu crashes Qube Manager if netVM isn't running.
Steps to reproduce
Expected behavior
Or less preferred expected response:
An error message will popup explaining the sys-firewall must be started to change netVM to sys-firewall.
Actual behavior
Additional context
After updating templates while browsing in DispVM, I wanted to restart sys-net and sys-usb, which is easy enough to do by shutting down sys-firewall and restarting sys-net and sys-usb. If am willing to shutdown the DispVM then I can do that and then shutdown sys-firewall and restart sys-net and sys-usb. If I start a new DispVM then sys-firewall starts up automatically.
If I am not willing to shutdown the DispVM then simply changing the network to none allows me to preserve what I am doing and also shutdown sys-firewall and restart sys-net and sys-usb. And if I start another appVM or dispVM sys-firewall will automatically be started and I can change my DispVM network back to default (sys-firewall) via Qube Manager context menu and it works with no crashing.
Only when I didn't realize that sys-firewall hadn't been restarted did I see this issue.
journalctl entries (edited)
I also noticed that changing VM network from none to default (sys-firewall) via Qube Manager settings gets the following error (edited) when sys-firewall isn't started:
Slightly related non-duplicate issues
4.1 RC1: "Qubes Domains": Add net-vm-selection #7044
Communicate to user that disposable is missing updates after its parent template has been updated but that restarting disposable will reset its state #7779
4.0 - Cannot change netvm where existing netvm is not running #6493
The text was updated successfully, but these errors were encountered: