On Monday, November 20, 2017 at 12:14:16 PM UTC, Bernhard wrote: > Hello, > with your nice help I happily installed Q4.0rc2. Then I created a bunch > of debian-8 based appvm's, to copy my data back from the backup. But > they don't start, finishing with "Cannot execute qrexec-daemon" error. I > hate that error : no clue where it comes from. Any hints? Thank you! > Bernhard > > > P.S: First, I thought that this is the annoying but harmless > "after-tempate-change-xfce-menu-messy" bug (which forces to go to VM > settings, remove all Applications, save, go there again, put them back & > save again to get all symlinks right). But the problem is somewhere else.
I did not read through the link due to short of time atm, but here are some suggestions nontheless, as I've encountered similar issues once in Qubes 4. - Make sure all your VM's are running in HVM mode, in particular if your system cannot run in PV mode. Paradoxially, some systems run PV mode just fine in Qubes 3.2., but PV stops working in Qubes 4. It doesnt matter anyhow, since HVM is the desired mode for now. So just make sure the VM is in HVM. Verify if "qvm-prefs VM-name virt_mode" is giving back PV or HVM. Try change it to HVM if it rapport back PV. - Don't use any Qubes 3.2 templates, as they should not have the same Qubes tools code in them. - Some AppVM's restored from Qubes 3.2. has in my experience been sluggish, laggy, and slow. I moved my data, bookmarks, thunderbird profile folder, etc. in traditional Linux backup sense, over to a new fresh Qubes 4 AppVM. It solved any lag I had, except, sometimes firefox was a bit laggy with 10 or so tabs, whereas before I could easily have 40 tabs open. The firefox browser update happened around same time, so not sure wihch was the cause. But cleaning old firefox data did not fix it, however a clean AppVM did fix it. The issue also extened outside firefox to other applications. - If you cannot start an AppVM that you restored from the backup, assuming you still have the backup available in case anything goes wrong, then try change the Debian AppVM to a Fedora AppVM. Then see if you can trasfer your files out of the broken AppVM, either via Qubes tools, or passtrough an USB pen/drive and transfer it this way. Just be careful, I've been having issues where I was unable to disconnect my USB drive from within the old Qubes 3.2. AppVM, when I tried to salvage my data from it. Luckily it only caused damage to the last file from multiple of different transactions. In case you want to avoid this issue, it may be possible to do an extra transfer, with something pointless you dont mind loosing, just in case the last transfer made is destroyed when trying to disconnect the USB drive. USB works just fine in Qubes 4 AppVM's though, at least, that's my experience with it for now. Hopefully you don't encounter the worst issues. At least I feel stable on Qubes 4 now, but its been a bit turbulent. Hopefully you'll be fine too. Also, is it just me, or does Qubes 4 seem bloody fast in some areas after recent updates? Like shutting down VM's for example, it happens almost instantly, and various of other places that it seems much faster than Qubes 3.2. Perhaps its just my mind playing with me. -- 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/8d023980-f2d9-47d1-bb18-b51d8f1aeff8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
