On 05/04/2017 11:20 AM, Stefano Ricci wrote:
> 2017-05-03 8:56 GMT+02:00 Michal Privoznik :
>> On 05/01/2017 09:57 AM, Stefano Ricci wrote:
>>> 2017-05-01 7:32 GMT+02:00 Michal Privoznik :
On 04/30/2017 07:12 PM, Stefano Ricci wrote:
>
> The version used for backtrace is 3.2.0, no
2017-05-03 8:56 GMT+02:00 Michal Privoznik :
> On 05/01/2017 09:57 AM, Stefano Ricci wrote:
>> 2017-05-01 7:32 GMT+02:00 Michal Privoznik :
>>> On 04/30/2017 07:12 PM, Stefano Ricci wrote:
>>>
The version used for backtrace is 3.2.0, now I have also tried the
current downloaded with
On 05/01/2017 09:57 AM, Stefano Ricci wrote:
> 2017-05-01 7:32 GMT+02:00 Michal Privoznik :
>> On 04/30/2017 07:12 PM, Stefano Ricci wrote:
>>
>>>
>>> The version used for backtrace is 3.2.0, now I have also tried the
>>> current downloaded with git but the problem is always present.
>>> This is th
2017-05-01 7:32 GMT+02:00 Michal Privoznik :
> On 04/30/2017 07:12 PM, Stefano Ricci wrote:
>
>>
>> The version used for backtrace is 3.2.0, now I have also tried the
>> current downloaded with git but the problem is always present.
>> This is the current version log file, set as shown on the Debug
On 04/30/2017 07:12 PM, Stefano Ricci wrote:
>
> The version used for backtrace is 3.2.0, now I have also tried the
> current downloaded with git but the problem is always present.
> This is the current version log file, set as shown on the DebugLogs page:
>
> https://drive.google.com/open?id=0B
2017-04-29 7:24 GMT+02:00 Michal Privoznik :
> On 04/29/2017 04:38 AM, Stefano Ricci wrote:
>> 2017-04-28 14:33 GMT+02:00 Michal Privoznik :
>>> On 04/27/2017 04:31 PM, Stefano Ricci wrote:
Here is the backtrace of the libvirt process just started
>>>
>>> [Just a side note, you shouldn't top p
On 04/29/2017 04:38 AM, Stefano Ricci wrote:
> 2017-04-28 14:33 GMT+02:00 Michal Privoznik :
>> On 04/27/2017 04:31 PM, Stefano Ricci wrote:
>>> Here is the backtrace of the libvirt process just started
>>
>> [Just a side note, you shouldn't top post on technical lists. Gmail
>> sucks at this.]
>>
2017-04-28 14:33 GMT+02:00 Michal Privoznik :
> On 04/27/2017 04:31 PM, Stefano Ricci wrote:
>> Here is the backtrace of the libvirt process just started
>
> [Just a side note, you shouldn't top post on technical lists. Gmail
> sucks at this.]
>
>>
>> https://pastebin.com/R66myzFp
>
> Looks like li
On 04/27/2017 04:31 PM, Stefano Ricci wrote:
> Here is the backtrace of the libvirt process just started
[Just a side note, you shouldn't top post on technical lists. Gmail
sucks at this.]
>
> https://pastebin.com/R66myzFp
Looks like libvirtd is trying to spawn /usr/bin/qemu-system-x86_64 but
i
Here is the backtrace of the libvirt process just started
https://pastebin.com/R66myzFp
Stefano
2017-04-27 15:12 GMT+02:00 Michal Privoznik :
> On 04/27/2017 03:11 PM, Michal Privoznik wrote:
>> On 04/27/2017 02:02 PM, Stefano Ricci wrote:
>>> Hello everyone
>>> I come back to ask for a hand to
On 04/27/2017 03:11 PM, Michal Privoznik wrote:
> On 04/27/2017 02:02 PM, Stefano Ricci wrote:
>> Hello everyone
>> I come back to ask for a hand to solve a problem that has affected me
>> since October 2016 and I have not yet solved using libvirt.
>> I thought I would solve it by going to a 4.9.x
On 04/27/2017 02:02 PM, Stefano Ricci wrote:
> Hello everyone
> I come back to ask for a hand to solve a problem that has affected me
> since October 2016 and I have not yet solved using libvirt.
> I thought I would solve it by going to a 4.9.x kernel with qemu
> 2.8.1.1 and with libvirt 3.2.0.
> C
Hello everyone
I come back to ask for a hand to solve a problem that has affected me
since October 2016 and I have not yet solved using libvirt.
I thought I would solve it by going to a 4.9.x kernel with qemu
2.8.1.1 and with libvirt 3.2.0.
Compile it all in a stable LFS environment version 7.9 and
13 matches
Mail list logo
