-
Notifications
You must be signed in to change notification settings - Fork 70
WIP: Debug: Enable VM debug console #658
base: master
Are you sure you want to change the base?
Conversation
kubernetes qa-passed 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
CI is failing though. I suspect we probably have a vendor or merge dep? In f26 we have:
|
Hmm, actually the CI run was successful for all 3 runs. Looks like there might be an issue with the jenkins-github plugin @sboeuf ? |
@grahamwhaley - the |
kubernetes qa-passed 👍 |
1 similar comment
kubernetes qa-passed 👍 |
44af25c
to
f28f5a2
Compare
kubernetes qa-passed 👍 |
Hi @mcastelino - this requires an update to the tests. From the CI logs:
|
f28f5a2
to
53c685c
Compare
kubernetes qa-passed 👍 |
Enable the VM debug console whenever the VM Kernel debug is enabled. Fixes: clearcontainers#559. Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
53c685c
to
b59bfde
Compare
kubernetes qa-passed 👍 |
for further debug. | ||
|
||
``` | ||
socat /run/virtcontainers/pods/<pod id>/console.sock |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a $
prompt for consistency with the rest of the doc please. Also, presumably we need a sudo
in there too?
@iphutch - please can you review these doc changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Hi @mcastelino - just one final nit in the docs from me. @iphutch - please could you review the doc changes? |
@@ -44,3 +44,12 @@ to enable kernel boot logs using the configuration file. | |||
|
|||
This will result in the `cc-proxy` log being printed on the terminal. This method | |||
can also be used to capture the logs in a specific `cc-proxy` file. | |||
|
|||
5. Connect to the Virtual machine console |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use all lower case:
s/Virtual/virtual
for further debug. | ||
|
||
``` | ||
socat /run/virtcontainers/pods/<pod id>/console.sock |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
|
||
5. Connect to the Virtual machine console | ||
|
||
If the kernel boots successfully then the virtual machine console can be accessed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should avoid using an "if" clause unless we provide options for when the kernel does not boot successfully.
Let us ensure that our instructions are accurate and assume the reader has followed the instructions exactly:
After the kernel boots, the virtual machine console can be accessed for further debugging.
kubernetes qa-failed 👎 |
Hi @mcastelino - just a reminder that this PR needs a few minor tweaks. |
kubernetes qa-failed 👎 |
4 similar comments
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
Hi @klynnrif, @rcaballeromx - I'm assuming @iphutch won't be able to complete this review so could one of you take a look and if you're happy, we'll force-merge this as we will have the requisite doc team approval. |
@jodh-intel @rcaballeromx the suggestions @iphutch made lgtm. All good to me with those changes. Thanks! |
kubernetes qa-failed 👎 |
3 similar comments
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
6 similar comments
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
kubernetes qa-failed 👎 |
Enable the VM debug console whenever the VM Kernel debug
is enabled.
Fixes: #559.
Has a dependency on having a updated agent being installed in the container rootfs to add the new systemd services.
clearcontainers/agent#122
Signed-off-by: Manohar Castelino manohar.r.castelino@intel.com