errors creating symbolic links
hello. I try to compile qemu 7.1 on windows but it is not possible, I tried with mingw through cygwin, but cygwin does not have all the necessary dependencies. I tried with msys2, this if ls has with mingw, the problem with msys2 is that it cannot create symbolic links during the compilation, I have searched a lot but the only thing I find regarding this is that tar cannot decompress files that contain symbolic links, they indicate that instead use bsdtar, in my case that doesn't work for me since the problem I have is when ln tries to create the symbolic links, I have tried to change the permissions but it still doesn't work, how could I solve it?, using mingw from linux doesn't work because only the compilers are included but not the libraries
Re: Macvtap devices?
I suggest you figure out the diff between different devices by reading some online docs, e.g., the below doc. https://developers.redhat.com/blog/2018/10/22/introduction-to-linux-interfaces-for-virtual-networking Here is how I setup a software-only environment to play with macvtap device. https://github.com/finallyjustice/sample/blob/master/kvm/macvtap.txt Dongli Zhang On 9/2/22 4:17 PM, X Tec wrote: > I have used the -netdev tap,[...] options before, though almost exclusively > for bridged networking. > > I understand this setup uses tap (or tun/tap?) virtual devices for the > virtual machines. > > But, what are "macvtap" devices really? > I saw the term while reading some libvirt docs for comparison purposes; they > particularly seem to favor these devices... > But even after internet searching I was not able to understand them. > > So, if someone could help, > What are they, or what's their difference with "normal" tap devices commonly > used in QEMU? > Are macvtap devices supported in QEMU? How can one use them? > > Thanks beforehand. >
Re: Arm64 ELF not loading
On Sat, 3 Sept 2022 at 02:30, Little Tree wrote: > > Hi, > > I have built a simple hello world program for aarch64 like this > > $aarch64-none-elf-gcc -c -march=armv8-a -g hello.c hello.o > $aarch64-none-elf-gcc -specs=aem-ve.specs -Wl,-Map=linkmap.txt hello.o -o > hello.axf > > Then I tried to load and execute the file QEMU as given below > > $ qemu-system-aarch64 -semihosting -m 128M -nographic -monitor none -serial > stdio -machine virt,gic-version=2,secure=on,virtualization=on -cpu > cortex-a53 -kernel hello.axf -S -gdb tcp::9000 > > I have also tried another method for loading > $qemu-system-aarch64 -device loader,file=./hello.axf -machine virt -cpu max > -m 256M -S -gdb tcp::9000 > > In both the cases it looks like the binary is not loaded properly > > $ readelf -h hello.axf | grep Entry > Entry point address: 0x80001148 > > (gdb) target remote localhost:9000 > Remote debugging using localhost:9000 > 0x in ?? () > (gdb) disas _start > Dump of assembler code for function _start: >0x80001148 <+0>: .inst 0x ; undefined >0x8000114c <+4>: .inst 0x ; undefined >0x80001150 <+8>: .inst 0x ; undefined >0x80001154 <+12>: .inst 0x ; undefined >0x80001158 <+16>: .inst 0x ; undefined >0x8000115c <+20>: .inst 0x ; undefined > > > Could you please shed some light why this binary is not loading properly? The virt board has no RAM at address 0x8000_, so QEMU has successfully loaded your ELF file into nothing. You need to link your baremetal binary so that it is linked where the RAM is (or the flash, if you prefer)... -- PMM
VDE Switch Error
I am using QEMU 6.2 on Ubuntu 22.04 LTS with the vde2 package. When running the following commands, I am encountering an error. Any help would be appreciated. What am I doing wrong? And what should I do to get around this error? vde_switch -sock /tmp/myswitch qemu-system-x86_64 -m 8G -cpu host -enable-kvm -nic vde,sock=/tmp/myswitch qemu-system-x86_64: -nic vde,sock=/tmp/myswitch: Parameter 'type' expects a netdev backend type
