qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] aarch64 ivshmem issues


From: Peter Maydell
Subject: Re: [Qemu-discuss] aarch64 ivshmem issues
Date: Sun, 10 Jan 2016 23:06:58 +0000

On 10 January 2016 at 13:07, Meng Xu <address@hidden> wrote:
> Hi All,
>
> I am using the ivshmem device to create shared memory between an x86_64 host 
> and aarch64 guest.
> The guest has ubuntu server 14.04 installed with kernel version 3.13.0. I 
> wrote a kernel driver to
> drive the ivshmem device (as a pci driver) however, the driver was never 
> registered:
>
> Can anyone help me point out what is wrong?
>
> My qemu launch script looks like this:
> qemu-system-aarch64 -machine virt,highmem=off -cpu cortex-a57 -m 1024M \
>         -drive file=<path-to-img>,id=hd0,if=none,format=qcow2 \
>         -device virtio-blk-device,drive=hd0 \
>         -device ivshmem,shm=vshmtest,size=16M \
>         -kernel <path-to-kernel> \
>         -initrd <path-to-initrd> \

You're using "highmem=off", which is disabling the
high-address PCI window. That means that PCI devices
which want a large address range for their PCI BARs
won't work. I think that ivshmem is one such device
(and in fact ivshmem is the reason we added the high
window).

Is there a reason why you have this in your command line?

I would expect that if you've built your kernel with
the relevant PCI diagnostic config options enabled,
the kernel should print out as it boots the PCI cards
it sees and what it's doing with them. That ought to
help in trying to diagnose what's happening.

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]