i've got two cleanly build mips64-764 initrds (based on cross linux from
scratch, gcc 6.1 and linux kernel 4.7) that i want to boot with qemu
initrd.cpio ~14.5 MB
big_initrd.cpio ~323.4 MB
mips64-softmmu/qemu-system-mips64 -M malta -m 1GB -nographic -monitor
telnet::4440,server,nowait -serial
On 08/09/2016 11:29, Dennis Luehring wrote:
i've got two cleanly build mips64-764 initrds (based on cross linux
from scratch, gcc 6.1 and linux kernel 4.7) that i want to boot with qemu
initrd.cpio ~14.5 MB
big_initrd.cpio ~323.4 MB
mips64-softmmu/qemu-system-mips64 -M malta -m 1GB -nographic
On 8 September 2016 at 10:29, Dennis Luehring wrote:
> small tests show that this seem not to be a kernel or gcc bug (same problem
> with linux 4.5,4.6.4,4,7, gcc 5.2,5.3,6.1)
That doesn't show that it's not a kernel bug -- it just shows
that if it is a kernel bug it's been around since at least
Stephen,
When building the various software packages use the following configuration
--prefix like this:
--prefix=/opt/qemu/qemu-${VARIANT}
When you do the "make install" you will get the software installed in a
directory structure like this (where VARIANT has values of RISC-V, NVMe, e
Hello, I am writing because I am trying to emulate and debug some code for
an ARM chip. My goal is to have QEMU emulate the code and output all 8
UARTs/USARTs, some GPIOs, and some SPIs to the host Linux machine into
/dev/uart1 ... /dev/uart8, /dev/gpio1 etc. However I can only seem to find
example
On 8 September 2016 at 13:32, Donald R Laster Jr wrote:
> Stephen,
>
> When building the various software packages use the following configuration
> --prefix like this:
>
> --prefix=/opt/qemu/qemu-${VARIANT}
If you're just doing local testing (where running QEMU
from the command line is
that makes it more clear - thx
Am 08.09.2016 um 20:54 schrieb Jakob Bohm:
According to your kernel message log, the guest machine only
has 256MiB RAM:
memory: 1000 @ (usable)
P.S.
I think you swapped the two log file names.
Am 08.09.2016 um 20:21 schrieb Peter Maydell:
One thing that does stand out is that the malta memory map
has the full 2G of RAM starting at 0x8000, but also
has a 256M window (alias) into that RAM starting at 0.
I think that if the kernel is linked such that it loads
at the 0 alias address ra
On 09/09/2016 06:42, Dennis Luehring wrote:
that makes it more clear - thx
Am 08.09.2016 um 20:54 schrieb Jakob Bohm:
According to your kernel message log, the guest machine only
has 256MiB RAM:
memory: 1000 @ (usable)
P.S.
I think you swapped the two log file
Hi All,
We are seeing an interesting scenario during the throughput tests.
*System Configuration:*
Two socket having 10 cores each.
VM -0 cores are pinned to phy cores 2-to-9 on socket# 0 and emulator pin
pinned on core 1
VM-1 cores are pinned to 12-19 on socket# 1 and emulator pin pinned
10 matches
Mail list logo
