-
Notifications
You must be signed in to change notification settings - Fork 679
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
document how to clean up from a previous libvirt make staging run #4993
Comments
Following up after troubleshooting errors during If you see this error, start over, all the way over. Keep reading... Also, be prepared... This is what I tried when attempting to reinstall staging:
I saw an error during
I saw another error during make staging that said to look at the logs, which said:
Once again after opening the app vm from libvirt's Virtual Machine app, see this error once again: |
Thanks for the detailed feedback, @creviera. I'll cobble together some docs clarifications, and tag you for review. One major oversight is that |
@creviera Which hardware is this? I am guessing the standard T470? |
X1 Carbon (6th Gen) |
Today I downgraded the kernel via: The result: I get passed the error that both @kushaldas and I shared above and am able to see and use the login screen using the libvirt Virtual Machine Manager application. Interestingly, it's only the console login that is broken -- I'm able to log in via ssh just fine using |
thanks for the report @creviera . The console/TTY kernel settings are identical for our 4.4 and 4.14 configurations. I will test on hardware to see if I can reproduce, and try to build on the latest grsecurity patch to see if it resolves the issue (the kernel version is still 4.14.154, but there have been a couple of grsecurity patches released since). Since it doesn't immediately block development (the VMs work, ssh works, but it only limited to console access) we can track this issue as part of general (kernel) QA for 1.2.0. |
I was able to reproduce the console hang in staging, and can fix it by switching the VM video driver to Virtio from Cirrus. I've found other reports of Cirrus misbehaving in VMs; we could specify a different video driver in the Vagrantfile. |
Good catch @rmol , it may have to do with the initial kernel configuration, I did not explicitly enable any virtualization settings (either host nor guest). Perhaps the virtio video support is not included due to guest virtualization not enabled. Given that the VMs work in libvirt otherwise, the issue may be easier to fix in the Vagrantfile, as you describe. If these (and the console) work in virtualbox, i think your suggestion sounds like the quickest path to resolution |
latest kernel (4.14.154-grsec-securedrop) does work in virtualbox with console |
I got stuck on this today :( |
stuck on logging in to the console to staging machines running on libvirt (asking because if so #5005 contains a fix) or fully destroying previously provisioned staging VMs on libvirt? |
@conorsch and @rmol have some work in progress to close this issue in https://github.com/freedomofpress/securedrop/compare/4993-explain-libvirt-cleanup-procedures |
During the 12/5-12/18 sprint, we'll aim to get a PR in for the changes above, and @zenmonkeykstop will help investigate whether this is sufficient (together with the #5005 fix which has landed) to resolve the types of hangs experienced by Kushal and Allie above. |
Reopening until we sort out #5066. |
#5066 was merged, so closing. |
Description
this is currently not documented and a few developers are having trouble with this
The text was updated successfully, but these errors were encountered: