Does ppc64 or s390x support guest vIOMMU

Hi all, I am trying to implement guest vIOMMU in the testing provision of virtualization at https://github.com/teemtee/tmt/issues/2392#issuecomment-1923047732 . For ppc64 or s390x arch, I don't know whether it supports guest vIOMMU. So does it support that? If supported, how to enable guest vIOMMU

Re: QEMU plugin past, present and future examples

Robert Henry writes: > QEMU plugin experts: > > A few years I wrote a plugin for QEMU that saves the instruction stream to a > file for offline analysis. QEMU could fly along at > about 10MIPS and the disk would soon fill up with large protobuf files. The > offline analysis runs at about

Re: QEMU plugin past, present and future examples

Hi Robert, On 11/6/24 18:53, Robert Henry wrote: QEMU plugin experts: A few years I wrote a plugin for QEMU that saves the instruction stream to a file for offline analysis.  QEMU could fly along at about 10MIPS and the disk would soon fill up with large protobuf files.  The offline

Re: target/i386: fix pushed value of EFLAGS.RF

On 2024-06-11 00:44, Paolo Bonzini wrote: On Tue, Jun 11, 2024 at 12:39 AM Robert Henry wrote: Paolo: Regarding your commit to QEMU https://github.com/qemu/qemu/commit/69cb498c56263a5ae484fd4fef920d3d3eea04c8 Four years ago I reported a bug

QEMU plugin past, present and future examples

QEMU plugin experts: A few years I wrote a plugin for QEMU that saves the instruction stream to a file for offline analysis. QEMU could fly along at about 10MIPS and the disk would soon fill up with large protobuf files. The offline analysis runs at about 50kIPS, and does a variety of

Re: target/i386: fix pushed value of EFLAGS.RF

On Tue, Jun 11, 2024 at 12:39 AM Robert Henry wrote: > > > Paolo: > > Regarding your commit to QEMU > https://github.com/qemu/qemu/commit/69cb498c56263a5ae484fd4fef920d3d3eea04c8 > > Four years ago I reported a bug > https://gitlab.com/qemu-project/qemu/-/issues/249 and as part of cleaning up

target/i386: fix pushed value of EFLAGS.RF

Paolo: Regarding your commit to QEMU https://github.com/qemu/qemu/commit/69cb498c56263a5ae484fd4fef920d3d3eea04c8 Four years ago I reported a bug https://gitlab.com/qemu-project/qemu/-/issues/249 and as part of cleaning up prior to retirement, I want to get my patch published. However, after 5

PEBS sampling from inside a qemu-kvm guest

Hello to all, I am using qemu with kvm enabled on a Saphire Rapid server. I would like to use Intel's PEBS sampling from within the guest. I am under the impression that since Linux kernel 6.3 there is some kvm support for PEBS counter virtualization, and if I grep the word "pebs" in the qemu

Emulating ast2600

Hi all! I tried to emulate BMC firmware for SYS-110P-WTR (Here is a link to download the bundle ). Does QEMU 9.0.0. support this version, or it's too fresh (BMC has been updated on march 23d)? I hope that I

How to stop QEMU punching holes in backing store

Hi. I'm using QEMU emulator version 5.2.0 on Linux. I am using thick-provisioned RAW files as the VM backing store. I've found that QEMU is punching holes in my RAW files (it's replacing some zero blocks with holes), which means that the number of blocks allocated to the VM volumes decreases. It

Re: Query related with Emulation on QEMU

[Resending my reply from the right address...] No, No, Yes Sadly, there seems to still be no IA64 CPU emulation in Qemu (even the ability to run QEMU on actual IA64 hardware has been removed) or anywhere else, forcing all but the richest companies to not develop IA64 software while the

Re: Query related with Emulation on QEMU

Hi QEMU team, Gentle Reminder!!! Can you please assist in clarifying the below queries in the email? I have a query on QEMU emulation capabilities. I have a system with RHEL 8/CENTOS 8 installed with QEMU. Can I emulate any of below hardware platform on top of RHEL 8  or CENTOS 8 using QEMU?

How to set MMC number in QEMU raspi4b

I have a task related to u-boot and have to simulate raspberry pi 4 when I am working remotely. I got the image here (the rasberrypi4-64 one). Because the QEMU uses mmc 1 but the image has some hardcoded mmcblk0 and real devices use mmc 0 also then

Re: Query related with Emulation on QEMU

No, No, Yes Sadly, there seems to still be no IA64 CPU emulation in Qemu (even the ability to run QEMU on actual IA64 hardware has been removed) or anywhere else, forcing all but the richest companies to not develop IA64 software while the architecture existed. For SunOS, look at the

Query related with Emulation on QEMU

Hi QEMU team, I have a query on QEMU emulation capabilities. I have a system with RHEL 8/CENTOS 8 installed with QEMU. Can I emulate any of below hardware platform on top of RHEL 8  or CENTOS 8 using QEMU? 1)  HP-UX 11.23 ia64 2)  HP-UX 11.31 ia 64  3) SunOS 5.10 If yes, Can you give me some

