Hi Dubravko, I would like to check: What's the latest status for your new board enabling? Regards Yin, Fengwei

Notice: Join ACRN’s TCM meeting with WebEx till Nov. 2019 Due to Zoom’s connection issue in PRC mainland recently, we have to use WebEx to replace Zoom for ACRN TCM meeting temporarily. We’ll

Notice: Join ACRN’s TCM meeting with WebEx till Nov. 2019 Due to Zoom’s connection issue in PRC mainland recently, we have to use WebEx to replace Zoom for ACRN TCM meeting temporarily. We’ll

Hi all, We are very pleased to announce Version 1.3 release of ACRN. You can see the release blog from https://projectacrn.org/blog/ and detailed Release Notes in website

<Cancel the meeting this week due to PRC holiday> Project ACRN: A flexible, light-weight, opensource reference hypervisor for IoT devices https://projectacrn.org || https://github.com/projectacrn

Hi Dubravko, For SOS kernel, I suppose you could build it based on our acrn-kernel with igb enabled. It looks like the serial port is a little bit mess. From dmesg_nohv.log, we could see following

Hi everyone, We've been busy bringing up some new hardware so it took me some time to respond. We are very grateful for all the assistance. I have uploaded the requested new logs to

Hello, I'm completely new to ACRN (only having learned about it yesterday). Let me know if this is not the proper group to post this question to. Should ACRN support any OS or does the OS require

Notice: Join ACRN’s TCM meeting with WebEx till Nov. 2019 Due to Zoom’s connection issue in PRC mainland recently, we have to use WebEx to replace Zoom for ACRN TCM meeting temporarily. We’ll

Hi Dubravko, The UP2 board uses realtek network controller. I believe the reason that your network can't work is the network controller is not enabled in SOS kernel. Could you please find out the

Notice: Join ACRN’s TCM meeting with WebEx till Nov. 2019 Due to Zoom’s connection issue in PRC mainland recently, we have to use WebEx to replace Zoom for ACRN TCM meeting temporarily. We’ll

Hi Dubravko, I only see following message from your sos kernel log: [ 1.200862] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 4.1.0-k [ 1.201695] ixgbevf:

Hi Dubravko, Which ttyS is used for console depends on your hardware design. You need to check with your hardware engineer to figure out which ttyS is used for console. If you are using the UP2

Hi Conghui, Yes. Emulated ttyS0 and physical ttyS1 share same irq. But there is no user of ttyS1. we can't see ttyS0/ttyS1 share irq4 in interrupt dump. But as Anthony said, the emulated ttyS0 share

Hi Dubravko， Checkedifconfig_log_20190913.log you uploaded: acrn-br0 Link encap:Ethernet HWaddr F2:14:63:23:6B:FD inet6 addr: fe80::f014:63ff:fe23:6bfd/64 Scope:Link

Hi, I have tried: compiling ACRN release version and setting console=ttyS2 (an earlier suggestion) = no improvement using ACRN release version and removing console=ttySx setting = the system is

Hi Dubravko, In SOS, vuart is sharing irq 4 with idma, that may cause issue. I think you are using debug version, can you try release version? There is no ttyS0 in release version. And please

I mean removing both hvlog=2M@0x1FE00000 and memmap=2M$0x1FE00000, that disables HV log. We can make hvlog optional, if hvlog is not specified, acrn log driver should allocate sbuf just like acrn

“memmap=2M$0x1FE00000” will reserve the memory for HV log; There is stability issue if no this parameter in cmdline(memory used by kernel was overwrite by HV log); Fengwei can give more detail

“memmap=2M$0x1FE00000” SOS kernel parameter is platform specific, can we remove “memmap=2M$0x1FE00000” by default? The only usage of “memmap=2M$0x1FE00000” is to check crack log,