similar to: IVSHMEM support

Hi all, Not sure if this is the best place to put this question since I'm not sure if it's a Libvirt issue but... I currently have two VMs up with networking and I can successfully ssh to and from each VM and I have confirmed that I can successfully download things from the internet. However, when trying to run mpiexec (which uses ssh), the connection fails and gives me the following

Hi all, I am trying to install a version of Libvirt that will be compatible with qemu-kvm-1.1 but I cannot seem to get Libvirt to compile. During the make portion of the install I get the following error: ... make[4]: Entering directory `/home/shawn/libvirt-0.10.0/docs' Generating 404.html.tmp /bin/bash: line 5: 59204 Segmentation fault /usr/bin/xsltproc --stringparam pagename $name

Hi all, I have been using Libvirt for several months now and I have only had minimal problems. I had a particular setup and was starting up multiple guests just fine. However, with seemingly no changes I now get the following error when trying to start a guest: virsh start guest0 error: Failed to start domain guest0 error: internal error Process exited while reading console log output: Supported

Hi all, I am using Ubuntu 10.04 Server and I am trying to figure out which versions of qemu-kvm and libvirt are known to work well together and if there is anything special that needs to be done during their installs. I am trying to work with the latest version of libvirt possible that will be stable with qemu-kvm. Right now, the only configuration I've been able to get working are the

Hi all, For some reason when I run "libvirtd -d" as root it seems to not start. I investigate by running "libvirtd -v" as root and I get a segfault. Here is the output: 2012-08-23 19:01:23.237+0000: 27464: info : libvirt version: 0.10.0 > 2012-08-23 19:01:23.237+0000: 27464: error : virDriverLoadModule:78 : > failed to load module >

Hello, friends. I encounter a problem when i use ivshmem with my guest, my ivshmem server is not start, and output a error : Example code, do not use in production ,cannot bind. Detail distribution: Today, I know ivshmem from a topic "QEMU version 2.10.93 User Documentation", Ivshmem: it can create a shared memory that guest device use, so we can use this memory to do something

> Fine, however Red Hat would also need a way to test ivshmem code, with > proper quality assurance (that also benefits upstream, of course). With > ivshmem this is not possible without the out-of-tree packages. You did not reply to my question: how to get the list of things that are/will be disabled by Redhat? About Redhat's QA, I do not care. About Qemu's QA, I do care ;) I

(+merging with Paolo's email because of overlaps) >> see inline (I am not on all mailing list, please, keep the cc list). >> >>> 1. ivshmem code needs work, but has no maintainer >> See David's contributions: >> http://patchwork.ozlabs.org/patch/358750/ > > We're grateful for David's patch for qemu-char.c, but this isn't ivshmem >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 18.06.2014 12:48, schrieb Stefan Hajnoczi: > On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: >> Il 17/06/2014 11:03, David Marchand ha scritto: >>>> Unless someone steps up and maintains ivshmem, I think it >>>> should be deprecated and dropped from QEMU. >>> >>> Then I can maintain

On Fri, Jun 13, 2014 at 10:10 PM, Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 13/06/2014 15:41, Vincent JARDIN ha scritto: >> I do repeat this use case that you had removed because vhost-user does >> not solve it yet: >> >>>> - ivshmem -> framework to be generic to have shared memory for many >>>> use cases (HPC, in-memory-database, a

Hi, I am using virsh 0.9.8 My qemu is 1.0 version. I would like to use Ivshmem device from virsh command line. It is possible to use ivshmem device from qemu command line.But its not working if I am giving -device ivshmem device in xml config file. Does virsh support ivshmem device.?? -- Mrugani Kurtadikar Btech IT College of Engineering, Pune. -------------- next part -------------- An HTML

Il 13/06/2014 15:41, Vincent JARDIN ha scritto: >> Fine, however Red Hat would also need a way to test ivshmem code, with >> proper quality assurance (that also benefits upstream, of course). With >> ivshmem this is not possible without the out-of-tree packages. > > You did not reply to my question: how to get the list of things that > are/will be disabled by Redhat? I

Il 13/06/2014 15:41, Vincent JARDIN ha scritto: >> Fine, however Red Hat would also need a way to test ivshmem code, with >> proper quality assurance (that also benefits upstream, of course). With >> ivshmem this is not possible without the out-of-tree packages. > > You did not reply to my question: how to get the list of things that > are/will be disabled by Redhat? I

Markus, see inline (I am not on all mailing list, please, keep the cc list). > Sure! The reasons for my dislike range from practical to > philosophical. > > My practical concerns include: > > 1. ivshmem code needs work, but has no maintainer See David's contributions: http://patchwork.ozlabs.org/patch/358750/ > 2. There is no libvirt support One can use qemu

Hi, I am trying to create a VM with the IVSHMEM feature, and I specify the device using qemu command line argument in my XML by using the pass through tag as follows: <qemu:commandline> <qemu:arg value='-device ivshmem,size=2048M,shm=fd:/mnt/huge/map_1:0x0:0x40000000:/dev/zero:0x0:0x3fffc000:/var/run/.ivshmem_metadata_config_2:0x0:0x4000'/>

Il 13/06/2014 11:26, Vincent JARDIN ha scritto: >> Markus especially referred to parts *outside* QEMU: the server, the >> uio driver, etc. These out-of-tree, non-packaged parts of ivshmem >> are one of the reasons why Red Hat has disabled ivshmem in RHEL7. > > You made the right choices, these out-of-tree packages are not required. > You can use QEMU's ivshmem

Il 13/06/2014 11:26, Vincent JARDIN ha scritto: >> Markus especially referred to parts *outside* QEMU: the server, the >> uio driver, etc. These out-of-tree, non-packaged parts of ivshmem >> are one of the reasons why Red Hat has disabled ivshmem in RHEL7. > > You made the right choices, these out-of-tree packages are not required. > You can use QEMU's ivshmem

Il 17/06/2014 11:03, David Marchand ha scritto: >> Unless someone steps up and maintains ivshmem, I think it should be >> deprecated and dropped from QEMU. > > Then I can maintain ivshmem for QEMU. > If this is ok, I will send a patch for MAINTAINERS file. Typically, adding yourself to maintainers is done only after having proved your ability to be a maintainer. :) So,

Hello all, On 06/17/2014 04:54 AM, Stefan Hajnoczi wrote: > ivshmem has a performance disadvantage for guest-to-host > communication. Since the shared memory is exposed as PCI BARs, the > guest has to memcpy into the shared memory. > > vhost-user can access guest memory directly and avoid the copy inside the guest. Actually, you can avoid this memory copy using frameworks like

Hello all, On 06/17/2014 04:54 AM, Stefan Hajnoczi wrote: > ivshmem has a performance disadvantage for guest-to-host > communication. Since the shared memory is exposed as PCI BARs, the > guest has to memcpy into the shared memory. > > vhost-user can access guest memory directly and avoid the copy inside the guest. Actually, you can avoid this memory copy using frameworks like