On Tue, Jan 15, 2019 at 03:53:42PM +0100, Peter Krempa wrote:
> On Tue, Jan 15, 2019 at 15:42:41 +0100, Jiri Denemark wrote:
> > On Mon, Jan 14, 2019 at 15:40:32 +, Daniel P. Berrangé wrote:
> > > On Mon, Jan 14, 2019 at 04:15:01PM +0100, Jiri Denemark wrote:
> > > > On Mon, Jan 14, 2019 at 15:
On Tue, Jan 15, 2019 at 15:42:41 +0100, Jiri Denemark wrote:
> On Mon, Jan 14, 2019 at 15:40:32 +, Daniel P. Berrangé wrote:
> > On Mon, Jan 14, 2019 at 04:15:01PM +0100, Jiri Denemark wrote:
> > > On Mon, Jan 14, 2019 at 15:03:26 +, Daniel P. Berrangé wrote:
> > > > On Mon, Jan 14, 2019 at
On Mon, Jan 14, 2019 at 15:40:32 +, Daniel P. Berrangé wrote:
> On Mon, Jan 14, 2019 at 04:15:01PM +0100, Jiri Denemark wrote:
> > On Mon, Jan 14, 2019 at 15:03:26 +, Daniel P. Berrangé wrote:
> > > On Mon, Jan 14, 2019 at 03:36:38PM +0100, Jiri Denemark wrote:
> > > > On Mon, Jan 14, 2019
On Mon, Jan 14, 2019 at 04:15:01PM +0100, Jiri Denemark wrote:
> On Mon, Jan 14, 2019 at 15:03:26 +, Daniel P. Berrangé wrote:
> > On Mon, Jan 14, 2019 at 03:36:38PM +0100, Jiri Denemark wrote:
> > > On Mon, Jan 14, 2019 at 14:21:42 +, Daniel P. Berrangé wrote:
> > > > On Mon, Jan 14, 2019
On Mon, Jan 14, 2019 at 15:03:26 +, Daniel P. Berrangé wrote:
> On Mon, Jan 14, 2019 at 03:36:38PM +0100, Jiri Denemark wrote:
> > On Mon, Jan 14, 2019 at 14:21:42 +, Daniel P. Berrangé wrote:
> > > On Mon, Jan 14, 2019 at 02:56:43PM +0100, Jiri Denemark wrote:
> > > > On Mon, Jan 14, 2019
On Mon, Jan 14, 2019 at 03:36:38PM +0100, Jiri Denemark wrote:
> On Mon, Jan 14, 2019 at 14:21:42 +, Daniel P. Berrangé wrote:
> > On Mon, Jan 14, 2019 at 02:56:43PM +0100, Jiri Denemark wrote:
> > > On Mon, Jan 14, 2019 at 20:07:34 +0800, zhenwei pi wrote:
> > > > Let libvirtd handle invalid x
On Mon, Jan 14, 2019 at 14:21:42 +, Daniel P. Berrangé wrote:
> On Mon, Jan 14, 2019 at 02:56:43PM +0100, Jiri Denemark wrote:
> > On Mon, Jan 14, 2019 at 20:07:34 +0800, zhenwei pi wrote:
> > > Let libvirtd handle invalid x86 cpu map error, and report the real reason.
> > >
> > > This issue c
On Mon, Jan 14, 2019 at 02:56:43PM +0100, Jiri Denemark wrote:
> On Mon, Jan 14, 2019 at 20:07:34 +0800, zhenwei pi wrote:
> > Let libvirtd handle invalid x86 cpu map error, and report the real reason.
> >
> > This issue can be reproduced :
> > 1, rm -rf /share/libvirt/cpu_map
> > 2, start libvirt
On Mon, Jan 14, 2019 at 20:07:34 +0800, zhenwei pi wrote:
> Let libvirtd handle invalid x86 cpu map error, and report the real reason.
>
> This issue can be reproduced :
> 1, rm -rf /share/libvirt/cpu_map
> 2, start libvirtd
> 3, virsh create INSTANCE.xml
>
> Libvirtd reports error :
> error: inv
Hi,
This series was run against 'syntax-check' test by patchew.org, which failed,
please find the details below:
Type: series
Subject: [libvirt] [PATCH] report invalid x86 cpu map error
Message-id: 1547467654-7093-1-git-send-email-pizhen...@bytedance.com
=== TEST SCRIPT BEGIN ===
#
Let libvirtd handle invalid x86 cpu map error, and report the real reason.
This issue can be reproduced :
1, rm -rf /share/libvirt/cpu_map
2, start libvirtd
3, virsh create INSTANCE.xml
Libvirtd reports error :
error: invalid argument: Failed to parse group 'tss'
In face, libvirtd gets invalid c
11 matches
Mail list logo