On Fri, 11 Aug 2023 at 11:34, Mario Marietto wrote:
>
> ok. I will recompile a qemu version lower than 5.2. I've asked all around and
> someone says that I should use 5.1,someone else 4.9. Which version should I
> use ? And,please can you point me to a good tutorial that can teach me the
>
On Fri, 11 Aug 2023 at 12:19, Mario Marietto wrote:
> Anyway,can you tell me where is the branch 5.1 for the qemu source code for
> armhf ?
You want the "v5.1.0" git tag.
-- PMM
ok. Can you share the github address ? I found the source code for x86-x64
but not for armhf.
On Fri, Aug 11, 2023 at 1:49 PM Peter Maydell
wrote:
> On Fri, 11 Aug 2023 at 12:19, Mario Marietto
> wrote:
> > Anyway,can you tell me where is the branch 5.1 for the qemu source code
> for armhf ?
>
ok. I will recompile a qemu version lower than 5.2. I've asked all around
and someone says that I should use 5.1,someone else 4.9. Which version
should I use ? And,please can you point me to a good tutorial that can
teach me the procedure to recompile it ? I might find it by myself,but what
I need
I know. I've been working on this project since 1 year ago. But I'm
stimulated by the "intellectual" challenge and even because old hardware
should not be thrown away only because it is old. If it is still useful,it
could be reused. The ARM chromebook in my opinion has been a nice toy to
play
On Thu, 10 Aug 2023 at 18:28, Mario Marietto wrote:
>
> ---> You can't use KVM with the vexpress-a15 board. The only Arm guest
> machine that will work with KVM is the "virt" board.
>
> point 1)
>
> On the virtual open systems website they used the vexpress-a15 board. You can
> read by yourself
I made some progress,but unfortunately I've got an error :
root@devuan:~/Desktop/qemu-v5.1.0# ./configure --target-list=arm-softmmu
--enable-opengl --enable-gtk --enable-kvm --enable-guest-agent
--enable-spice --audio-drv-list="oss pa" --enable-libusb
no errors here.
Hello, I tried to compile executable for Arm64 some time ago. There is no
special branch of QEMU for Arm hosts, you just need to find a toolchain to
cross-compile for Arm. Try to look at Linaro site, they have complete
cross-configured GCC toolchains. And then try script like this (note the
I'm on devuan 4,so this is the default gcc compiler :
root@devuan:~/Desktop/qemu-v5.1.0# gcc --version
gcc (Debian 10.2.1-6) 10.2.1 20210110
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for
On Fri, 11 Aug 2023 at 13:30, Mario Marietto wrote:
>
> ok. Can you share the github address ? I found the source code for x86-x64
> but not for armhf.
There is not, and has never been, a separate git tree for
different guest architectures. It is all in the one
git tree at
Dear Mario,
Am 11.08.23 um 14:29 schrieb Mario Marietto:
ok. Can you share the github address ? I found the source code for
x86-x64 but not for armhf.
The source code archive [1] contains the code for all architectures.
From that you configure your build environment, where you can specify
ok thanks. Are the following parameters correct still today ? something is
missing ? thanks.
a) to compile qemu :
./configure \
--target-list=arm-softmmu \
--audio-drv-list=alsa,pa \
--enable-fdt --enable-kvm --enable-sdl
b) to run a guest os (I want to virtualize FreeBSD)
I've thought to compile it directly on the devuan 4 installed on the ARM
chromebook.
On Fri, Aug 11, 2023 at 3:20 PM Валентин wrote:
> Hello, I tried to compile executable for Arm64 some time ago.
>
> There is no special branch of QEMU for Arm hosts, you just need to find a
> toolchain to
On Fri, 11 Aug 2023 at 17:05, Mario Marietto wrote:
>
> I made some progress,but unfortunately I've got an error :
>
> root@devuan:~/Desktop/qemu-v5.1.0# ./configure --target-list=arm-softmmu
> --enable-opengl --enable-gtk --enable-kvm --enable-guest-agent --enable-spice
> --audio-drv-list="oss
These are the config parameters if the hardware is x86_64 :
./configure --target-list=x86_64-softmmu --enable-opengl --enable-gtk
--enable-kvm --enable-guest-agent --enable-spice --audio-drv-list="oss pa"
--enable-libusb
I don't know if those parameters are valid even for armhf.
On Fri, Aug
> I've thought to compile it directly on the devuan 4 installed on the ARM
> chromebook. If you have native Arm toolchain, it's even simpler then – just
> try to "./configure" and "make". QEMU v5.1 will compile with at least GCC
> v4.8. With best regards, Valentine.
On Fri, 11 Aug 2023 at 14:44, Валентин via wrote:
>
> > I've thought to compile it directly on the devuan 4 installed on the ARM
> > chromebook.
>
> If you have native Arm toolchain, it's even simpler then – just try to
> "./configure" and "make".
Specify a --target-list= option to configure
ok. I've been lucky. Qemu compiled successfully. Now I'm going to
execute this command :
qemu-system-arm \
-enable-kvm -serial stdio -kernel zImage \
-m 512 -M vexpress-a15 -cpu cortex-a15 \
-drive file=/mnt/fisso/bhyve/img/Linux/ubuntu2210.img,id=virtio-blk,if=none
\
-device
On Fri, 11 Aug 2023 at 18:52, Mario Marietto wrote:
>
> ok. I could extract the kernel files (so,between the qemu parameters I should
> put : initrd and vmlinuz,right ? How ?
>
> -enable-kvm -serial stdio -kernel vmlinux -what here initrd \
>
> from the ubuntu 22.10 img,but I'm sure that it does
> between the qemu parameters I should put : initrd and vmlinuz,right ? Try
> "-kernel kernel.img -initrd initrd.img". Oh, too late. :) By the way, I
> myself didn't experiment much with qemu-system-arm, but people successfully
> ran hdd/iso images with EFI bioses (for Arm architecture), if
I remember. So,more or less,it should be something like this :
qemu-system-arm \
-enable-kvm -serial stdio \
-m 512 -M virt -cpu cortex-a15 \
-drive file=/mnt/fisso/OS/FreeBSD/FreeBSD-13.2.qcow2,id=virtio-blk,if=none \
-device virtio-blk,drive=virtio-blk \
-device
On Fri, 11 Aug 2023 at 18:27, Mario Marietto wrote:
>
> ok. I've been lucky. Qemu compiled successfully. Now I'm going to execute
> this command :
>
> qemu-system-arm \
> -enable-kvm -serial stdio -kernel zImage \
> -m 512 -M vexpress-a15 -cpu cortex-a15 \
> -drive
>
ok. I could extract the kernel files (so,between the qemu parameters I
should put : initrd and vmlinuz,right ? How ?
-enable-kvm -serial stdio -kernel vmlinux -what here initrd \
from the ubuntu 22.10 img,but I'm sure that it does not have any dtb file.
I never needed a dtb file when I booted my
I've found the right uefi file to use :
/usr/share/AAVMF/AAVMF32_CODE.fd
so now every piece is on the right place (I hope) :
qemu-system-arm \
-enable-kvm -serial stdio \
-m 512 -M virt -cpu cortex-a15 \
-drive file=/mnt/fisso/OS/FreeBSD/FreeBSD-13.2.qcow2,id=virtio-blk,if=none \
I think that I've found it :
qemu-efi-arm/stable 2020.11-2+deb11u1 all
UEFI firmware for 32-bit ARM virtual machines
On Fri, Aug 11, 2023 at 9:23 PM Mario Marietto
wrote:
> I remember. So,more or less,it should be something like this :
>
> qemu-system-arm \
> -enable-kvm -serial stdio \
> -bios "*.fd" Try "-pflash *.fd" or "-drive if=pflash,format=raw,file=*.fd",
> if it works for Arm machines. I saw that OVMF developers didn't recommend to
> use "-bios" because image will be mounted as ROM and will not be able to save
> bios settings. With best regards, Valentine.
26 matches
Mail list logo