On 19/04/2015 18:50, Brad Campbell wrote:
> And I can confidently state that over the years I've seen this happen a
> number of times, but in each case I was using qemu with an SDL console
> as a user-interactive VM, and a moving the mouse would restore network
> connectivity. It was obviously se
On 19/04/15 23:48, Nadav Amit wrote:
Brad Campbell wrote:
On 13/04/15 22:02, Paolo Bonzini wrote:
On 13/04/2015 14:45, Brad Campbell wrote:
G'day Paolo,
Yes, on AMD and I've tried hard to reproduce it on Intel and been unable
to thus far.
Now you mention it may be AMD specific, I have a s
Brad Campbell wrote:
>
> On 13/04/15 22:02, Paolo Bonzini wrote:
>> On 13/04/2015 14:45, Brad Campbell wrote:
>>> G'day Paolo,
>>>
>>> Yes, on AMD and I've tried hard to reproduce it on Intel and been unable
>>> to thus far.
>>>
>>> Now you mention it may be AMD specific, I have a spare mother
On 13/04/15 22:02, Paolo Bonzini wrote:
On 13/04/2015 14:45, Brad Campbell wrote:
G'day Paolo,
Yes, on AMD and I've tried hard to reproduce it on Intel and been unable
to thus far.
Now you mention it may be AMD specific, I have a spare motherboard and
processor sitting in a drawer. I'll bolt
On 13/04/15 22:02, Paolo Bonzini wrote:
Actually, if you have time to change your course of action, please
revert the one that Nadav pointed out (f210f7572bed, KVM: x86:
Fix lost interrupt on irr_pending race) or cherry-pick it on top of 3.17.
Ok, I've done just that. Started on a 3.17 vani
On 13/04/2015 15:34, Nadav Amit wrote:
> Paolo,
>
> I hope I am not misleading or interrupting, and I am obviously very biased —
> but couldn’t it be related to the issue that patch f210f7572bed ("KVM: x86:
> Fix lost interrupt on irr_pending race”) deals with?
>
> I got this issue first when I
On 13/04/2015 14:45, Brad Campbell wrote:
> G'day Paolo,
>
> Yes, on AMD and I've tried hard to reproduce it on Intel and been unable
> to thus far.
>
> Now you mention it may be AMD specific, I have a spare motherboard and
> processor sitting in a drawer. I'll bolt it together tomorrow and see
Paolo,
I hope I am not misleading or interrupting, and I am obviously very biased —
but couldn’t it be related to the issue that patch f210f7572bed ("KVM: x86:
Fix lost interrupt on irr_pending race”) deals with?
I got this issue first when I upgraded to 3.17 in my testing environment,
since appa
2015-04-13 14:38+0200, Paolo Bonzini:
> If so, the most likely culprit is this:
>
> commit 6addfc42992be4b073c39137ecfdf4b2aa2d487f
> Author: Paolo Bonzini
> Date: Thu Mar 27 11:29:28 2014 +0100
>
> KVM: x86: avoid useless set of KVM_REQ_EVENT after emulation
| [...]
>
> I would first try
On 13/04/15 20:38, Paolo Bonzini wrote:
On 13/04/2015 06:07, Brad Campbell wrote:
On 31/03/15 05:11, Paolo Bonzini wrote:
On 22/03/2015 16:31, Brad Campbell wrote:
No help I'm afraid, but at least I can conclusively say that 3.16 is
good, and 3.17 is bad.
Can you try more specifically aroun
> From: Paolo Bonzini
> Sent: Monday, April 13, 2015 2:39 PM
> Subject: Re: XP machine freeze
>
> ...
> Also:
>
> 1) Brad, I see you are on AMD. Have you ever reproduced it on Intel?
> Saso, are you on AMD as well?
No, this is an Intel machine:
Intel(R) Xeon(
On 13/04/2015 06:07, Brad Campbell wrote:
>
> On 31/03/15 05:11, Paolo Bonzini wrote:
>>
>> On 22/03/2015 16:31, Brad Campbell wrote:
>>>
>>> No help I'm afraid, but at least I can conclusively say that 3.16 is
>>> good, and 3.17 is bad.
>> Can you try more specifically around the first KVM pull
On 31/03/15 05:11, Paolo Bonzini wrote:
On 22/03/2015 16:31, Brad Campbell wrote:
No help I'm afraid, but at least I can conclusively say that 3.16 is
good, and 3.17 is bad.
Can you try more specifically around the first KVM pull request? That
would be between c9b88e958182 (presumed good) a
On 31/03/15 19:23, Paolo Bonzini wrote:
On 31/03/2015 13:16, Brad Campbell wrote:
If you look at the bisect point I'm currently at it's a mix of i2c and
arm. The only vaguely relevant (as far as I can see) commit is the
addition of the getrandom() syscall, so my bisect is looking dodgy at
best
On 31/03/2015 13:16, Brad Campbell wrote:
>
> If you look at the bisect point I'm currently at it's a mix of i2c and
> arm. The only vaguely relevant (as far as I can see) commit is the
> addition of the getrandom() syscall, so my bisect is looking dodgy at
> best. If I can come up with a better
On 31/03/15 16:56, Paolo Bonzini wrote:
On 31/03/2015 09:18, Brad Campbell wrote:
Better than that, it's recording h264 rtsp streams from 3 CCTV cameras,
so there is a constant network load of about 1.5-2MB/s (bytes not bits).
Come to think of it, out of the 3 XP VM's I have that are an identi
On 31/03/2015 09:18, Brad Campbell wrote:
> Better than that, it's recording h264 rtsp streams from 3 CCTV cameras,
> so there is a constant network load of about 1.5-2MB/s (bytes not bits).
> Come to think of it, out of the 3 XP VM's I have that are an identical
> config and actually come from t
On 31/03/15 14:29, Saso Slavicic wrote:
From: Brad Campbell
Sent: Tuesday, March 31, 2015 2:28 AM
If someone could give me some hard tests to do along the lines of what
Saso is up to I could probably get that done faster. With the right
bad kernel I can reproduce this lockup in a matter of hou
> From: Brad Campbell
> Sent: Tuesday, March 31, 2015 2:28 AM
>
>
> If someone could give me some hard tests to do along the lines of what
> Saso is up to I could probably get that done faster. With the right
> bad kernel I can reproduce this lockup in a matter of hours.
Hi,
My machine usually (b
On 31/03/15 05:11, Paolo Bonzini wrote:
On 22/03/2015 16:31, Brad Campbell wrote:
No help I'm afraid, but at least I can conclusively say that 3.16 is
good, and 3.17 is bad.
Can you try more specifically around the first KVM pull request? That
would be between c9b88e958182 (presumed good)
On 22/03/2015 16:31, Brad Campbell wrote:
>
>
> No help I'm afraid, but at least I can conclusively say that 3.16 is
> good, and 3.17 is bad.
Can you try more specifically around the first KVM pull request? That
would be between c9b88e958182 (presumed good) and 8533ce727188 (presumed
bad)?
T
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Thursday, March 19, 2015 1:52 AM
>
> Generate a Windows dump?
>
> https://support.microsoft.com/en-us/kb/254649
>
> https://support.microsoft.com/en-us/kb/972110
> Step 7: Generate a complete crash dump file or a kernel crash dump fi
On 16/03/15 23:10, Saso Slavicic wrote:
Hi,
I'm fairly experienced with KVM (Centos 5/6), running about a dozen servers
with 20-30 different (Linux & MS platform) systems.
I have one Windows XP machine that acts very strangely - it freezes. I get
ping timeout for the VM from my monitoring and th
On Mon, Mar 16, 2015 at 04:10:40PM +0100, Saso Slavicic wrote:
> Hi,
>
> I'm fairly experienced with KVM (Centos 5/6), running about a dozen servers
> with 20-30 different (Linux & MS platform) systems.
> I have one Windows XP machine that acts very strangely - it freezes. I get
> ping timeout for
Hi,
I'm fairly experienced with KVM (Centos 5/6), running about a dozen servers
with 20-30 different (Linux & MS platform) systems.
I have one Windows XP machine that acts very strangely - it freezes. I get
ping timeout for the VM from my monitoring and the machine spins 2 or 3
cores using all the
25 matches
Mail list logo
