-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VM does not start - Qubes R4 - qrexec and sudo xl console vmname - broken at the same time in any Debian based VMs #3187
Comments
(just repeating marek's suggestion made to me elsewhere: have you also tried sudo xl console -t pv vmname ?) |
Also see |
I failed to reproduce this issue for some hours. Now I managed to reproduce. It's not a debian-stretch issue since it also happened with debian-8 and whonix-ws TemplateBased AppVMs. In order to reproduce it I did run
(Starting VM
Takes a long time then shows.
Before it shows that error it is in
Managed to grab a journal while a VM was not starting. Btw what is the difference between guest-vmname.log and guest-vmname-dm.log? I send the logs by private e-mail to @marmarek. Can you make any head or tail of it? Anything else I can do to help? |
@HW42 any idea? I've seen something similar previously. I think it was while debugging grub in HVM. When Linux kernel was started quickly, VM sometimes crashed/hung before producing any output from Linux kernel. But when I added some timeout in grub, it happened much rarer, or at all. It is still happening from time to time on my system, but since no output is produced in such case, it is hard to debug. Mostly while running automated tests (hundreds of VM starts, happens like in 1% of cases).
The -dm one is about stubdomain hosting qemu process. |
As a temporary workaround (attempt)... How do I increase grub timeout? Inside the VM, I adjusted timeout to |
To actually use that grub, you need to set `kernel` property to empty
string ("(none)" in GUI).
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
When I set it to None in GUI, it will always be reset to previous value. Do we have a bug report for this? (Just now upgraded with latest packages from Qubes testing and rebooted.) Did...
VM startup took long, but couldn't see grub boot menu in xl console. Any advice? |
Enable debug mode to access it on VGA console.
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Not really. But I think I have seen this at least once. For some reason the VM won't start at all (but the stubdomain runs). I try to reproduce it. In case somebody sees this again it would be good to post:
|
Once one VM ( After enabling debug mode to access it on VGA console, I could see grub boot screen. I noticed After line When I tried this another time, the same as above happened, but I could see a bit more.
and automatically terminated. |
Thanks. The rootfs not found error is something else than I have been thinking about. And probably something else than @marmarek described (since here we see kernel output). @adrelanos what kernel and initramfs do you have in this template? Is it new enough to have the updated script for rootfs mounting in initramfs? |
If you want this output also in the xen guest console you need to add |
It's a debian-8 template, cloned and upgraded to debian-stretch.
Does above look recent enough? Probably a separate bug indeed. Perhaps no one has tried a debian-stretch with VM kernel yet? hypervisor.log is now populated (without root fs error - which is easy to disable - by disabling VM kernel and debug mode). Sent to @marmarek and @HW42. Should I redo the other logs or provide something else? |
Do you have |
@adrelanos do you still have startup problems with |
Progress here, how awesome! :) I didn't look into this ticket for a few days and didn't test my Qubes R4 notebook much. Too bad git commits referenced here don't e-mail notify me. Didn't notice there the updated package that may fix it. Anyhow. For the little testing I did, I didn't notice any VM startup issues. |
Qubes OS version:
R4 RC1 with all upgrades from Qubes testing
Affected TemplateVMs:
debian-stretch
(Cloned debian-8 template, upgraded to stretch and Qubest testing.)
Steps to reproduce the behavior:
Unclear. Happening after running for a while. First everything works, then no more VMs can be started.
Speculation: Might happen when starting too many VMs too quickly. Multiple starts/shutdowns of VMs too quickly.
Does a long running qrexec such as for copying new packages downloaded using qubes-dom0-update from UpdateVM to dom0 like it could block other qrexec (such as starting VMs) operations?
Expected behavior:
Qrexec (starting VMs functional) / sudo xl console vmname functional.
Actual behavior:
Even
sudo xl console vmname
does not work. Shows:Or after using
qvm-shutdown vm-name
followed byqvm-start vm-name
.qvm-start vmname
not doing anything. It outputs nothing and exits with return code0
.General Notes:
What debug output would be useful?
The text was updated successfully, but these errors were encountered: