e not from the same crash
instance.
I'm not subscribed,so please cc me on any reply.
Happy to provide any additional diagnostics (but may need help on how to
get them) or test patches, etc
Thanks
Chris Clayton
--
To unsubscribe from this list: send the line "unsubscribe kvm&qu
Ping.
Have I committed a bug-reporting sin in the mail below or is everyone
simply too busy to look at this kvm-related crash?
On 07/09/12 11:57, Chris Clayton wrote:
Hi,
When I run WinXP SP3 through qemu-kvm-1.1.0 on linux kernel 3.5.0-rc6, I
get a segmentation fault within 3 or 4 minutes
On 07/11/12 08:12, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in the mail below or is
everyone simply too busy to look at this kvm-related crash?
Since you have good and bad points can you bisect the problem
On 07/11/12 08:22, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:18:17AM +0100, Chris Clayton wrote:
On 07/11/12 08:12, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in the mail below or is
everyone simply too
On 07/15/12 20:52, Chris Clayton wrote:
On 07/11/12 08:22, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:18:17AM +0100, Chris Clayton wrote:
On 07/11/12 08:12, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact, crash
on 3.5.0-rc6 (and rc7). I didn't get it earlier because it takes many
times more invocations before the crash occurs with 1.0.1
On 07/19/12 19:23, Chris Clayton wrote:
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact,
crash
on 3.5.0-rc6 (and rc7). I didn't get it earlier because it takes many
times more invoca
On 07/26/12 11:01, Avi Kivity wrote:
On 07/26/2012 12:52 PM, Chris Clayton wrote:
On 07/19/12 19:23, Chris Clayton wrote:
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact,
crash
on 3.5.0-rc6
On 07/26/12 12:10, Xiao Guangrong wrote:
Hi Chris,
Could you please try this patch?
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=ccebf448daf7964ee2aff7947c0bbe4c7962d059
Sorry, that patch does not fix the crashes.
On 07/26/2012 05:52 PM, Chris Clayton wrote:
On
On 07/26/12 13:07, Avi Kivity wrote:
On 07/26/2012 02:58 PM, Chris Clayton wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
I've just done 10 runs of WinXP SP3 and 5 of them crashed. Three crashe
On 07/27/12 00:22, Chris Clayton wrote:
On 07/26/12 13:07, Avi Kivity wrote:
On 07/26/2012 02:58 PM, Chris Clayton wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
I've just done 10 runs of WinXP
On 07/27/12 19:08, Eric Northup wrote:
Could you include the output of "info registers" at the point where it
crashed?
Here you go:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6a78b40 (LWP 13249)]
__strcmp_sse4_2 () at ../sysdeps/i386/i686/multiarch/strcmp-sse
On 07/29/12 13:42, Avi Kivity wrote:
On 07/27/2012 10:04 PM, Chris Clayton wrote:
On 07/27/12 19:08, Eric Northup wrote:
Could you include the output of "info registers" at the point where it
crashed?
Here you go:
Program received signal SIGSEGV, Segmentation fault.
[Switching
On 07/29/12 15:48, Avi Kivity wrote:
On 07/29/2012 05:18 PM, Avi Kivity wrote:
I think you are saying that the problem isn't in kvm, so where would you
recommend I continue investigations. I'm not seeing a crash with any
other applications.
What might have happened is that the movdqu instruct
On 07/29/12 17:34, Avi Kivity wrote:
On 07/29/2012 06:47 PM, Avi Kivity wrote:
What might have happened is that the movdqu instruction faulted (as it's
an fpu instruction), and on the way back from the fault, ds and es
didn't get restored correctly.
You can test this by writing a trivial versio
On 07/29/12 18:54, Gleb Natapov wrote:
On Sun, Jul 29, 2012 at 06:50:09PM +0100, Chris Clayton wrote:
On 07/29/12 17:34, Avi Kivity wrote:
On 07/29/2012 06:47 PM, Avi Kivity wrote:
What might have happened is that the movdqu instruction faulted (as it's
an fpu instruction), and on th
On 07/29/12 20:10, Chris Clayton wrote:
Possible culprit: b2da15ac26a0c00.
That commit isn't in qermu-kvm-1.1.1.
It is in kernel.
Sorry, so it is.
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
clean invocations of vanilla qemu-kvm-1.1.1. So that commit would
On 07/30/12 15:03, Avi Kivity wrote:
On 07/30/2012 05:00 PM, Chris Clayton wrote:
On 07/29/12 20:10, Chris Clayton wrote:
Possible culprit: b2da15ac26a0c00.
That commit isn't in qermu-kvm-1.1.1.
It is in kernel.
Sorry, so it is.
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I
ightweight exit path.
Reported-by: Chris Clayron
Signed-off-by: Avi Kivity
I've just had 15 successful runs of qemu-kvm-1.1.1 with kernel 3.5.0
plus this patch, so:
Tested-by: Chris Clayton
I assume this will be forwarded to stable once it has been applied to
mainline.
---
arc
leared
ds, es)
Fix by avoiding the optimization on i386 and reloading ds, es on the
lightweight exit path.
Reported-by: Chris Clayron
Signed-off-by: Avi Kivity
I've just had 15 successful runs of qemu-kvm-1.1.1 with kernel 3.5.0
plus this patch, so:
Tested-by: Chris Clayton
I assume this
20 matches
Mail list logo
