similar to: Xen Inter VM Fast Communication HVM

Henning Schild <henning.schild at siemens.com> writes: > Hi, > > i am working on the jailhouse[1] project and am currently looking at > inter-VM communication. We want to connect guests directly with virtual > consoles based on shared memory. The code complexity in the hypervisor > should be minimal, it should just make the shared memory discoverable > and provide a

Hi: I have two HVM domU ubuntu 10.04 Lts and Window XP running. I have assigned PCIe device to each of this domU. I would like to communicate these two VM. Can anyone give me some idea on how to do. I did some research on IVC but unable to get answer. Anything will be appreciated. Anju _______________________________________________ Xen-users mailing list

Hi, i am working on the jailhouse[1] project and am currently looking at inter-VM communication. We want to connect guests directly with virtual consoles based on shared memory. The code complexity in the hypervisor should be minimal, it should just make the shared memory discoverable and provide a signaling mechanism. We would like to reuse virtio so that Linux-guests will eventually just work

Hi, i am working on the jailhouse[1] project and am currently looking at inter-VM communication. We want to connect guests directly with virtual consoles based on shared memory. The code complexity in the hypervisor should be minimal, it should just make the shared memory discoverable and provide a signaling mechanism. We would like to reuse virtio so that Linux-guests will eventually just work

On 2014-06-12 04:27, Rusty Russell wrote: > Henning Schild <henning.schild at siemens.com> writes: >> Hi, >> >> i am working on the jailhouse[1] project and am currently looking at >> inter-VM communication. We want to connect guests directly with virtual >> consoles based on shared memory. The code complexity in the hypervisor >> should be minimal, it

On 2014-06-12 04:27, Rusty Russell wrote: > Henning Schild <henning.schild at siemens.com> writes: >> Hi, >> >> i am working on the jailhouse[1] project and am currently looking at >> inter-VM communication. We want to connect guests directly with virtual >> consoles based on shared memory. The code complexity in the hypervisor >> should be minimal, it

On 10/06/2014 18:48, Henning Schild wrote:> Hi, > In a first prototype i implemented a ivshmem[2] device for the > hypervisor. That way we can share memory between virtual machines. > Ivshmem is nice and simple but does not seem to be used anymore. > And it > does not define higher level devices, like a console. FYI, ivhsmem is used here:

On Thu, 12 Jun 2014 08:48:04 +0200 Markus Armbruster <armbru at redhat.com> wrote: > Vincent JARDIN <vincent.jardin at 6wind.com> writes: > > > On 10/06/2014 18:48, Henning Schild wrote:> Hi, > >> In a first prototype i implemented a ivshmem[2] device for the > >> hypervisor. That way we can share memory between virtual machines. > >> Ivshmem

Jan Kiszka <jan.kiszka at siemens.com> writes: > On 2014-06-12 04:27, Rusty Russell wrote: >> Henning Schild <henning.schild at siemens.com> writes: >> It was also never implemented, and remains a thought experiment. >> However, implementing it in lguest should be fairly easy. > > The reason why a trusted helper, i.e. additional logic in the > hypervisor,

Il 13/06/2014 08:23, Jan Kiszka ha scritto: >>> That would preserve zero-copy capabilities (as long as you can work >>> against the shared mem directly, e.g. doing DMA from a physical NIC or >>> storage device into it) and keep the hypervisor out of the loop. > > > > This seems ill thought out. How will you program a NIC via the virtio > > protocol

Il 15/06/2014 08:20, Jan Kiszka ha scritto: >> > I think implementing Xen hypercalls in jailhouse for grant table and >> > event channels would actually make a lot of sense. The Xen >> > implementation is 2.5kLOC and I think it should be possible to compact >> > it noticeably, especially if you limit yourself to 64-bit guests. > At least the grant table

On 2014-06-13 10:45, Paolo Bonzini wrote: > Il 13/06/2014 08:23, Jan Kiszka ha scritto: >>>> That would preserve zero-copy capabilities (as long as you can work >>>> against the shared mem directly, e.g. doing DMA from a physical NIC or >>>> storage device into it) and keep the hypervisor out of the loop. >> > >> > This seems ill thought

On 2014-06-13 10:45, Paolo Bonzini wrote: > Il 13/06/2014 08:23, Jan Kiszka ha scritto: >>>> That would preserve zero-copy capabilities (as long as you can work >>>> against the shared mem directly, e.g. doing DMA from a physical NIC or >>>> storage device into it) and keep the hypervisor out of the loop. >> > >> > This seems ill thought

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

On 2014-06-13 02:47, Rusty Russell wrote: > Jan Kiszka <jan.kiszka at siemens.com> writes: >> On 2014-06-12 04:27, Rusty Russell wrote: >>> Henning Schild <henning.schild at siemens.com> writes: >>> It was also never implemented, and remains a thought experiment. >>> However, implementing it in lguest should be fairly easy. >> >> The

On 2014-06-13 02:47, Rusty Russell wrote: > Jan Kiszka <jan.kiszka at siemens.com> writes: >> On 2014-06-12 04:27, Rusty Russell wrote: >>> Henning Schild <henning.schild at siemens.com> writes: >>> It was also never implemented, and remains a thought experiment. >>> However, implementing it in lguest should be fairly easy. >> >> The

Hello, I'm using CentOS 5.5 / 16bit as a virtual machine in VMWare Workstation and have installed the "VMWare Tools" by running vmware-install.pl and vmware-config-tools.pl but can't figure out how to make the VM shutdown, when I shutdown the Windows PC hosting it. Does anybody please have any hints or scripts? Do I need to use any VMWare modules if I just want to shutdown the

Henning Schild <henning.schild at siemens.com> writes: > On Thu, 12 Jun 2014 08:48:04 +0200 > Markus Armbruster <armbru at redhat.com> wrote: > >> Vincent JARDIN <vincent.jardin at 6wind.com> writes: >> >> > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> >> In a first prototype i implemented a ivshmem[2] device for the >>

Henning Schild <henning.schild at siemens.com> writes: > On Thu, 12 Jun 2014 08:48:04 +0200 > Markus Armbruster <armbru at redhat.com> wrote: > >> Vincent JARDIN <vincent.jardin at 6wind.com> writes: >> >> > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> >> In a first prototype i implemented a ivshmem[2] device for the >>