On Wednesday, November 22, 2017 at 7:43:59 PM UTC, Ray Joseph wrote: > donoban, > > Thank you. It is now running in dom0. I changed to v4.0RC1. My vms start > intermittently so it is a challenge to test further. > > I guess I could practice in v3.2 until v4 matures.
Actually, if you managed to get that far, you can probably manage to get Qubes 4 to run more or less smoothly. Albeit still may be unlucky to encounter a nasty bug of course, but in my own experience it runs pretty smoothly with newest updates and fixed user mistakes. Qubes 4 user (or semi-user) mistakes that I encountered, that have a big impact on a working Qubes 4: - Not making sure ALL VM's, i.e. from restored backup, are set to HVM instead of PV. This can mess up your VM's, as some systems can no longer run PV VM's properly in Qubes 4, despite having done so just fine in Qubes 3.2. - Using any older Qubes 3.2. templates. A lot of changes was made to the Qubes tools, so the Qubes tools code probably changed in the VM templates too. Be sure you are mindful of this, if you insist on using an older Qubes 3.2. VM template. - A bug in the AppVM templates, seem to mess up icon update in the XFCE4 menu, or somehow even preventing apps to start in VM's. If you encounter a bad AppVM, check if it was restored from Qubes 3.2. If so, then manually transfter your files, bookmarks, etc. out of it and over into a new Qubes 4 freshly made AppVM. - VT-D and similar, is now required for a fully working system, instead of just recommended as it was in Qubes 3.2. and back. You may be able to install, but it won't run smooth without VT-D or similar supported tech. - Newest Qubes (Testing update) has a drawback of Hibernate/Suspend breaking Wi-Fi, and various of other VM functionality. For example all your VM apps may be gone and cannot start. Only solution is either restart ALL your VM's, or in the worst cases, having to restart all of Qubes. Still, this is a testing update, and a user mistake for using a testing update. The developers will probably get it fixed eventually. Staying with regular updates should be safe, I assume of course. If you get the bug, then just be sure you save important work if you use suspend/hibernate. This is likely a pass-through issue (I think), but its definitely not a driver/module issue, like those we otherwise often saw in the past after hibernate/suspend. Either way, my guess is its probably soon fixed before it becomes a normal update. I'm not saying to go Qubes 4 for stability or critical data production, though, in my experience the user (or semi user) mistakes above can have a huge impact on if Qubes 4 works properly or not. There are still other issues, but they are getting more rare, and mostly everything seems to work now. Personally I'd rate Qubes RC-2, fully updated to this date, as late stage beta testing. But that's just my look at it. If you got important work, then it's probably better to stay on Qubes 3.2. for a while yet. If not, and you want to play with Qubes, then you can probably get it work reasonably on supported hardware. -- 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/658c1271-b949-413e-a768-6840e17f665c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
