[Top][All Lists]

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

Re: [Qemu-discuss] Memory host - guest sharing

From: Sławomir Kowalewski
Subject: Re: [Qemu-discuss] Memory host - guest sharing
Date: Wed, 10 Sep 2014 15:19:03 +0200


IVSHMEM will not work because lack of PCI in this case so I must use SYSBUS.

The plan is to create device in /dev and map host RAM memory to it (that contain important data) then pass device to guest so I could read from it.

For now I create simple char device and have problem pass it to guest system.

Should --device parameter work in this case?
Do you have any SysBusDevice - tutorials or examples?
Do I need some Qemu driver, host kernel driver or it should just appear?
Maybe better use here virsh (libvirt)?

Sławomir Kowalewski

2014-09-05 15:44 GMT+02:00 Sławomir Kowalewski <address@hidden>:

does somebody use IVSHMEM on arm host/guest?

Sławomir Kowalewski

2014-09-03 12:06 GMT+02:00 Sławomir Kowalewski <address@hidden>:

this is one of possible solution but we can't use pci but sysbus instead.
So there will be need to rewrite IVSHMEM.

Sławomir Kowalewski

2014-09-03 11:47 GMT+02:00 Tetsuya.Mukawa <address@hidden>:

Hi Sławomir,

If you are using linux, how about using IVSHMEM?
You may be able to get physical memory from hugetlbfs on host, then
export it as pci memory to a guest.
Then, mmap it from user application of the guest.


(2014/09/03 18:19), Sławomir Kowalewski wrote:
> Hi,
> I have application on host system that using part of RAM to create
> some kind of tables. I need to give access to this memory to
> application that is running on guest system.
> What is the easiest way to do it?
> I came up with two ideas.
> 1. Write driver for Qemu and kernel that will use sysbus to get
> addresses from host and map memory into file on guest.
> 2. Map part of memory into file on host and then use libvirt XML
> configuration file to pass created file into guest system.
> Do you have better ideas or know why one of mine will not work?
> Best Regards
> Sławomir Kowalewski

reply via email to

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