Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

shimv2 missed watching the hypervisor's console after re-FetchSandbox #2091

Closed
lifupan opened this issue Sep 27, 2019 · 0 comments
Closed

shimv2 missed watching the hypervisor's console after re-FetchSandbox #2091

lifupan opened this issue Sep 27, 2019 · 0 comments
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.

Comments

@lifupan
Copy link
Member

lifupan commented Sep 27, 2019

Description of problem

Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Expected result

(replace this text with an explanation of what you thought would happen)

Actual result

(replace this text with details of what actually happened)

@lifupan lifupan added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Sep 27, 2019
lifupan added a commit to lifupan/kata-runtime that referenced this issue Sep 27, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Sep 27, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 12, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 12, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 12, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 12, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 12, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 12, 2019
Both of the KataBuiltInProxyType and NoProxyType have the
same feature of can watch the hypervisor's console in
shimv2.

When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 17, 2019
When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 17, 2019
When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 18, 2019
When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 18, 2019
When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 18, 2019
When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 18, 2019
When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
lifupan added a commit to lifupan/kata-runtime that referenced this issue Oct 18, 2019
When do the reloading sandbox in shimv2, it's needed to
rewatch the hypervisor's console when debug enabled.

Fixes:kata-containers#2091

Signed-off-by: lifupan <lifupan@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.
Projects
None yet
Development

No branches or pull requests

2 participants