Closed polijh closed 2 years ago
@bennoleslie @stevebob @jashank @ajaysusarla @lsf37 Can you help me with this problem? thanks!
Sorry can't help you with that one, I'm no expert on VMs. @Ivan-Velickovic can you help?
@polijh when you add commands or machine output to an issue, please surround the input/output by ``` and ``` (see GitHub markdown syntax), because GitHub rendering gets confused otherwise which makes the issue very hard to read. Example:
``` some output # another line ```
will show up as
some output
# another line
I've added these to your post, so nothing to do for now, just for future issues.
Sorry can't help you with that one, I'm no expert on VMs. @Ivan-Velickovic can you help?
@polijh when you add commands or machine output to an issue, please surround the input/output by
and
(see GitHub markdown syntax), because GitHub rendering gets confused otherwise which makes the issue very hard to read. Example:
some output # another line
will show up as
some output # another line
I've added these to your post, so nothing to do for now, just for future issues.
Thanks for your reply, I solved the problem by replacing a self-compiled linux kernel and the previous modification on psci node. It seems that the kernel Image provided by this repo has some problems or some debug prints are not removed. And the processing of the psci node by the function generate_psci_node caused some problems
I followed the tutorial at https://github.com/seL4/camkes-vm-examples and tried to use qemu to simulate the environment of arm64 to run sel4 and start the linux virtual machine. At present, the single-core case can run correctly, but the multi-core error is reported: This is my operation
I noticed that the fdt is not being generated correctly. Debugging with gdb, I found that sel4 will generate psci nodes for fdt, so I make changes:
Finally, I thought I entered the linux kernel, but there is a loop of printing:
@ Gerwin Klein Can you help me with this problem?