sys-net keeps dying
38 views
Skip to first unread message
tetra...@danwin1210.me
Dec 8, 2019, 2:57:21 PM12/8/19
to qubes...@googlegroups.com
see the corresponding issue:
https://github.com/QubesOS/qubes-issues/issues/5508
The tldr is that ever since I upgraded to fedora-30, sys-net has started
dying intermittently (or less intermittently, nearly every time) I put
my laptop to sleep.
This is really problematic.
I am wondering if it would make sense to re-create sys-net from scratch.
Could it be that this is something from fedora-29 that is not working
well with fedora-30?
There doesn't seem to be much documentation on how to do this. One post
suggests you just create a new VM and call it sys-net:
https://www.reddit.com/r/Qubes/comments/amvkz3/how_to_create_net_and_firewall_again_with_default/efpl5i2/
However that doesn't seem right, isn't something extra needed to get
the NetworkManager wifi menu widget set up?
https://github.com/QubesOS/qubes-issues/issues/5508
The tldr is that ever since I upgraded to fedora-30, sys-net has started
dying intermittently (or less intermittently, nearly every time) I put
my laptop to sleep.
This is really problematic.
I am wondering if it would make sense to re-create sys-net from scratch.
Could it be that this is something from fedora-29 that is not working
well with fedora-30?
There doesn't seem to be much documentation on how to do this. One post
suggests you just create a new VM and call it sys-net:
https://www.reddit.com/r/Qubes/comments/amvkz3/how_to_create_net_and_firewall_again_with_default/efpl5i2/
However that doesn't seem right, isn't something extra needed to get
the NetworkManager wifi menu widget set up?
Claudia
Dec 9, 2019, 5:41:12 PM12/9/19
to qubes...@googlegroups.com
tetrahedra via qubes-users:
just change the template back to 29 for sys-net and see if that fixes
it. If not, perhaps you could downgrade it, or try explicitly installing
the fedora 29 template.
>
> There doesn't seem to be much documentation on how to do this. One post
> suggests you just create a new VM and call it sys-net:
> https://www.reddit.com/r/Qubes/comments/amvkz3/how_to_create_net_and_firewall_again_with_default/efpl5i2/
>
>
> However that doesn't seem right, isn't something extra needed to get
> the NetworkManager wifi menu widget set up?
>
Not that I know of. As far as I know, system tray icons are just like a
regular window, in that any VM can create them without any special
configuration, and they're colored according to the VM. So when you
start NetworkManager it should just appear in the tray.
I don't know anything about that guide, but it may be worth trying. You
can create a new VM called sys-net2 or whatever so you don't have to
overwrite your existing sys-net. Then just create a temporary AppVM with
sys-net2 as its NetVM to test it.
Other than that the only option I can think of is to debug your current
sys-net and fix whatever is causing it to crash. Check /var/log/qubes,
/var/log/xen, and `xl dmesg`.
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
> see the corresponding issue:
> https://github.com/QubesOS/qubes-issues/issues/5508
>
> The tldr is that ever since I upgraded to fedora-30, sys-net has started
> dying intermittently (or less intermittently, nearly every time) I put
> my laptop to sleep.
>
> This is really problematic.
>
> I am wondering if it would make sense to re-create sys-net from scratch.
> Could it be that this is something from fedora-29 that is not working
> well with fedora-30?
Did you keep the fedora 29 template installed? If so, I think you could
> https://github.com/QubesOS/qubes-issues/issues/5508
>
> The tldr is that ever since I upgraded to fedora-30, sys-net has started
> dying intermittently (or less intermittently, nearly every time) I put
> my laptop to sleep.
>
> This is really problematic.
>
> I am wondering if it would make sense to re-create sys-net from scratch.
> Could it be that this is something from fedora-29 that is not working
> well with fedora-30?
just change the template back to 29 for sys-net and see if that fixes
it. If not, perhaps you could downgrade it, or try explicitly installing
the fedora 29 template.
>
> There doesn't seem to be much documentation on how to do this. One post
> suggests you just create a new VM and call it sys-net:
> https://www.reddit.com/r/Qubes/comments/amvkz3/how_to_create_net_and_firewall_again_with_default/efpl5i2/
>
>
> However that doesn't seem right, isn't something extra needed to get
> the NetworkManager wifi menu widget set up?
>
regular window, in that any VM can create them without any special
configuration, and they're colored according to the VM. So when you
start NetworkManager it should just appear in the tray.
I don't know anything about that guide, but it may be worth trying. You
can create a new VM called sys-net2 or whatever so you don't have to
overwrite your existing sys-net. Then just create a temporary AppVM with
sys-net2 as its NetVM to test it.
Other than that the only option I can think of is to debug your current
sys-net and fix whatever is causing it to crash. Check /var/log/qubes,
/var/log/xen, and `xl dmesg`.
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
tetra...@danwin1210.me
Dec 10, 2019, 3:11:35 AM12/10/19
to Claudia, qubes...@googlegroups.com
On Thu, Dec 05, 2019 at 03:05:42PM +0000, Claudia wrote:
>>I am wondering if it would make sense to re-create sys-net from scratch.
>>Could it be that this is something from fedora-29 that is not working
>>well with fedora-30?
>
>Did you keep the fedora 29 template installed? If so, I think you
>could just change the template back to 29 for sys-net and see if that
>fixes it. If not, perhaps you could downgrade it, or try explicitly
>installing the fedora 29 template.
No, I just deleted the fedora-29 template recently, not realising it
>>I am wondering if it would make sense to re-create sys-net from scratch.
>>Could it be that this is something from fedora-29 that is not working
>>well with fedora-30?
>
>Did you keep the fedora 29 template installed? If so, I think you
>could just change the template back to 29 for sys-net and see if that
>fixes it. If not, perhaps you could downgrade it, or try explicitly
>installing the fedora 29 template.
might be the root of the issue :/
>
>>
>>There doesn't seem to be much documentation on how to do this. One post
>>suggests you just create a new VM and call it sys-net:
>>https://www.reddit.com/r/Qubes/comments/amvkz3/how_to_create_net_and_firewall_again_with_default/efpl5i2/
>>
>>
>>However that doesn't seem right, isn't something extra needed to get
>>the NetworkManager wifi menu widget set up?
>>
>
>Not that I know of. As far as I know, system tray icons are just like
>a regular window, in that any VM can create them without any special
>configuration, and they're colored according to the VM. So when you
>start NetworkManager it should just appear in the tray.
>
>I don't know anything about that guide, but it may be worth trying.
>You can create a new VM called sys-net2 or whatever so you don't have
>to overwrite your existing sys-net. Then just create a temporary AppVM
>with sys-net2 as its NetVM to test it.
I did create sys-net2 and NetworkManager started automatically (no
>>
>>There doesn't seem to be much documentation on how to do this. One post
>>suggests you just create a new VM and call it sys-net:
>>https://www.reddit.com/r/Qubes/comments/amvkz3/how_to_create_net_and_firewall_again_with_default/efpl5i2/
>>
>>
>>However that doesn't seem right, isn't something extra needed to get
>>the NetworkManager wifi menu widget set up?
>>
>
>Not that I know of. As far as I know, system tray icons are just like
>a regular window, in that any VM can create them without any special
>configuration, and they're colored according to the VM. So when you
>start NetworkManager it should just appear in the tray.
>
>I don't know anything about that guide, but it may be worth trying.
>You can create a new VM called sys-net2 or whatever so you don't have
>to overwrite your existing sys-net. Then just create a temporary AppVM
>with sys-net2 as its NetVM to test it.
configuration needed!) and connected to wifi.
However, when I try to configure sys-firewall to use sys-net2 instead of
sys-net for networking, I get the error:
ERROR Basic tab: Failed to access 'netvm' property
I have sys-net2 set up in HVM mode, with "provides network" checked in
the Advanced tab, the NICs configured in Devices, etc.
>Other than that the only option I can think of is to debug your
>current sys-net and fix whatever is causing it to crash. Check
>/var/log/qubes, /var/log/xen, and `xl dmesg`.
them. I will post to the relevant Github issue about this:
https://github.com/QubesOS/qubes-issues/issues/4658
awokd
Dec 11, 2019, 6:46:24 AM12/11/19
to qubes...@googlegroups.com
tetrahedra via qubes-users:
> However, when I try to configure sys-firewall to use sys-net2 instead of
> sys-net for networking, I get the error:
> ERROR Basic tab: Failed to access 'netvm' property
This should work, but make sure sys-firewall is shutdown before
attempting to change. If it still isn't, try changing with qvm-prefs
sys-firewall.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
> However, when I try to configure sys-firewall to use sys-net2 instead of
> sys-net for networking, I get the error:
> ERROR Basic tab: Failed to access 'netvm' property
attempting to change. If it still isn't, try changing with qvm-prefs
sys-firewall.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
tetra...@danwin1210.me
Dec 12, 2019, 9:25:05 PM12/12/19
to awokd, qubes...@googlegroups.com
On Wed, Dec 11, 2019 at 11:46:04AM +0000, 'awokd' via qubes-users wrote:
>This should work, but make sure sys-firewall is shutdown before
>attempting to change. If it still isn't, try changing with qvm-prefs
>sys-firewall.
Ok, I didn't realize sys-firewall had to be shutdown. Most of the time
>This should work, but make sure sys-firewall is shutdown before
>attempting to change. If it still isn't, try changing with qvm-prefs
>sys-firewall.
you can change a VM's networking without shutting it down first... in
any case, once sys-firewall was off, changing networking worked fine.
Unfortunately, creating a new sys-net does not appear to have fixed the
issue, crashes still occur.
Reply all
Reply to author
Forward
0 new messages