Wednesday, 2020-07-08

« Tuesday, 2020-07-07 Index Thursday, 2020-07-09 »
*** bpradipt has joined #kata-dev04:38
*** sameo has joined #kata-dev05:23
*** dklyle has quit IRC06:03
*** Yarboa has joined #kata-dev06:10
*** fgiudici has joined #kata-dev06:44
*** jodh has joined #kata-dev07:03
kata-irc-bot<abdasgupta> Hi @fidencio,  Yes. That was the problem. Rust compiler was picking up the cpu architecture as powerpc64. List of the architectures can be found here: https://doc.rust-lang.org/core/arch/index.html07:13
kata-irc-bot<abdasgupta> So I changed to ```target_arch = "powerpc64"``` in src/agent/src/linux_abi.rs07:14
kata-irc-bot<fidencio> @abdasgupta Would you send us a patch?07:14
kata-irc-bot<abdasgupta> Yes. I wl..07:14
kata-irc-bot<fidencio> Thanks, appreciated! :-)07:15
kata-irc-bot<abdasgupta> There is another problem in the PR https://github.com/kata-containers/kata-containers/pull/370/files while building on powerpc64le. Let me mention it there07:16
kata-irc-bot<abdasgupta> On another note, after successfully building the kata agent, I hit this07:21
kata-irc-bot<abdasgupta> ```target/powerpc64le-unknown-linux-gnu/release/kata-agent {"msg":"announce","level":"INFO","ts":"2020-07-08T03:17:45.817710529-04:00","source":"agent","subsystem":"root","pid":"2035951","name":"kata-agent","version":"0.1.0","agent-type":"rust","agent-version":"1.4.5","api-version":"0.0.1","agent-commit":""} thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Socket("EAFNOSUPPORT: Address family not supported by07:21
kata-irc-botprotocol")', src/rpc.rs:1436:18 stack backtrace:    0:        0x13ee00468 - backtrace::backtrace::libunwind::trace::hd0dc03cc1bedb5c1                                at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86    1:        0x13ee00468 - backtrace::backtrace::trace_unsynchronized::hfea553d11e75ca2a                                at07:21
kata-irc-bot/cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66    2:        0x13ee00468 - std::sys_common::backtrace::_print_fmt::h7e9c32d48692e946                                at src/libstd/sys_common/backtrace.rs:78    3:        0x13ee00468 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h6765b49c01c47aa5                                at src/libstd/sys_common/backtrace.rs:59    4:07:21
kata-irc-bot       0x13ee334c4 - core::fmt::write::h638dfaeca4693d23                                at src/libcore/fmt/mod.rs:1069    5:        0x13edf77a0 - std::io::Write::write_fmt::hafc73ab3b9fb167b                                at src/libstd/io/mod.rs:1504    6:        0x13ee04054 - std::sys_common::backtrace::_print::h40bdb4b47bc84644                                at src/libstd/sys_common/backtrace.rs:62    7:        0x13ee04054 -07:21
kata-irc-botstd::sys_common::backtrace::print::h8838e24051f7eeaf                                at src/libstd/sys_common/backtrace.rs:49    8:        0x13ee04054 - std::panicking::default_hook::{{closure}}::heb6913e23d192b66                                at src/libstd/panicking.rs:198    9:        0x13ee03c88 - std::panicking::default_hook::hb2d04042fa540878                                at src/libstd/panicking.rs:218   10:        0x13ee049b4 -07:21
kata-irc-botstd::panicking::rust_panic_with_hook::h9d57f5a072fcfe91                                at src/libstd/panicking.rs:511   11:        0x13ee043d8 - rust_begin_unwind                                at src/libstd/panicking.rs:419   12:        0x13ee2fe4c - core::panicking::panic_fmt::hb696be953e22a1e1                                at src/libcore/panicking.rs:111   13:        0x13ee2fbe0 - core::option::expect_none_failed::h330d6ef81521e6ed07:21
kata-irc-bot                   at src/libcore/option.rs:1268   14:        0x13e9cb304 - kata_agent::rpc::start::h3881b816e7355a15   15:        0x13e9e3d30 - kata_agent::main::he9884f4df2f6dcda   16:        0x13ea00b90 - std::rt::lang_start::{{closure}}::h86394a3bed3aee89   17:        0x13ee00e34 - std::rt::lang_start_internal::{{closure}}::{{closure}}::hd32df984fa119da9                                at src/libstd/rt.rs:52   18:        0x13ee00e34 -07:21
kata-irc-botstd::sys_common::backtrace::__rust_begin_short_backtrace::hefe1080732f46deb                                at src/libstd/sys_common/backtrace.rs:130   19:        0x13ee04e08 - std::rt::lang_start_internal::{{closure}}::hc0a5ce7fb754bd0f                                at src/libstd/rt.rs:52   20:        0x13ee04e08 - std::panicking::try::do_call::h55b5524f28576f3d                                at src/libstd/panicking.rs:331   21:07:21
kata-irc-bot0x13ee04e08 - std::panicking::try::h1d5a2592d7aa1264                                at src/libstd/panicking.rs:274   22:        0x13ee04e08 - std::panic::catch_unwind::h34936b12fbe5f1e4                                at src/libstd/panic.rs:394   23:        0x13ee04e08 - std::rt::lang_start_internal::h112407a12b285e37                                at src/libstd/rt.rs:51   24:        0x13e9e5928 - main   25:     0x7fffad6949f8 -07:21
kata-irc-botgeneric_start_main.isra.0   26:     0x7fffad694be4 - __libc_start_main   27:                0x0 - <unknown> Segmentation fault (core dumped)```07:21
kata-irc-bot<abdasgupta> I am looking into the format of `const VSOCK_ADDR: &str = "vsock://-1";` in `src/main.rs` . Any suggestion is welcome on this.07:21
kata-irc-bot<fidencio> @bergwolf:  ^07:28
*** hashar has joined #kata-dev07:39
kata-irc-bot<bergwolf> @abdasgupta Does your guest kernel support vsock? Looks like a vsock error `"EAFNOSUPPORT: Address family not supported by protocol`07:48
*** th0din has quit IRC08:05
*** sgarzare has joined #kata-dev08:07
*** th0din has joined #kata-dev08:11
*** amorenoz has quit IRC08:33
*** amorenoz has joined #kata-dev08:33
kata-irc-bot<abdasgupta> @bergwolf Yes, vsock is supported on ppc64le..09:42
*** sameo has quit IRC09:49
kata-irc-bot<abdasgupta> I am still looking into it, will update you with my findings.. Thank you09:57
kata-irc-bot<bergwolf> yeah, please check if vsock is enabled in your guest kernel.09:59
*** sameo has joined #kata-dev10:09
*** fgiudici has quit IRC10:34
*** fgiudici has joined #kata-dev10:34
kata-irc-bot<pradipta.banerjee> Did you find the reason? I too am curious why kata-runtime list shows two entries10:59
kata-irc-bot<pradipta.banerjee> @bergwolf @fidencio any idea why `kata-runtime list` shows two entries for a single container pod11:04
kata-irc-bot<fidencio> I don't know, never check that11:05
kata-irc-bot<bergwolf> The container map is not cleaned up?11:05
kata-irc-bot<abdasgupta> I worked with @pradipta.banerjee and now kata rust agent is running fine on ppc64le. Working on the necessary PRs, I will raise the PRs shortly. Thanks @bergwolf and @fidencio11:09
kata-irc-bot<bergwolf> Great news!11:10
kata-irc-bot<pradipta.banerjee> np.. will dig into it11:13
*** pcaruana has quit IRC11:54
*** pcaruana has joined #kata-dev11:55
*** hashar is now known as hasharNap12:02
kata-irc-bot<rajasaur> there is one for the pod and one for the container12:26
kata-irc-bot<rajasaur> but yeah havent figured why yet.. Trying to build a custom rootfs so that i can debug into the console to see how this is done, but will try this asap12:27
*** devimc has joined #kata-dev12:34
*** pcaruana has quit IRC12:56
*** hasharNap is now known as hashar12:57
*** pcaruana has joined #kata-dev13:09
*** crobinso has joined #kata-dev13:53
kata-irc-bot<rajasaur> Ive followed the instructions from https://github.com/kata-containers/kata-containers/blob/2.0-dev/docs/Developer-Guide.md#set-up-a-debug-console to use a clearlinux distro with bash and coreutils installed and have been able to boot up vms using the modified image. When I try to connect to the console.sock through socat, it just hangs , Can someone help with how to connect?13:58
kata-irc-bot<rajasaur> Contents of osbuilder.yaml: https://pastebin.com/h8pacmRS14:04
*** dklyle has joined #kata-dev14:11
*** fgiudici has quit IRC14:34
*** fgiudici has joined #kata-dev14:35
*** devimc has quit IRC14:42
*** devimc has joined #kata-dev14:43
*** sameo has quit IRC15:46
*** sameo has joined #kata-dev15:49
*** hashar has quit IRC15:58
*** sameo_ has joined #kata-dev16:06
*** sgarzare has quit IRC16:08
*** sameo has quit IRC16:08
*** devimc has quit IRC16:27
*** hashar has joined #kata-dev16:47
*** fgiudici has quit IRC16:53
*** jodh has quit IRC17:08
*** crobinso has quit IRC17:42
*** hashar has quit IRC17:43
*** devimc has joined #kata-dev18:05
*** devimc has quit IRC18:05
*** hashar has joined #kata-dev18:36
*** bpradipt has quit IRC18:59
*** davidgiluk has joined #kata-dev19:25
*** sameo_ has quit IRC19:50
*** Yarboa has quit IRC19:52
*** jbryce has joined #kata-dev19:55
*** davidgiluk has quit IRC20:08
*** iamweswilson has joined #kata-dev20:13
*** stackedsax has joined #kata-dev20:23
*** hashar has left #kata-dev20:39
kata-irc-bot<archana.m.shinde> @rajasaur Can you pass `agent.debug_console` in the `kernel_params` in the configuration.toml22:21
« Tuesday, 2020-07-07 Index Thursday, 2020-07-09 »

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!