https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #10 from Mark ---
well thanks very much guys, I'll cautiously say that a patched guest kernel
seems to resolve it :-)
the bug seemed to appear even when the host is untainted; serial log says
[ 375.989736] divide error: [#1] SMP
https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #9 from Mark ---
I'll try both of your suggestions, thanks
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message t
https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #8 from Mark ---
Created attachment 166461
--> https://bugzilla.kernel.org/attachment.cgi?id=166461&action=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this lis
https://bugzilla.kernel.org/show_bug.cgi?id=92291
Paolo Bonzini changed:
What|Removed |Added
CC||bonz...@gnu.org
--- Comment #7 from Paolo
https://bugzilla.kernel.org/show_bug.cgi?id=92291
Alan changed:
What|Removed |Added
Status|NEW |NEEDINFO
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #5 from Mark ---
Created attachment 166021
--> https://bugzilla.kernel.org/attachment.cgi?id=166021&action=edit
result of guest lsmod; identical for mono-cpu / multi-cpu
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #4 from Mark ---
I should just add that that 'code' segment in the kvm dump is identical every
time, I'd be happy to try to track what is causing it, providing someone could
give me some pointers to debugging that kind of stuff in more
https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #3 from Mark ---
Created attachment 165201
--> https://bugzilla.kernel.org/attachment.cgi?id=165201&action=edit
host cpuinfo
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from t
https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #2 from Mark ---
Created attachment 165191
--> https://bugzilla.kernel.org/attachment.cgi?id=165191&action=edit
serial log when no smp
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscr
https://bugzilla.kernel.org/show_bug.cgi?id=92291
--- Comment #1 from Mark ---
Created attachment 165181
--> https://bugzilla.kernel.org/attachment.cgi?id=165181&action=edit
serial log during bug; when smp > 1
--
You are receiving this mail because:
You are watching the assignee of the bug.
-
https://bugzilla.kernel.org/show_bug.cgi?id=92291
Bug ID: 92291
Summary: kvm/guest crashes when smp > 1 with AMD FX8300; with
host kernel oops from abrt as well
Product: Virtualization
Version: unspecified
Kernel Version: 3.1
copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Johannes Truschnigg (c0l0)
Assigned to: Nobody/Anonymous (nobody)
Summary: KVM guest cra
Marcelo Tosatti wrote:
> On Mon, Jan 26, 2009 at 04:53:21PM +0100, Alexander Graf wrote:
>
>>> There are a number of problems that can result in this error, and the
>>> problems are possibly different between the in-kernel PIT and userspace
>>> PIT emulation (note it also happens with in-kernel
On Mon, Jan 26, 2009 at 04:53:21PM +0100, Alexander Graf wrote:
> > There are a number of problems that can result in this error, and the
> > problems are possibly different between the in-kernel PIT and userspace
> > PIT emulation (note it also happens with in-kernel PIT, just much more
> > rarely
Marcelo Tosatti wrote:
> Hi Alexander,
>
> On Thu, Jan 22, 2009 at 09:29:46PM +0100, Alexander Graf wrote:
>
>
>> Following the discussion on IRC, I tried -no-kvm-irqchip and found some
>> virtual machines broken after >1 day of stress testing again:
>>
>> + sudo -u contain2 env -i qemu-kvm -loc
On 24.01.2009, at 14:06, Marcelo Tosatti wrote:
On Sat, Jan 24, 2009 at 08:42:06AM +0100, Alexander Graf wrote:
rarely now). You can use the no_timer_check kernel option to bypass
it.
Ok :-). Thanks. The logic in the kernel for this is really stupid
(basing timing on clock speed). What about
On Sat, Jan 24, 2009 at 08:42:06AM +0100, Alexander Graf wrote:
>> rarely now). You can use the no_timer_check kernel option to bypass
>> it.
>
> Ok :-). Thanks. The logic in the kernel for this is really stupid
> (basing timing on clock speed). What about disabling the check if we
> detect K
Hi Marcelo,
On 23.01.2009, at 23:36, Marcelo Tosatti wrote:
Hi Alexander,
On Thu, Jan 22, 2009 at 09:29:46PM +0100, Alexander Graf wrote:
Following the discussion on IRC, I tried -no-kvm-irqchip and found
some
virtual machines broken after >1 day of stress testing again:
+ sudo -u contain
Hi Alexander,
On Thu, Jan 22, 2009 at 09:29:46PM +0100, Alexander Graf wrote:
> Following the discussion on IRC, I tried -no-kvm-irqchip and found some
> virtual machines broken after >1 day of stress testing again:
>
> + sudo -u contain2 env -i qemu-kvm -localtime -kernel virtio-kernel
> -initr
Alexander Graf wrote:
> Alexander Graf wrote:
>
>> Alexander Graf wrote:
>>
>> [...]
>>
>>
>>> Also after two days of permanent stress testing I also got the Intel
>>> machine w/ current git down:
>>>
>>> + sudo -u contain1 env -i /usr/local/bin/qemu-system-x86_64 -localtime
>>> -kernel
Alexander Graf wrote:
> Alexander Graf wrote:
>
> [...]
>
>> Also after two days of permanent stress testing I also got the Intel
>> machine w/ current git down:
>>
>> + sudo -u contain1 env -i /usr/local/bin/qemu-system-x86_64 -localtime
>> -kernel virtio-kernel -initrd virtio-initrd -nographic
Alexander Graf wrote:
[...]
> Also after two days of permanent stress testing I also got the Intel
> machine w/ current git down:
>
> + sudo -u contain1 env -i /usr/local/bin/qemu-system-x86_64 -localtime
> -kernel virtio-kernel -initrd virtio-initrd -nographic -append 'quiet
> clocksource=acpi_pm
Avi Kivity wrote:
> Avi Kivity wrote:
>>
>> I suggest checking if you have the latest BIOS update applied. I've
>> had bad experiences with un-updated processors.
>>
>
> FWIW, I have an 8-way F9 guest (2.6.27.5-blah) running on an 2x4
> Barcelona host, happily make -j16ing an allmodconfig kernel.
Avi Kivity wrote:
> Avi Kivity wrote:
>>
>> I suggest checking if you have the latest BIOS update applied. I've
>> had bad experiences with un-updated processors.
>>
>
> FWIW, I have an 8-way F9 guest (2.6.27.5-blah) running on an 2x4
> Barcelona host, happily make -j16ing an allmodconfig kernel.
Avi Kivity wrote:
I suggest checking if you have the latest BIOS update applied. I've
had bad experiences with un-updated processors.
FWIW, I have an 8-way F9 guest (2.6.27.5-blah) running on an 2x4
Barcelona host, happily make -j16ing an allmodconfig kernel.
--
error compiling committe
Alexander Graf wrote:
Avi Kivity wrote:
Alexander Graf wrote:
The guest kernels included here are openSUSE 11.0 (2.6.25) and 11.1
(2.6.27) kernels.
Find the tests here: http://alex.csgraf.de/kvm-tests.tar.bz2
And some logs here (NPT enabled): http://alex.csgraf.de/kvm-logs.tar.bz2
I'm
Avi Kivity wrote:
> Alexander Graf wrote:
>> The guest kernels included here are openSUSE 11.0 (2.6.25) and 11.1
>> (2.6.27) kernels.
>>
>> Find the tests here: http://alex.csgraf.de/kvm-tests.tar.bz2
>> And some logs here (NPT enabled): http://alex.csgraf.de/kvm-logs.tar.bz2
>>
>> I'm somewhat los
On 20.01.2009, at 21:07, Avi Kivity wrote:
Alexander Graf wrote:
Hi list,
recently I've been hitting some KVM bugs others seem to have
reported as
well, including
- CIFS timeouts
- Stuck ?? errors
- Random segmentation faults in the guest
so I figured, I'll put together a stress test
Alexander Graf wrote:
Hi list,
recently I've been hitting some KVM bugs others seem to have reported as
well, including
- CIFS timeouts
- Stuck ?? errors
- Random segmentation faults in the guest
so I figured, I'll put together a stress test that can be used to
reproduce these issues. This is
Hi list,
recently I've been hitting some KVM bugs others seem to have reported as
well, including
- CIFS timeouts
- Stuck ?? errors
- Random segmentation faults in the guest
so I figured, I'll put together a stress test that can be used to
reproduce these issues. This is done by using a CIFS mou
the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Johannes Truschnigg (c0l0)
Assigned to: Nobody/Anonymous (nobody)
Summary: KVM guest crashes w
a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Johannes Truschnigg (c0l0)
Assigned to: Nobody/Anonymous (nobody)
Summary: KVM g
32 matches
Mail list logo
