Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-06 Thread Daniel Henrique Barboza
Hi, After investigating more I've fixed the problem in a way that I believe it's worth a patch. I'll be sending it to the ML shortly. Thanks everyone for the inputs and insights, DHB On 2/4/19 10:59 AM, Yuval Shaia wrote: + Kamal and Marcel On Mon, Feb 04, 2019 at 09:58:47AM +0100, Michal

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-05 Thread Daniel Henrique Barboza
On 2/5/19 8:32 AM, Daniel P. Berrangé wrote: On Mon, Feb 04, 2019 at 08:44:21PM -0200, Daniel Henrique Barboza wrote: I'm still experiencing the issue with IPC_LOCK inside the guest though. I'll update here when I have concrete findings about it. Any use of capabilities "inside the guest"

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-05 Thread Daniel P . Berrangé
On Mon, Feb 04, 2019 at 08:44:21PM -0200, Daniel Henrique Barboza wrote: > Hi Erik, > > Just to let you know that the error I reported in one of my replies was > being caused by one change I forgot to undo. This error here: > > > error : virQEMUCapsNewForBinaryInternal:4687 : internal error:

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-05 Thread Erik Skultety
On Mon, Feb 04, 2019 at 08:44:21PM -0200, Daniel Henrique Barboza wrote: > Hi Erik, > > Just to let you know that the error I reported in one of my replies was > being caused by one change I forgot to undo. This error here: > > > error : virQEMUCapsNewForBinaryInternal:4687 : internal error:

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Daniel Henrique Barboza
Hi Erik, Just to let you know that the error I reported in one of my replies was being caused by one change I forgot to undo. This error here: error : virQEMUCapsNewForBinaryInternal:4687 : internal error: Failed to probe QEMU binary with QMP: libvirt:  error : prctl failed to enable

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Daniel Henrique Barboza
Hey Erik, On 2/4/19 8:11 AM, Erik Skultety wrote: On Fri, Feb 01, 2019 at 07:40:36PM -0200, Daniel Henrique Barboza wrote: Update: I've figured it out. The bug here was that, even running as root, I was getting errors like: error : virQEMUCapsNewForBinaryInternal:4687 : internal error:

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Daniel Henrique Barboza
On 2/4/19 7:48 AM, Christian Ehrhardt wrote: On Mon, Feb 4, 2019 at 9:59 AM Michal Privoznik wrote: On 2/1/19 7:04 PM, Daniel Henrique Barboza wrote: Hi, I'm facing a strange behavior when running Libvirt from source code, latest upstream, on an Ubuntu 18.04.1 LTS Power 9 server. My QEMU

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Daniel Henrique Barboza
On 2/4/19 6:47 AM, Yuval Shaia wrote: On Fri, Feb 01, 2019 at 07:40:36PM -0200, Daniel Henrique Barboza wrote: Update: I've figured it out. The bug here was that, even running as root, I was getting errors like: error : virQEMUCapsNewForBinaryInternal:4687 : internal error: Failed to probe

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Yuval Shaia
On Mon, Feb 04, 2019 at 09:58:47AM +0100, Michal Privoznik wrote: > On 2/1/19 7:04 PM, Daniel Henrique Barboza wrote: > > Hi, > > > > I'm facing a strange behavior when running Libvirt from source code, > > latest upstream, on an Ubuntu 18.04.1 LTS Power 9 server. My QEMU > > guest - which is

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Yuval Shaia
+ Kamal and Marcel On Mon, Feb 04, 2019 at 09:58:47AM +0100, Michal Privoznik wrote: > On 2/1/19 7:04 PM, Daniel Henrique Barboza wrote: > > Hi, > > > > I'm facing a strange behavior when running Libvirt from source code, > > latest upstream, on an Ubuntu 18.04.1 LTS Power 9 server. My QEMU > >

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Erik Skultety
On Fri, Feb 01, 2019 at 07:40:36PM -0200, Daniel Henrique Barboza wrote: > Update: I've figured it out. > > The bug here was that, even running as root, I was getting errors like: > > error : virQEMUCapsNewForBinaryInternal:4687 : internal error: Failed to > probe QEMU binary with > QMP: libvirt: 

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Christian Ehrhardt
On Mon, Feb 4, 2019 at 9:59 AM Michal Privoznik wrote: > > On 2/1/19 7:04 PM, Daniel Henrique Barboza wrote: > > Hi, > > > > I'm facing a strange behavior when running Libvirt from source code, > > latest upstream, on an Ubuntu 18.04.1 LTS Power 9 server. My QEMU > > guest - which is using VFIO

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Michal Privoznik
On 2/1/19 7:04 PM, Daniel Henrique Barboza wrote: Hi, I'm facing a strange behavior when running Libvirt from source code, latest upstream, on an Ubuntu 18.04.1 LTS Power 9 server. My QEMU guest - which is using VFIO and GPU passthrough - breaks on boot when trying to allocate a DMA window

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-04 Thread Yuval Shaia
On Fri, Feb 01, 2019 at 07:40:36PM -0200, Daniel Henrique Barboza wrote: > Update: I've figured it out. > > The bug here was that, even running as root, I was getting errors like: > > error : virQEMUCapsNewForBinaryInternal:4687 : internal error: Failed to > probe QEMU binary with > QMP:

Re: [libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-01 Thread Daniel Henrique Barboza
Update: I've figured it out. The bug here was that, even running as root, I was getting errors like: error : virQEMUCapsNewForBinaryInternal:4687 : internal error: Failed to probe QEMU binary with QMP: libvirt:  error : prctl failed to enable 'dac_override' in the AMBIENT set: Operation not

[libvirt] running Libvirt from source code, IPC_LOCK and VFIO

2019-02-01 Thread Daniel Henrique Barboza
Hi, I'm facing a strange behavior when running Libvirt from source code, latest upstream, on an Ubuntu 18.04.1 LTS Power 9 server. My QEMU guest - which is using VFIO and GPU passthrough - breaks on boot when trying to allocate a DMA window inside KVM. Debugging the code, I've found out that