Re: [qubes-users] Re: Unable to start standalone vm based on debian-9
On Friday, August 24, 2018 at 6:22:31 AM UTC-3, awokd wrote: > On Wed, August 22, 2018 3:03 pm, Fernando wrote: > > On Wednesday, August 22, 2018 at 10:39:19 AM UTC-3, Fernando wrote: > > > >> Hi, > >> > >> > >> This morning I updated my standalone debian-9. From what I remember, it > >> updated the linux image and a few other packages, and it didn't remove > >> any of qubes dependencies. > >> > >> After a system reboot, I'm unable to start the domain. I think I > >> didnt't shutdown the standalone vm manually before the reboot. > >> > >> $ qvm-start mind > >> Cannot connect to qrexec agent for 60 seconds, see > >> /var/log/xen/console/guest-mind.log for details > >> > >> > >> $ tail /var/log/xen/console/guest-mind.log > >> [.[0;32m OK .[0m] Reached target Network is Online. > >> You are in emergency mode. After logging in, type "journalctl -xb" to > >> view system logs, "systemctl reboot" to reboot, "systemctl default" or > >> ^D to try again to boot into default mode. > >> Press Enter for maintenance. > >> > >> > >> I've read in the forums about using xen console to login and try to fix > >> it, but I cannot access the vm: > >> > >> $ sudo xl console mind > >> mind is an invalid domain identifier > >> > >> The domain is not listed in the output of "sudo xl list". > >> > >> > >> Any ideas on how can I fix my standalone vm? Any help is greatly > >> appreciated. > >> > >> Thanks, > >> > >> > >> Fernando. > >> > > > > I forgot to mention that I'm using Qubes 4.0 and non-standalone VMs are > > working as usual. > > > > I'm trying to resume work using the standalone backup, but unfortunately > > restoring it is also failing :( > > Try to enable debug mode on the HVM. This should show a console which > might give you an idea where it's failing, and generate an additional log > file in /var/log/xen/console. Review both HVM related logs for errors. > Also, double check the kernel setting- if it's showing a version try > changing it to (none) or an older version. Hi awokd, Thanks for the response. Since this was my work vm I had to find a quick solution and I ended up recreating the standalone vm. I created a backup of the broken vm and then used the emergency recovery instructions to extract the data from it. This gave me some relief that even in worst case scenario, I'll be able to recover data. If I find this issue again I'll keep in mind your tips and give them a try. Thanks and best regards. -- 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/988b1bbb-f046-4e14-b820-06644f52d428%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Unable to start standalone vm based on debian-9
On Wed, August 22, 2018 3:03 pm, Fernando wrote: > On Wednesday, August 22, 2018 at 10:39:19 AM UTC-3, Fernando wrote: > >> Hi, >> >> >> This morning I updated my standalone debian-9. From what I remember, it >> updated the linux image and a few other packages, and it didn't remove >> any of qubes dependencies. >> >> After a system reboot, I'm unable to start the domain. I think I >> didnt't shutdown the standalone vm manually before the reboot. >> >> $ qvm-start mind >> Cannot connect to qrexec agent for 60 seconds, see >> /var/log/xen/console/guest-mind.log for details >> >> >> $ tail /var/log/xen/console/guest-mind.log >> [.[0;32m OK .[0m] Reached target Network is Online. >> You are in emergency mode. After logging in, type "journalctl -xb" to >> view system logs, "systemctl reboot" to reboot, "systemctl default" or >> ^D to try again to boot into default mode. >> Press Enter for maintenance. >> >> >> I've read in the forums about using xen console to login and try to fix >> it, but I cannot access the vm: >> >> $ sudo xl console mind >> mind is an invalid domain identifier >> >> The domain is not listed in the output of "sudo xl list". >> >> >> Any ideas on how can I fix my standalone vm? Any help is greatly >> appreciated. >> >> Thanks, >> >> >> Fernando. >> > > I forgot to mention that I'm using Qubes 4.0 and non-standalone VMs are > working as usual. > > I'm trying to resume work using the standalone backup, but unfortunately > restoring it is also failing :( Try to enable debug mode on the HVM. This should show a console which might give you an idea where it's failing, and generate an additional log file in /var/log/xen/console. Review both HVM related logs for errors. Also, double check the kernel setting- if it's showing a version try changing it to (none) or an older version. -- 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/2ace92998547db43ae5f69d0aca9548d.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unable to start standalone vm based on debian-9
On Wednesday, August 22, 2018 at 10:39:19 AM UTC-3, Fernando wrote: > Hi, > > This morning I updated my standalone debian-9. From what I remember, it > updated the linux image and a few other packages, and it didn't remove any of > qubes dependencies. > > After a system reboot, I'm unable to start the domain. I think I didnt't > shutdown the standalone vm manually before the reboot. > > $ qvm-start mind > Cannot connect to qrexec agent for 60 seconds, see > /var/log/xen/console/guest-mind.log for details > > $ tail /var/log/xen/console/guest-mind.log > [.[0;32m OK .[0m] Reached target Network is Online. > You are in emergency mode. After logging in, type "journalctl -xb" to view > system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try > again to boot into default mode. > Press Enter for maintenance. > > I've read in the forums about using xen console to login and try to fix it, > but I cannot access the vm: > > $ sudo xl console mind > mind is an invalid domain identifier > > The domain is not listed in the output of "sudo xl list". > > Any ideas on how can I fix my standalone vm? Any help is greatly appreciated. > > Thanks, > > Fernando. I forgot to mention that I'm using Qubes 4.0 and non-standalone VMs are working as usual. I'm trying to resume work using the standalone backup, but unfortunately restoring it is also failing :( -- 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/2fdadbe3-56f5-4742-8a9b-80a07ff61a53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
