-
Notifications
You must be signed in to change notification settings - Fork 996
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
runtime-rs on Arm64 Machine: Unable to Boot Container Image using Cloud-Hypervisor #8381
Labels
Projects
Comments
brianwang12
added
bug
Incorrect behaviour
needs-review
Needs to be assessed by the team.
labels
Nov 6, 2023
brianwang12
added a commit
to brianwang12/kata-containers
that referenced
this issue
Nov 13, 2023
…-Hypervisor In the case of Cloud Hypervisor running on arm64 architecture, only arm AMBA UART (pl011) is supported as the TTY. Consequently, when enabling Hypervisor debug mode, it's essential to configure the console as "ttyAMA0" rather than "ttyS0 Fixes: kata-containers#8381 Signed-off-by: briwan01 <brian.wang@arm.com> Change-Id: I9b3dda858d2f41d9cc8f8de5328d2d76d8903d67
brianwang12
added a commit
to brianwang12/kata-containers
that referenced
this issue
Nov 13, 2023
…-Hypervisor In the case of Cloud Hypervisor running on arm64 architecture, only arm AMBA UART (pl011) is supported as the TTY. Consequently, when enabling Hypervisor debug mode, it's essential to configure the console as "ttyAMA0" rather than "ttyS0 Fixes: kata-containers#8381 Signed-off-by: briwan01 <brian.wang@arm.com>
brianwang12
added a commit
to brianwang12/kata-containers
that referenced
this issue
Nov 15, 2023
…ervisor In the case of Cloud Hypervisor running on arm64 architecture, only arm AMBA UART (pl011) is supported as the TTY. Consequently, when enabling Hypervisor debug mode, it's essential to configure the console as "ttyAMA0" rather than "ttyS0 Fixes: kata-containers#8381 Signed-off-by: briwan01 <brian.wang@arm.com>
brianwang12
added a commit
to brianwang12/kata-containers
that referenced
this issue
Nov 15, 2023
In the case of Cloud Hypervisor running on arm64 architecture, only arm AMBA UART (pl011) is supported as the TTY. Consequently, when enabling Hypervisor debug mode, it's essential to configure the console as "ttyAMA0" rather than "ttyS0 Fixes: kata-containers#8381 Signed-off-by: briwan01 <brian.wang@arm.com>
sprt
pushed a commit
to sprt/kata-containers
that referenced
this issue
Dec 1, 2023
In the case of Cloud Hypervisor running on arm64 architecture, only arm AMBA UART (pl011) is supported as the TTY. Consequently, when enabling Hypervisor debug mode, it's essential to configure the console as "ttyAMA0" rather than "ttyS0 Fixes: kata-containers#8381 Signed-off-by: briwan01 <brian.wang@arm.com>
sprt
pushed a commit
to microsoft/kata-containers
that referenced
this issue
Dec 7, 2023
In the case of Cloud Hypervisor running on arm64 architecture, only arm AMBA UART (pl011) is supported as the TTY. Consequently, when enabling Hypervisor debug mode, it's essential to configure the console as "ttyAMA0" rather than "ttyS0 Fixes: kata-containers#8381 Signed-off-by: briwan01 <brian.wang@arm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To help us understand the problem more quickly, please do the following:
$sudo ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest hello7 sh
#Actual result
ctr: failed to create shim task: Others("failed to handler message try init runtime instance\n\nCaused by:\n 0: init runtime handler\n 1: start sandbox\n 2: connect\n 3: connect agent server\n 4: connect\n 5: cannot connect to agent ttrpc server ConnectConfig { dial_timeout_ms: 10, reconnect_timeout_ms: 3000 }"): unknown
Encountering the Following Error Logs:
handshake error: malformed response code: ""","level":"DEBG","ts":"2023-11-06T06:09:59.186059964Z","subsystem":"agent","version":"0.1.0","name":"kata-runtime","source":"hello7","pid":"1177340"}
Warning: unable to open an initial console."","level":"INFO","ts":"2023-11-06T06:09:59.187190618Z","version":"0.1.0","name":"kata-runtime","pid":"1177340","source":"hello7","subsystem":"cloud-hypervisor","stream":"stdout"}
reboot: Power down"","level":"INFO","ts":"2023-11-06T06:09:59.396102532Z","version":"0.1.0","subsystem":"cloud-hypervisor","pid":"1177340","source":"hello7","name":"kata-runtime","stream":"stdout"}
INFO:vmm/src/cpu.rs:1032 -- VmExit::Shutdown"","level":"INFO","ts":"2023-11-06T06:09:59.39625404Z","source":"hello7","pid":"1177340","version":"0.1.0","subsystem":"cloud-hypervisor","name":"kata-runtime","stream":"stderr"}
INFO:vmm/src/lib.rs:1891 -- VM exit event"","level":"INFO","ts":"2023-11-06T06:09:59.396297182Z","source":"hello7","name":"kata-runtime","subsystem":"cloud-hypervisor","pid":"1177340","version":"0.1.0","stream":"stderr"}
The text was updated successfully, but these errors were encountered: