Replies: 1 comment
-
Hello, Regarding this issue, it appears there was a problem with memory allocation. It now works correctly after reducing the memory size allocated to each Linux VM by half. I would like to increase the total memory capacity for Bao itself, but I will investigate that separately at a later time. For now, since this particular issue has been resolved, I will close it. Thank you again for the Bao project. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. Thank you for the wonderful Bao project.
I am trying to run two Linux VMs on the Bao Hypervisor, but it seems the CPU allocation for one of the VMs is not working correctly, and I would appreciate some advice.
I am allocating two cores to each VM.
One Linux VM outputs to UART, and the other Linux VM has a virtconsole allocated via MMIO.
I can confirm that Linux is booting on both VMs, but when I actually check the one outputting to UART, only one CPU is allocated.
I can see an error message when the Bao Hypervisor starts, but I couldn't find the same error string in the source code, so I'm not sure what the issue is.
Below, I will show my environment and config, logs.
qemu-system-riscv64
version: 8.2.2bao-hypervisor
version: main branchLinux Image
: I use bao-demos's buildrootconfig.c
linux.dts
linux2.dts
QEMU command
Bao Hypervisor Boot log
Linux VM2 log
Initially, I thought the CPU reg values assigned in the Linux DeviceTree should be unique for each, so I had assigned 0x02 and 0x03 to Linux VM2. However, this caused an error like the one shown below, and the Linux VM wouldn't boot. That's why I changed to the current DeviceTree configuration.
My apologies for my broken English, but I would appreciate it if you could check it.
Beta Was this translation helpful? Give feedback.
All reactions