On Monday, 8 January 2018 00:59:29 UTC, Sameer Vao wrote: > >> If you haven't already, try running "sudo qubes-dom0-update" as soon as > >> you get in to Qubes. > > >Thank you awokd. I did but haven't solved it. > >I'm thinking something limiting memory or CPU may be the way to solve it, > >but may be something else. > >Any other ideas anybody? > > After much search and trials last 5 days, still found nothing online to solve > this problem. Another notebook not an option for me at this time > unfortunately. > > If I can't fix it I will have to install another linux distribution - but > that would be sad. Anybody else have other ideas so I can keep qubes? Thank > you >
How many VM are you running? I suspect with your limitation sys-net, sys-firewall and one or two other VM is all you can reasonably do. Is the system still unstable if you have only sys-net and sys-firewall up? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3daa2bd5-852b-4526-94f9-430cdf4d188b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