Question on using DMA Engine API with QEMU/KVM

[Public] Hi, I have some questions on emulating a DMA hardware with QEMU. I want to test some kernel code I wrote with core DMA Engine API (https://www.kernel.org/doc/Documentation/DMA-API-HOWTO.txt) I'm getting an error while requesting the DMA channel. Also, I don't see any listed with

Re: Ubuntu Linux broken after installation of QEMU 9.0.0 (latest version)

Hi there, On Sat, 25 May 2024, novaTopFlex wrote: I have installed QEMU 9.0.0 and have effectively attempted to remove my native QEMU 6.2.0 installation by pushing the 9.0.0 commands into the “/usr/bin/“ directory. Mr. Garcia gives good advice but I think this is off-topic for QEMU.

Re: Ubuntu Linux broken after installation of QEMU 9.0.0 (latest version)

Newest supported Qemu packages by Ubuntu GNU/Linux is 8.2.2 version: https://packages.ubuntu.com/noble/qemu-system I recommend you to use Stable only versions of operating system distributions, and its packages platform exclusively. I suggest for this case to uninstall the "push" you manually

Ubuntu Linux broken after installation of QEMU 9.0.0 (latest version)

I have installed QEMU 9.0.0 and have effectively attempted to remove my native QEMU 6.2.0 installation by pushing the 9.0.0 commands into the “/usr/bin/“ directory. I can no longer access various elements of my Ubuntu Linux (22.04.1 LTS system formerly with native QEMU 6.2) system, and some of

Is it possible? Qemu PPC GPU Passthrough using VFIO with Pegasos II machine (Amiga OS 4.1FE installed).

Hello there, I would like to ask if I can passthrough my secondary (real) GPU Radeon RX550 to qemu-system-ppc with Pegasos II installation using Zoltan Balaton's Bboot for Amiga OS4.1. It currently works with -device sm501. But instead, this is what I tried for the VFIO passthrough (not

Re: QEMU on Windows

> On 22 May 2024, at 00:10, ItSeems wrote: > > Can you please tell me which version of Qemu works on Windows 10? For example: - https://github.com/xpack-dev-tools/qemu-arm-xpack/ - https://github.com/xpack-dev-tools/qemu-riscv-xpack/ Regards, Liviu

QEMU on Windows

Can you please tell me which version of Qemu works on Windows 10? I tried a bunch of different versions and all of them have trouble writing into some files. During installation I get an error message like this: "error writing to file edk2-arm-vars.fd".

hot-plug memory in aarch64 virt-9.0

Hello, I'm trying to use the memory hotplug feature, but it fails for qemu 9.0 with a virt-9.0 machine: $ qemu-system-aarch64 -M virt-9.0 -nographic -serial null -m 1G,slots=2,maxmem=2G -object memory-backend-file,size=1G,id=mem0,mem-path=./test_ram -device pc-dimm,memdev=mem0,id=dimm0 QEMU

Re: shared memory mechanism other than ivshmem

Hi Sanjeev, On 5/17/24 3:02 PM, Sanjeev Kumar wrote: Hi Gustavo, I understood difference between the two patchsets. thanks for the ivshmem-flat. i will try to get info from QNX side how to access the memory location in QNX. with the ivshmem-flat enabled, i am able to see shmem in "info qtree"

Re: shared memory mechanism other than ivshmem

Hi Gustavo, I understood difference between the two patchsets. thanks for the ivshmem-flat. i will try to get info from QNX side how to access the memory location in QNX. with the ivshmem-flat enabled, i am able to see shmem in "info qtree" as below (qemu) info qtree bus: main-system-bus type

Re: shared memory mechanism other than ivshmem

Hi Gustavo, Thanks for your reply. Will try it out. But i see two set of patches. https://lore.kernel.org/qemu-devel/2024022218.2261956-1-gustavo.rom...@linaro.org/ And https://lore.kernel.org/qemu-devel/20231127052024.435743-2-gustavo.rom...@linaro.org/ First one looks latest. But when i

Re: shared memory mechanism other than ivshmem

Hi Sanjeev, On 5/16/24 11:22 AM, Sanjeev Kumar wrote: Hi Philippe, I have taken patches from the link you provided and built QEMU and started appending below line to QEMU -chardev socket,path=/tmp/ivshmem_socket,id=ivshmem_flat -device

Re: shared memory mechanism other than ivshmem

and there is this missing part in patches in https://lore.kernel.org/qemu-devel/2024022218.2261956-1-gustavo.rom...@linaro.org/ missing property for ivshmem-flat "x-bus-qompath" which is present in https://lore.kernel.org/qemu-devel/20231127052024.435743-2-gustavo.rom...@linaro.org/ patches.

Re: shared memory mechanism other than ivshmem

Hi Philippe, I have taken patches from the link you provided and built QEMU and started appending below line to QEMU -chardev socket,path=/tmp/ivshmem_socket,id=ivshmem_flat -device

Re: shared memory mechanism other than ivshmem

On 14/5/24 12:23, Sanjeev Kumar wrote: and forgot to mention. why our VM doesn't support ivshmem because it doesn't have PCI supported. Is there any other shared memory mechanism QEMU which doesn't use the PCI interface? On Tue, May 14, 2024 at 11:28 AM Sanjeev Kumar

Re: shared memory mechanism other than ivshmem

and forgot to mention. why our VM doesn't support ivshmem because it doesn't have PCI supported. Is there any other shared memory mechanism QEMU which doesn't use the PCI interface? On Tue, May 14, 2024 at 11:28 AM Sanjeev Kumar wrote: > Hi, > is there any other mechanism of shared memory with

Ignoring arm mis-aligned memory access / bus error 7

Hi, I'm trying to use Qemu to assist with a cross-compiler environment. The underlying is using gentoo and musl as the basic toolchain. Very quick version is that I have a arm 32bit chroot running on a powerful AMD Zen2 processor machine, and I'm using user mode emulation to run the binaries.

shared memory mechanism other than ivshmem

Hi, is there any other mechanism of shared memory with QEMU other than ivshmem? I tried ivshmem with ubuntu vm with qemu x86_64 and it is working fine. but our use case is with ARM and ivshmem isn't supported by our custom VM. so please let me know if we have any other mechanism other than

Re: GPU passthrough

solved by #VFIO -device pcie-root-port,bus=pcie.0,id=pci_root,multifunction=true,addr=0x2 -device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' -device

GPU passthrough

Hello! I'm trying to passthrough gpu to windows vm When using virt-manager it works fine but when i try to run with -device pcie-root-port,bus=pcie.0,slot=1,x-speed=16,x-width=32 -device vfio-pci,host="06:00.0",multifunction=on,bus=pcie.0,rombar=1 -device

Application

Can't find the app

Re: base format

Le jeu. 25 avr. 2024 à 15:13, Jakob Bohm via a écrit : > On 2024-04-25 14:51, lacsaP Patatetom wrote: > > Le jeu. 25 avr. 2024 à 11:30, Peter Maydell > > a écrit : > > > > On Thu, 25 Apr 2024 at 09:55, lacsaP Patatetom > > mailto:patate...@gmail.com>>

Re: base format

On 2024-04-25 14:51, lacsaP Patatetom wrote: Le jeu. 25 avr. 2024 à 11:30, Peter Maydell > a écrit : On Thu, 25 Apr 2024 at 09:55, lacsaP Patatetom mailto:patate...@gmail.com>> wrote: > > hi, > > when using `qemu-img create`, why do I

Re: base format

On Thu, Apr 25, 2024 at 02:51:28PM +0200, lacsaP Patatetom wrote: > > > when using `qemu-img create`, why do I have to specify the > > > format of the base image ? can't `qemu-img` detect it itself ? > > > > Image format detection isn't 100% reliable. Notably, a 'raw' > > format image could in

Re: base format

Le jeu. 25 avr. 2024 à 11:30, Peter Maydell a écrit : > On Thu, 25 Apr 2024 at 09:55, lacsaP Patatetom > wrote: > > > > hi, > > > > when using `qemu-img create`, why do I have to specify the format of the > base image ? > > can't `qemu-img` detect it itself ? > > Image format detection isn't

Re: base format

On Thu, 25 Apr 2024 at 09:55, lacsaP Patatetom wrote: > > hi, > > when using `qemu-img create`, why do I have to specify the format of the base > image ? > can't `qemu-img` detect it itself ? Image format detection isn't 100% reliable. Notably, a 'raw' format image could in theory look like any

base format

hi, when using `qemu-img create`, why do I have to specify the format of the base image ? can't `qemu-img` detect it itself ? I understand that I have to specify the format of the created image, but I don't understand for the base image. `qemu-img create -b base.img -f qcow2 new.img` rather than

Re: Qemu for TC377

Hi Bastian, Thanks a lot. I have downloaded HighTec IDE from ( https://free-entry-toolchain.hightec-rt.com/) and tried to run the TSIM but no success. In web, I don't see any documentation how to run it. The doc comes along with tsim doesn't explain how to start the simulator. Could you let me

qcow2 conversion error

Hey! It's Ahad. Recently I've faced with an issue. I got a SAN storage. If I want to convert my disk image (qcow2) to a qcow2 one, I would get mismatch while comparing the converted and the base Image. The point is that this issue only happens in the SAN to SAN conversion. Converting from SAN to

Generating a new interrupt in TCG (aarch64)

Hello, I am doing a concurrency research of OS guests in full system emulation under QEMU, namely for AArch64 target. For my activities, I would like to force yielding of el0 application. If the guest is Linux, it is a call to sched_yield syscall (#124). For some reason, I don't want to

Re: Qemu for TC377

Hi Sameer, On Tue, Apr 16, 2024 at 02:26:10PM -0400, Sameer Kalliadan Poyil wrote: > Hi Bastian, > > Thanks for the information. I thought that I can do some prototyping before > the > HW arrives. :) > >  Yes I am interested for your bare metal program boot_to_main run it on TSIM.  >   > Is

Could not refresh total sector count: Resource temporarily unavailable

Hello, Got QEMU on my ubuntu server. Also have Xming installed on my windows pc. I star my VM's this way: 1. From windows, open Xming 2.From windows open a putty session and connect to ubuntu 3. From putty session run $virt-manger 4. Then on my windows PC virt-manager UI shows up an then I can

Query VM Clock Time with high precision

Hi All! I'm trying to query the VM Clock Time while in a paused state. The only way I've found to do this is to save a snapshot and use QMP's "query-block" command which contains "vm-clock-sec" and "vm-clock-nsec" fields for each snapshot. Is there any way to get this information without having

virtio-net can't work with event_idx=off

Hi, When tried to run iperf3 between guest and host, virtio-net can work correctly after a while if disable event_idx by "event_idx=off". It's on a Intel x86 platform. The host/guest kernel doesn't matter as I hit the issue with kernels form different distributions/built-by-my-self. The issue

Re: Qemu for TC377

Hi Bastian, Thanks for the information. I thought that I can do some prototyping before the HW arrives. :) Yes I am interested for your bare metal program boot_to_main run it on TSIM. Is Infineon TSIM free? I searched it and I didn't find any download link. Could you please give a link for that

Re: Qemu for TC377

Hi Sameer, On Sun, Apr 14, 2024 at 06:15:56PM +0200, Philippe Mathieu-Daudé wrote: > Hi Sameer, > > On 13/4/24 14:52, Sameer Kalliadan Poyil wrote: > > Hello All, > > I see that Latest qemu supports for tricore TC277 and TC377 > > image.png > > But when I downloaded source code and checked for

Re: Qemu for TC377

Hi Sameer, On 13/4/24 14:52, Sameer Kalliadan Poyil wrote: Hello All, I see that Latest qemu supports for tricore TC277 and TC377 image.png But when I downloaded source code and checked for TC377 related file , I didn't find anything I want to run RTOS/bare metal code on TC377 . could you

Qemu for TC377

Hello All, I see that Latest qemu supports for tricore TC277 and TC377 [image: image.png] But when I downloaded source code and checked for TC377 related file , I didn't find anything I want to run RTOS/bare metal code on TC377 . could you please let me know how to start qemu on TC377 ? Here is

kernel boot message not seen in -nographic mode

Hi, I would like to see all the kernel boot messages in -nographic mode so that I can scroll back and copy/paste them (not possible with SDL/GTK mode). I would also be happy if I can scroll back in the SDL / GTK window, TBH. I do see the output in GTK window when running: 'qemu-system-i386

QEMU Emulation of a PCIe Non-Transparent Bridge

Hi All I'm looking at if I can use QEMU to emulate a PCIe Non-Transparent Bridge (NTB) for some research I am doing. Does anyone out there have any experience of this or heard lore of others doing it? Any pointers at QEMU invocations that might work for this would be appreciated. Cheers

Questions regarding qemu-system <> QMP commands compatibility around disk attachment and AIO information

Hi, I am working with a team that uses QEMU quite a lot. We want to attach devices via QMP `blockdev-add` with `aio:native` option. Is there any way to validate the AIO option set for the drive? `query-block` command doesn’t return anything relevant as far as we can tell. Couldn’t find anything

Send packet from qemu nic to host

Hi all, I have implemented a basic nic model in qemu with a custom machine. I am able to receive packets inside qemu from host using "echo "Hello from host" | nc -q 0 localhost 12345" qemu command: ./qemu-system-aarch64 -machine my_machine,secure=on,enable-nw=on,netdev=net0 -cpu cortex-a55 -m 1024

qemu device_add helper

hi, when I want to offer a smartphone to my virtual machine, I have to attach it as "device_add usb-host,hostbus=X,hostport=Y,id=Z" otherwise, I lose the attachment on the virtual machine side when I switch the smartphone mode (MTP, USB connection sharing, etc...). to avoid having to manually

Re: Fast booting q35 VM?

Cc'ing qemu-devel@ On 30/3/24 10:00, Paul Menzel wrote: Dear Linux folks, Starting a QEMU q35 with Linux built with `make defconfig`     qemu7-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32 -device virtio-rng-pci -net nic,model=virtio-net-pci -net

Re: armv7-m: tlb_set_page_full: Assertion failed

Hi Peter, I actually found the problem but I didn't know how to reply to the thread as I sent my email before being subscribed to the mailing list. Anyway, you are right, the issue was that my base address wasn't aligned on 4k. I said on my previous that base address was 0x0021E000 when in

Re: armv7-m: tlb_set_page_full: Assertion failed

On Fri, 29 Mar 2024 at 12:47, Raphaël Poggi wrote: > > Hi, > > I am currently working on adding support of a custom ASIC based on > ARMv7-M (Cortex-M3). > > I have a RAM region defined as followed: > > base address = 0x0021E000 > size = 0x1FFC > > For some reason, during memcpy performed on guest

low io performance after loadvm.

Hi team, I’m testing a libvirt feature in Ubuntu. And I found the IO perf is low after I revert a snapshot. Then I try to start a VM by qemu-system-x86_64, add a blkiotune to restrict the iops , savevm then loadvm. Get the same result (low IO performance). My qemu start cmd:

armv7-m: tlb_set_page_full: Assertion failed

Hi, I am currently working on adding support of a custom ASIC based on ARMv7-M (Cortex-M3). I have a RAM region defined as followed: base address = 0x0021E000 size = 0x1FFC For some reason, during memcpy performed on guest side, I have an assertion failed: qemu-system-arm:

qemu process consumes 100% host CPU after reverting snapshot

Hi, I am testing throttle filter chain(multiple throttle-groups on disk) with the following steps: 1. start guest vm(chained throttle filters applied on disk per https://github.com/qemu/qemu/blob/master/docs/throttle.txt) 2. take snapshot 3. revert snapshot after step3, I noticed qemu

Re: Technical support

On 24/03/2024 19.45, Luca Vajen wrote: Hello, I'm not sure if this is the right place to ask for help. I guess in the worst case you might get a laugh out of this. There's an old game I would like to play again and someone made a ready-to-play version using QEMU. See the corresponding link

Re: Technical support

On 3/25/24 09:19, Pierrick Bouvier wrote: On 3/24/24 22:45, Luca Vajen wrote: Hello, I'm not sure if this is the right place to ask for help. I guess in the worst case you might get a laugh out of this. There's an old game I would like to play again and someone made a ready-to-play version

Re: Technical support

On 3/24/24 22:45, Luca Vajen wrote: Hello, I'm not sure if this is the right place to ask for help. I guess in the worst case you might get a laugh out of this. There's an old game I would like to play again and someone made a ready-to-play version using QEMU. See the corresponding link on 

Technical support

Hello,   I'm not sure if this is the right place to ask for help. I guess in the worst case you might get a laugh out of this. There's an old game I would like to play again and someone made a ready-to-play version using QEMU. See the corresponding link on 

Re: VLAN bridge without ip address

Am 15.03.24 um 22:11 schrieb stefanx: > Hello, > > I have a fairly simple question: I need an netplan example configuration for > a VLAN bridge without ip address for using kvm/qemu/libvirt (Ubuntu 22.04). I > can't find anything about it. > > Thanks > > Stefan Hello, can't anyone help me ?  

PCI hot plug to a VM does not work in Alma

Hi We have a chassis with a peripheral PCI device installed. We have a hypervisor running on the chassis where we have deployed a VM which can use the PCI device once it is attached. When the PCI device is powered on or off we need to do a hotplug in/out using virsh commands. Even though the

Re: No 'PCI' bus found for device 'ivshmem-plain'

On Thu, 21 Mar 2024 at 08:16, Sanjeev Kumar wrote: > > Hi, > our kernel is build with aarch64le. it is 64 bit ARM architecture. Such a kernel cannot possibly boot on the vexpress-a15 machine that you say you are using. So something doesn't seem right... > when i am trying to use virt as

Re: No 'PCI' bus found for device 'ivshmem-plain'

as we are beginners. can you please guide us on using virt cpu please. On Thu, Mar 21, 2024 at 1:52 PM Sanjeev Kumar wrote: > cpu we are using cortex-a57 because it is nearby to our actual hardware > exynos v9 > > On Thu, Mar 21, 2024 at 1:46 PM Sanjeev Kumar > wrote: > >> Hi, >> our kernel is

Re: No 'PCI' bus found for device 'ivshmem-plain'

cpu we are using cortex-a57 because it is nearby to our actual hardware exynos v9 On Thu, Mar 21, 2024 at 1:46 PM Sanjeev Kumar wrote: > Hi, > our kernel is build with aarch64le. it is 64 bit ARM architecture. > when i am trying to use virt as machine, then qemu isn't starting. it is > being

Re: No 'PCI' bus found for device 'ivshmem-plain'

Hi, our kernel is build with aarch64le. it is 64 bit ARM architecture. when i am trying to use virt as machine, then qemu isn't starting. it is being stuck after entering command, On Wed, Mar 20, 2024 at 7:06 PM Peter Maydell wrote: > On Wed, 20 Mar 2024 at 13:06, Sanjeev Kumar > wrote: > > >

Re: No 'PCI' bus found for device 'ivshmem-plain'

On Wed, 20 Mar 2024 at 13:06, Sanjeev Kumar wrote: > > Hi Peter, > Thanks for your detailed review. > ifs.bin is our custom build and the linux kernel is booting fine with this > file. If it is, then it must be a 32-bit kernel. So trying to run it on the cortex-a57 will not work at all, because

Re: No 'PCI' bus found for device 'ivshmem-plain'

Hi Peter, Thanks for your detailed review. ifs.bin is our custom build and the linux kernel is booting fine with this file. "this board doesn't have a PCI bus" - can you please suggest some board which can support PCI bus? if possible can you please reframe the command line which i shared with you

Re: No 'PCI' bus found for device 'ivshmem-plain'

On Wed, 20 Mar 2024 at 06:40, Sanjeev Kumar wrote: > > Hi, > Sorry for incomplete command. > here is the complete command line. > > qemu-system-aarch64 -machine vexpress-a15 -cpu cortex-a57 -smp 4 -m 10G > -kernel ifs.bin -drive file=disk-qemu.vmdk,if=none,id=drv0 -device >

Re: No 'PCI' bus found for device 'ivshmem-plain'

Hi, Sorry for incomplete command. here is the complete command line. qemu-system-aarch64 -machine vexpress-a15 -cpu cortex-a57 -smp 4 -m 10G -kernel ifs.bin -drive file=disk-qemu.vmdk,if=none,id=drv0 -device virtio-blk-device,drive=drv0 -netdev tap,id=mynet0,ifname=tap0,script=no,downscript=no

Re: No 'PCI' bus found for device 'ivshmem-plain'

On Tue, 19 Mar 2024 at 09:41, Sanjeev Kumar wrote: > > Hi, > I am starting QEMU as below. > qemu-system-aarch64 [] -device ivshmem-plain,memdev=hostmem -object > memory-backend-file,size=1M,share=on,mem-path=/dev/shm/ivshmem,id=hostmem Please give us the *full* command line, not the

No 'PCI' bus found for device 'ivshmem-plain'

Hi, I am starting QEMU as below. qemu-system-aarch64 [] -device ivshmem-plain,memdev=hostmem -object memory-backend-file,size=1M,share=on,mem-path=/dev/shm/ivshmem,id=hostmem before this, i am starting ivshmem-server which i build from QEMU source git repo. i am able to see ivshmem device

VLAN bridge without ip address

Hello, I have a fairly simple question: I need an netplan example configuration for a VLAN bridge without ip address for using kvm/qemu/libvirt (Ubuntu 22.04). I can't find anything about it. Thanks Stefan

Re: QEMU Compatibility for Cortex-A55 AArch32 Firmware

On Thu, 7 Mar 2024 at 01:03, yb liu wrote: > > Thanks a lot for you respond me soon! > The exact instruction is mrc, and the exception happended in early boot > process. I have no idea to how to debug this error because it happended in > code_gen_prologue. That's a system register access. If

Re: QEMU Compatibility for Cortex-A55 AArch32 Firmware

Thanks a lot for you respond me soon! The exact instruction is mrc, and the exception happended in early boot process. I have no idea to how to debug this error because it happended in code_gen_prologue. I need to comform that whether QEMU A55 fully supports aarch32 mode. If it need me to add

Re: QEMU Compatibility for Cortex-A55 AArch32 Firmware

On Wed, 6 Mar 2024 at 14:33, yb liu wrote: > > > Dear QEMU developers > > I hope this email finds you well. We are currently facing an issue related to > QEMU and the Cortex-A55 architecture. Specifically, we have compiled a > firmware for Cortex-A55 and would like it to run smoothly on QEMU

QEMU Compatibility for Cortex-A55 AArch32 Firmware

Dear QEMU developers I hope this email finds you well. We are currently facing an issue related to QEMU and the Cortex-A55 architecture. Specifically, we have compiled a firmware for Cortex-A55 and would like it to run smoothly on QEMU A55 in AArch32 mode. Despite our numerous attempts, we

RE: Xilinx zcu102 machine is absent in list of supported machines

Hi, Thank you very much - the problem solved. Best regards Vadim Idelchuk vadim.idelc...@mail.ru -Original Message- From: qemu-discuss-bounces+vadim.idelchuk=mail...@nongnu.org [mailto:qemu-discuss-bounces+vadim.idelchuk=mail...@nongnu.org] On Behalf Of Peter Maydell Sent: Tuesday,

Re: Xilinx zcu102 machine is absent in list of supported machines

On Tue, 5 Mar 2024 at 18:31, Vadim Idelchuk via wrote: > The additional information about my build: Thanks for that. Yeah, you're missing only this machine type. I had a poke around in the config files, and I think this is because the machine has a dependency on pixman, so if configure doesn't

RE: Xilinx zcu102 machine is absent in list of supported machines

Hi, The additional information about my build: - qemu build cmd: mkdir build cd build ../configure make - git status: On branch master Your branch is up to date with 'origin/master'. nothing to commit, working tree clean - version:

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

Thanks Jim! > On Mar 4, 2024, at 10:10 PM, Jim Mattson wrote: > > !---| > This Message Is From an External Sender > > |---! > > On Mon, Mar 4, 2024 at 6:11 PM Xu

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

On Mon, Mar 4, 2024 at 6:11 PM Xu Liu wrote: > > Hey Alex and Paolo, > > I saw there is some code related to AVX > https://elixir.bootlin.com/linux/latest/source/arch/x86/kvm/emulate.c#L668 > > Does that mean in some special cases, kvm supports AVX instructions ? > I didn’t really know the big

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

Hey Alex and Paolo, I saw there is some code related to AVX https://elixir.bootlin.com/linux/latest/source/arch/x86/kvm/emulate.c#L668 Does that mean in some special cases, kvm supports AVX instructions ? I didn’t really know the big picture, so just guess what it is doing . Thanks, Xu > On

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

Hey Paolo, Thanks for confirming that the AVX is not supported for MMIO space. So for the emulated device, basically I have to force the compiler avoid using vmovdqu . I am curious about how kvm emulates those instructions. Do you mind sharing some related code pointer ? Thanks, Xu On Mar

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

Hey Alex, Thanks for the detailed explanation! First answer your question: Is your "program" just doing a memcpy() with an mmap() of the PCI BAR acquired through pci-sysfs or a userspace vfio-pci driver within the guest? My program is using a usersapcee vfio-pci driver for both emulated device

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

Hey Alex, Thanks for the detailed explanation! First answer your question: Is your "program" just doing a memcpy() with an mmap() of the PCI BAR acquired through pci-sysfs or a userspace vfio-pci driver within the guest? My program is using a usersapcee vfio-pci driver for both emulated device

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

On 3/4/24 22:59, Alex Williamson wrote: Since you're not seeing a KVM_EXIT_MMIO I'd guess this is more of a KVM issue than QEMU (Cc kvm list). Possibly KVM doesn't emulate vmovdqu relative to an MMIO access, but honestly I'm not positive that AVX instructions are meant to work on MMIO space.

Usb passthrough for windows host

Hi Everyone, I tried to have usb cam working, however even if the console report it with info usb. Linux quest don't seem to see the web cam Any clues? Command Line: qemu-system-x86_64 -vga qxl -M q35 -device AC97 -smp 2,sockets=2,cores=1,threads=1 -hda .\file\Linux.img -m 2G -usb -device

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

On Sun, 3 Mar 2024 22:20:33 + Xu Liu wrote: > Hello, > > Recently I am running my programs in QEMU (x86_64) with “-accel=kvm”. > The QEMU version is 6.0.0. > > I run my programs in two ways: > > 1. I pass through my device through vfio-pci to QEMU, this way > works well. > > 2. I

Re: Xilinx zcu102 machine is absent in list of supported machines

On Mon, 4 Mar 2024 at 11:20, Vadim Idelchuk via wrote: > For building the products I run the following: > > ./configure > > make > > > > I tried these sequence number of times with the same result - machine type > xlnx-zcu102 is absent in the list of supported machines What is the exact command

RE: Xilinx zcu102 machine is absent in list of supported machines

For building the products I run the following: ./configure make I tried these sequence number of times with the same result - machine type xlnx-zcu102 is absent in the list of supported machines Best regards Vadim Idelchuk vadim.idelc...@mail.ru -- This email has

Emulating multicore processor on QEMU in a bare metal environment

Hello, As suggested, QEMU supports few dual core machines. So, I want to emulate mps2-an521 Or mps3-an24 on QEMU, and implement inter core communication and synchronization. The application is developed in bare metal ARM environment. What are the approaches to do this? I have a basic knowledge

  1   2   3   4   5   6   7   8   9   10   >