On 2016/1/26 19:40, Stefan Priebe - Profihost AG wrote:
Am 26.01.2016 um 12:39 schrieb Yang Zhang:
On 2016/1/26 18:43, Stefan Priebe - Profihost AG wrote:
Am 26.01.2016 um 11:13 schrieb Yang Zhang:
On 2016/1/26 15:22, Stefan Priebe - Profihost AG wrote:
Hi,
Am 26.01.2016 um 02:46 schrieb H
Am 26.01.2016 um 12:39 schrieb Yang Zhang:
> On 2016/1/26 18:43, Stefan Priebe - Profihost AG wrote:
>>
>> Am 26.01.2016 um 11:13 schrieb Yang Zhang:
>>> On 2016/1/26 15:22, Stefan Priebe - Profihost AG wrote:
Hi,
Am 26.01.2016 um 02:46 schrieb Han, Huaitong:
> What is the host
On 2016/1/26 18:43, Stefan Priebe - Profihost AG wrote:
Am 26.01.2016 um 11:13 schrieb Yang Zhang:
On 2016/1/26 15:22, Stefan Priebe - Profihost AG wrote:
Hi,
Am 26.01.2016 um 02:46 schrieb Han, Huaitong:
What is the host kernel version and host dmesg information? And does
the problem exist
Am 26.01.2016 um 11:13 schrieb Yang Zhang:
> On 2016/1/26 15:22, Stefan Priebe - Profihost AG wrote:
>> Hi,
>>
>> Am 26.01.2016 um 02:46 schrieb Han, Huaitong:
>>> What is the host kernel version and host dmesg information? And does
>>> the problem exist when you use latest kernel and QEMU to repl
On 2016/1/26 15:22, Stefan Priebe - Profihost AG wrote:
Hi,
Am 26.01.2016 um 02:46 schrieb Han, Huaitong:
What is the host kernel version and host dmesg information? And does
the problem exist when you use latest kernel and QEMU to replace old
binary file?
Guest and Host is both 4.1.15. You m
Hi,
Am 26.01.2016 um 02:46 schrieb Han, Huaitong:
> What is the host kernel version and host dmesg information? And does
> the problem exist when you use latest kernel and QEMU to replace old
> binary file?
Guest and Host is both 4.1.15. You mean the complete dmesg output from host?
What do you
What is the host kernel version and host dmesg information? And does
the problem exist when you use latest kernel and QEMU to replace old
binary file?
On Mon, 2016-01-25 at 14:51 +0100, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> while running qemu 2.4 on whestmere CPUs i'm pretty often getting
Hi,
while running qemu 2.4 on whestmere CPUs i'm pretty often getting this
one while booting:
[0.811645] Switched APIC routing to physical x2apic.
[1.835678] [ cut here ]
[1.835704] WARNING: CPU: 0 PID: 1 at
arch/x86/kernel/apic/apic.c:1309 setup_local_APIC+0x28
