Re: [qubes-users] Fedora no longer starts, installed from RPM.
On Saturday, 17 March 2018 00:58:59 UTC+11, Unman wrote: > Not supported means the Qubes team dont say it will work and wont put > any effort in to making it work. > Lots of people have had the "QREXEC not running" problem - usually > caused by attached devices or incorrect upstream netvms.That's where I'd > start looking, as well as checking logs, both for the qube and in dom0. I don't mind, it's a Guest that should start since it's a guest. Since it used to work in Qubes. No up-stream vms to it. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e8b2dc87-16a6-439a-9823-1cdf195f7a4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora no longer starts, installed from RPM.
On Thu, Mar 15, 2018 at 07:32:54PM -0700, Drew White wrote: > On Friday, 16 March 2018 11:04:31 UTC+11, Unman wrote: > > On Thu, Mar 15, 2018 at 04:50:14PM -0700, Drew White wrote: > > > I installed my template for fedora 17 and 20, and neither of them will > > > start. > > > I installed them from the RPMs provided. > > > > > > Upon start it looks like it's booting then says "Error could not start VM > > > F17: Cannot execute QREXEC daemon." > > > > > > How can I get them running again? > > > > > > > Hello Drew, > > > > Nice to see you again. > > > > Fedora 17 and 20 are long past eol, and therefore no longer supported in > > Qubes. > > You *may* be able to get them running by building your own qubes > > packages , but I would think that you will have to mangle the code > > somewhat to do that. It's not impossible but you'll have to hack about > > in qubes-builder and the relevant package sources. > > > > I suggest you use more up to date Fedora templates. > > > > unman > > Supported or not, they should still start. > They still use the same Qubes system. > Even if there is no QREXEC they should still start and then be able to have > the console attached to update the QREXEC. > > So support isn't an issue here. > Right now it's an issue of Qubes 3.2 and those templates not starting. > > Is there anyone that is having a similar issue or else managed to resolve a > similar issue here old templates aren't starting any more? > Not supported means the Qubes team dont say it will work and wont put any effort in to making it work. Lots of people have had the "QREXEC not running" problem - usually caused by attached devices or incorrect upstream netvms.That's where I'd start looking, as well as checking logs, both for the qube and in dom0. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180316135855.bfdowvzuywcrr24f%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora no longer starts, installed from RPM.
On Friday, 16 March 2018 11:04:31 UTC+11, Unman wrote: > On Thu, Mar 15, 2018 at 04:50:14PM -0700, Drew White wrote: > > I installed my template for fedora 17 and 20, and neither of them will > > start. > > I installed them from the RPMs provided. > > > > Upon start it looks like it's booting then says "Error could not start VM > > F17: Cannot execute QREXEC daemon." > > > > How can I get them running again? > > > > Hello Drew, > > Nice to see you again. > > Fedora 17 and 20 are long past eol, and therefore no longer supported in > Qubes. > You *may* be able to get them running by building your own qubes > packages , but I would think that you will have to mangle the code > somewhat to do that. It's not impossible but you'll have to hack about > in qubes-builder and the relevant package sources. > > I suggest you use more up to date Fedora templates. > > unman Supported or not, they should still start. They still use the same Qubes system. Even if there is no QREXEC they should still start and then be able to have the console attached to update the QREXEC. So support isn't an issue here. Right now it's an issue of Qubes 3.2 and those templates not starting. Is there anyone that is having a similar issue or else managed to resolve a similar issue here old templates aren't starting any more? -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/658f9638-c91c-4eba-a976-f2e9af31c356%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Fedora no longer starts, installed from RPM.
I installed my template for fedora 17 and 20, and neither of them will start. I installed them from the RPMs provided. Upon start it looks like it's booting then says "Error could not start VM F17: Cannot execute QREXEC daemon." How can I get them running again? -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/61950809-32be-45ec-8d61-df58edd80c38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
