On Wed, Jan 18, 2017 at 08:35:27AM +0100, Boris Fiuczynski wrote:
> On 01/17/2017 05:39 PM, Daniel P. Berrange wrote:
> > I'm thinking we've hit the limit of what we should try to force into the
> > 3.0.0 release.
> >
> > My vote at this poiint is to change the code so that namespaces are
> >
On 01/17/2017 05:39 PM, Daniel P. Berrange wrote:
I'm thinking we've hit the limit of what we should try to force into the
3.0.0 release.
My vote at this poiint is to change the code so that namespaces are
disabled out of the box, and do a 3.0.0 release. Look at fixing the
bugs to turn it back
On 01/17/2017 05:39 PM, Daniel P. Berrange wrote:
> I'm thinking we've hit the limit of what we should try to force into the
> 3.0.0 release.
>
> My vote at this poiint is to change the code so that namespaces are
> disabled out of the box, and do a 3.0.0 release. Look at fixing the
Ack.
>
On 17.01.2017 14:21, Michal Privoznik wrote:
> On 01/17/2017 02:13 PM, Marc Hartmayer wrote:
>> Update:
>> It's a SELinux labeling problem and seems to be introduced by the
>> QEMU namespace patches.
>>
>
> I wouldn't guess from the error message that qemu is getting EPERM.
>
> Anyway, the
On Tue, Jan 17, 2017 at 04:41:57PM +0100, Michal Privoznik wrote:
> On 01/17/2017 04:28 PM, Marc Hartmayer wrote:
> > On Tue, Jan 17, 2017 at 03:28 PM +0100, Michal Privoznik
> > wrote:
> >> [Dropping libvirt-announce]
> >>
> >> On 01/17/2017 02:51 PM, Boris Fiuczynski
On Tue, Jan 17, 2017 at 04:41:57PM +0100, Michal Privoznik wrote:
> On 01/17/2017 04:28 PM, Marc Hartmayer wrote:
> > On Tue, Jan 17, 2017 at 03:28 PM +0100, Michal Privoznik
> > wrote:
> >> [Dropping libvirt-announce]
> >>
> >> On 01/17/2017 02:51 PM, Boris Fiuczynski
On Tue, Jan 17, 2017 at 04:41 PM +0100, Michal Privoznik
wrote:
> On 01/17/2017 04:28 PM, Marc Hartmayer wrote:
>> On Tue, Jan 17, 2017 at 03:28 PM +0100, Michal Privoznik
>> wrote:
>>> [Dropping libvirt-announce]
>>>
>>> On 01/17/2017 02:51 PM, Boris
On 01/17/2017 04:28 PM, Marc Hartmayer wrote:
> On Tue, Jan 17, 2017 at 03:28 PM +0100, Michal Privoznik
> wrote:
>> [Dropping libvirt-announce]
>>
>> On 01/17/2017 02:51 PM, Boris Fiuczynski wrote:
>>> On 01/17/2017 02:21 PM, Michal Privoznik wrote:
>>
>>
On Tue, Jan 17, 2017 at 03:28 PM +0100, Michal Privoznik
wrote:
> [Dropping libvirt-announce]
>
> On 01/17/2017 02:51 PM, Boris Fiuczynski wrote:
>> On 01/17/2017 02:21 PM, Michal Privoznik wrote:
>
>
>
>
> With v2.5.0 everything has worked. I'll
[Dropping libvirt-announce]
On 01/17/2017 02:51 PM, Boris Fiuczynski wrote:
> On 01/17/2017 02:21 PM, Michal Privoznik wrote:
With v2.5.0 everything has worked. I'll take a closer look to it today.
>> You can try and see if this is a namespace caused issue. Just
On 01/17/2017 02:21 PM, Michal Privoznik wrote:
With v2.5.0 everything has worked. I'll take a closer look to it today.
You can try and see if this is a namespace caused issue. Just disable
the namespaces and retry. If it succeeds with namespaces disabled, the
bug indeed is in my
On 01/17/2017 02:13 PM, Marc Hartmayer wrote:
> Update:
> It's a SELinux labeling problem and seems to be introduced by the
> QEMU namespace patches.
>
I wouldn't guess from the error message that qemu is getting EPERM.
Anyway, the SELinux issue is fixed in -rc2:
commit
Update:
It's a SELinux labeling problem and seems to be introduced by the
QEMU namespace patches.
On Tue, Jan 17, 2017 at 11:18 AM +0100, Marc Hartmayer
wrote:
> Hey,
>
> I have tried to live hot plug a disk backed on a qcow2 disk (see XML
> snippet below) on a s390
Hey,
I have tried to live hot plug a disk backed on a qcow2 disk (see XML
snippet below) on a s390 system and I've got the following error
message:
internal error: unable to execute QEMU command 'device_add': Property
'scsi-hd.drive' can't find value 'drive-scsi0-0-0-0'
On Sat, Jan 14, 2017 at 11:02:37PM +0100, Daniel Veillard wrote:
> I missed the Friday deadline ot push it, so did it today. It's now tagged
> in git, signed tarball and rpms are at the usual place:
>ftp://libvirt.org/libvirt/
>
> As a result I think GA should happen on Tuesday to give at
I missed the Friday deadline ot push it, so did it today. It's now tagged
in git, signed tarball and rpms are at the usual place:
ftp://libvirt.org/libvirt/
As a result I think GA should happen on Tuesday to give at least one
working day to raise critical issues. Nothing seems to have been
16 matches
Mail list logo