similar to: Obtaining the PID of a domain's QEMU process from C

On Sat, Mar 09, 2019 at 04:32:00PM +0100, Michal Prívozník wrote: > On 3/1/19 2:31 AM, Shawn Anastasio wrote: > > Hello all, > > > > I'm currently writing a C program that uses the libvirt API and I need a > > way to obtain the pid of a given domain's QEMU process. > > > > Specifically, I'm writing an ivshmem server that uses SO_PEERCRED to get

On Mon, Mar 11, 2019 at 09:33:30AM +0100, Michal Privoznik wrote: > On 3/11/19 9:02 AM, Erik Skultety wrote: > > On Sat, Mar 09, 2019 at 04:32:00PM +0100, Michal Prívozník wrote: > > > On 3/1/19 2:31 AM, Shawn Anastasio wrote: > > > > Hello all, > > > > > > > > I'm currently writing a C program that uses the libvirt API and I need a >

Thanks for the response. /var/run/libvirt/qemu/ seems to be exactly what I'm looking for. It would, however, be nice to be able to access this file without root privileges. Is there any way to access the file using the credentials from a connected virConnectPtr? If not, I can stick to my current workaround of walking /proc and scanning each PID's cmdline for the VM's UUID string.

On 3/1/19 2:31 AM, Shawn Anastasio wrote: > Hello all, > > I'm currently writing a C program that uses the libvirt API and I need a > way to obtain the pid of a given domain's QEMU process. > > Specifically, I'm writing an ivshmem server that uses SO_PEERCRED to get > the pid of clients that connect to it, and I would like to use that pid > to look up the

On 3/11/19 9:02 AM, Erik Skultety wrote: > On Sat, Mar 09, 2019 at 04:32:00PM +0100, Michal Prívozník wrote: >> On 3/1/19 2:31 AM, Shawn Anastasio wrote: >>> Hello all, >>> >>> I'm currently writing a C program that uses the libvirt API and I need a >>> way to obtain the pid of a given domain's QEMU process. >>> >>>

On Mon, Mar 11, 2019 at 09:46:11AM +0000, Daniel P. Berrangé wrote: > On Mon, Mar 11, 2019 at 09:33:30AM +0100, Michal Privoznik wrote: > > On 3/11/19 9:02 AM, Erik Skultety wrote: > > > On Sat, Mar 09, 2019 at 04:32:00PM +0100, Michal Prívozník wrote: > > > > On 3/1/19 2:31 AM, Shawn Anastasio wrote: > > > > > Hello all, > > > > > >

On Sat, 9 Mar 2019 at 17:27, Shawn Anastasio <shawn@anastas.io> wrote: > Thanks for the response. /var/run/libvirt/qemu/ seems to be exactly what > I'm looking for. It would, however, be nice to be able to access this > file without root privileges. > Use a tiny setuid C program that reads the relevant file and writes it to a known UNIX-domain socket that has more liberal

On 30. 3. 2020 15:26, john doe wrote: > On 3/30/2020 1:20 PM, Andrea Bolognani wrote: >> On Mon, 2020-03-30 at 12:04 +0200, Michal Prívozník wrote: >>> On 27. 3. 2020 20:49, john doe wrote: >>>> If my understanding is correct, using 'try06' or 'debian' should do the >>>> same thing? >>> >>> Yes, that is the idea. However,

Hi Fellow users I've just compiled latest libvirt and qemu, both from their respective official repositories. Libvirtd starts perfect, but when I try to start a domain using the virsh console, I get the following: virsh # start --domain win8.1 error: Failed to start domain win8.1 error: internal error: Failed to start QEMU binary /usr/bin/qemu-system-x86_64 for probing: qemu-system-x86_64:

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

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

Some dropped quoted text restored. Vincent JARDIN <vincent.jardin at 6wind.com> writes: > 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

Some dropped quoted text restored. Vincent JARDIN <vincent.jardin at 6wind.com> writes: > 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

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 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

Hi list, I'm trying to get some ideas on this subject. Normally astersik sends emails with voicemail attached trough local MTA. As far as i know there is no way for asterisk to authenticate to an external mailserver to relay these emails. Well, these days every provider has some sort of spam blocking, to add to that usually users of asterisk are behid a dynamic IP with no PTR and list grows

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 ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding

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 ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding

Coming late to the party, On 31.08.2015 16:11, Michael S. Tsirkin wrote: > Hello! > During the KVM forum, we discussed supporting virtio on top > of ivshmem. I have considered it, and came up with an alternative > that has several advantages over that - please see below. > Comments welcome. as Jan mentioned we actually discussed a virtio-shmem device which would incorporate the