Geoffroy Van Cutsem
toggle quoted message
Show quoted text
Have you observed the same problems on the UP2 board?
From: acrn-users@... <acrn-users@...>
On Behalf Of Liu, Fuzhong
Sent: Thursday, September 12, 2019 7:15 AM
Subject: Re: [acrn-users] Setting up ACRN on a new board with Apollo Lake
All issues you mentioned are for Service OS, right?
Clear Linux image newer than 30900 fixed “memmap=2M$0x1FE00000” issue
ACRN git commit hash is 555a03db99621c6a9d3bea0933c65db9dee44c46. I am getting identical behavior with ACRN that I've compiled, as well as with ACRN installed by Clear Linux (version
dmesg output from SOS
/proc/interrupts from SOS
loader.conf from EFI partition
acrn.conf (here I've verified that root UUID is correct, and I've had to delete settings related to hypervisor memory log because otherwise it crashed)
Our board has 8 GB of memory and 64 GB MMC, and is similar to Up Squared and Leaf Hill CRB.
On 2019/9/10 下午9:00, Dubravko Moravski | Exor Embedded S.r.l. wrote:
> Hello everyone,
> I work for Exor Embedded and we are developing a new board with an
> Apollo Lake E3940 CPU. We would like to run ACRN on it. Indeed,
> following the instructions on
> https://projectacrn.github.io/latest/index.html I've managed to get it
> running, dmesg among other things says:
> Hypervisor detected: ACRN
> ACRNTrace: Initialized acrn trace module with 4 cpu
> systemd: Detected virtualization acrn.
> However, it's not really usable. We have following issues:
> * mouse cursor jumps around in a weird way, like there is some problem
> with switching video buffers
> * we can't open the Terminal in any way, there's always a message:
> "There was an error creating a child process for this terminal.
> Failed to open PTY: Permission denied"
> * network doesn't work
> * everything works much slower than usual
> When not running with hypervisor, everything works.
> We've noticed some differences between dmesgs when running the same
> kernel with and without hypervisor, but so far we were unable to figure
> out if any of these differences is significant.
> We would appreciate if you have any hints for us, either what is exactly
> our problem, or at least how we should continue to debug the system.
Could you share:
1. ACRN last git commit hash
2. dmesg output in your SOS
3. the output of cat /proc/interrupt in your SOS
> Best regards,
> Dubravko Moravski
> *Dubravko Moravski*
> /SW engineering/
> *Exor Embedded S.r.l.*
> p: +38 512455659 <tel:+38 512455659> m:+38 5915402413 <tel:+38 5915402413>
> a: Slavonska avenija, 50, Zagreb, Croatia, 10000
> w: exorint.com <https://exorint.com/>
> Prima di stampare pensa ai costi ambientali. Please consider the
> environment before printing this email.
> Privacy <https://www.exorint.com/it/privacy>
di stampare pensa ai costi ambientali. Please consider the environment before printing this email.