Skip to content
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

Error message about missing NetVM; sys-net cannot be started #8461

Closed
code9n opened this issue Aug 29, 2023 · 7 comments
Closed

Error message about missing NetVM; sys-net cannot be started #8461

code9n opened this issue Aug 29, 2023 · 7 comments
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: installer C: networking hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@code9n
Copy link

code9n commented Aug 29, 2023

How to file a helpful issue

Qubes OS release

4.2 rc1

Brief summary

A fresh install of Qubes 4.2 rc1 on two different Lenovo T430 i7 3520M works but you get a message to the effect of:

'There is no net vm'.

There is a net vm in the Qubes manager but you can't start it, it just stops again automatically if you try.

In the 'devices' tab of the Qubes settings manager both Ethernet and Wireless NICs appear to be present in the 'selected' box.

Steps to reproduce

Completely install a fresh Qubes 4.2 rc1 on a Lenovo T430 or T430s. All defaults followed.

Expected behavior

There should be a functioning net vm and you should have network connectivity.

Actual behavior

There is a complete install that appears correct in all matters except for the 'no net vm created' issue described.

@code9n code9n added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Aug 29, 2023
@andrewdavidwong
Copy link
Member

Possible related or duplicate issue: #8242

@andrewdavidwong andrewdavidwong added C: installer hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. C: networking affects-4.2 This issue affects Qubes OS 4.2. labels Aug 29, 2023
@andrewdavidwong andrewdavidwong changed the title r4.2 rc1: no net vm created on fresh install Error message about missing NetVM; sys-net cannot be started Aug 29, 2023
@andrewdavidwong
Copy link
Member

Can you try Qubes 4.2.0-rc2?

@code9n
Copy link
Author

code9n commented Aug 30, 2023

Yes it looks like the same issue, sorry about that. I'll try rc2 and comment on #8242 if and as appropriate.
Closing this issue.

@code9n code9n closed this as completed Aug 30, 2023
@andrewdavidwong
Copy link
Member

This appears to be a duplicate of an existing issue. If so, please comment on the appropriate existing issue instead. If anyone believes this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

@andrewdavidwong andrewdavidwong closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2023
@andrewdavidwong
Copy link
Member

Duplicate of #8242

@andrewdavidwong andrewdavidwong marked this as a duplicate of #8242 Aug 30, 2023
@andrewdavidwong andrewdavidwong added R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Aug 30, 2023
@code9n
Copy link
Author

code9n commented Sep 1, 2023

I don't know if this is the same issue as #8242 or not but hopefully it is useful.

###Qubes OS release

4.2 rc2

###Brief summary

On fresh default install of 4.2 rc2 onto a Lenovo T430 the install is all good except you get this message:

['/usr/bin/qvm-start', 'sys-firewall'] failed:
stdout:""
stderr: "Start failed: internal error libxenlight failed to create new domain 'sys-
firewall', see /var/log/libvirt/libxl/libxl-driver.log for details

at the end of the install.

The only running vm is dom0.

Then when you try to start either sys-usb, sys-net or sys-firewall they open and start then immediately shut down. Leaving no network access so no updating.

sys-usb and sys-firewall are dvms but sys-net is from a template (default - fedora 38)

###Steps to reproduce

Make a default install of Qubes 4.2 rc2 (the same thing happened in rc1). Reboot.

###Expected behavior

These vms should persist and provide network access.

###Actual behavior

These vms start then once started immediately stop themselves.

I have not tried @syntheticdrek 's comment in #8242 because the net-vm was not disposable.

@code9n
Copy link
Author

code9n commented Sep 4, 2023

This is fixed in 4.2 rc3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: installer C: networking hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

2 participants